WebKit + Native Xcode target + ZeroLink disabled + 10.2.7 SDK = weird dragging?!?!
WebKit + Native Xcode target + ZeroLink disabled + 10.2.7 SDK = weird dragging?!?!
- Subject: WebKit + Native Xcode target + ZeroLink disabled + 10.2.7 SDK = weird dragging?!?!
- From: George Browning <email@hidden>
- Date: Fri, 23 Jan 2004 15:35:15 -0500
This has been posted to Apple with bugreporter #3532730.
Earlier this was a discussion on the webkitsdk list but now that it
appears to be an Xcode problem so I'm moving it over here.
PROBLEM:
Our app uses WebKit. If you drag an image from a WebKit-rendered view
the dragging image is upside down. Interestingly if you select some
text and drag it, that dragging image is fine.
This only occurs on 10.3.x systems. It works fine on 10.2 systems.
HOW TO REPRODUCE:
How to reproduce the flipped dragging image with the MiniBrowser sample
application with Xcode 1.1 and Mac OS 10.3.2:
Looks like the flipped image is due to a combination of these three
items: (1) Native XCode targets, (2) ZeroLink disabled, (3) the 10.2.7
SDK.
1. Make a backup copy of /Developer/Examples/MiniBrowser.
2. Open MiniBrowser.pbproj in Xcode.
3. In the Groups & Files list, expand the Targets item.
4. Click on the MiniBrowser target and choose Project > Upgrade
"MiniBrowser" To Native Target.
5. While the top item, "MiniBrowser", is selected in the Groups & Files
list, bring up the Inspector.
6. Turn off ZeroLink (under the Styles tab in the Inspector) and switch
the Cross-Develop SDK to 10.2.7 (under the General tab).
7. Switch the Active Target on the toolbar to the original MiniBrowser
target.
8. Choose Build > Build and Run. The browser will pop up and you can
drag an image and the dragging image is rightside up. Quit MiniBrowser.
9. Do a Clean All (this is important!).
10. Switch the Active Target on the toolbar to the new MiniBrowser
(Upgraded) native target.
11. Choose Build > Build and Run. The browser will pop up and you can
drag an image and the dragging image is now UPSIDE DOWN! Quit
MiniBrowser.
The dragging works beautifully with the original non-native target.
Non-Native + ZeroLink On + Current OS = works
Non-Native + ZeroLink Off + Current OS = works
Non-Native + ZeroLink On + 10.2.7 = works
Non-Native + ZeroLink Off + 10.2.7 = works
However, if you use a native target then it gets messy:
Native + ZeroLink On + Current OS = works
Native + ZeroLink Off + Current OS = works
Native + ZeroLink On + 10.2.7 = works
Native + ZeroLink Off + 10.2.7 = DOESN'T WORK!!!!
Obviously for a shipping product ZeroLink has to be off. And,
unfortunately, our app needs 10.2.7 because we need libcrypto and we
have to support 10.2 Macs.
BTW: I have MACOSX_DEPLOYMENT_TARGET set to 10.2 in my
~/.MacOSX/environment.plist and .tcshrc since I'm only deploying only
as far back as 10.2 (thus supporting weak linking).
Does anyone have any suggestions on how I can work around this issue?
My first thought is to bring back ProjectBuilder and re-create a PB
target for our application. <sigh>
Thanks,
g
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.