Re: Cocoa from carbon - cursor tracking issues
Re: Cocoa from carbon - cursor tracking issues
- Subject: Re: Cocoa from carbon - cursor tracking issues
- From: Alan Dail <email@hidden>
- Date: Tue, 26 Jul 2005 10:34:03 -0400
good idea - I just tried this. I didn't even have to write an app.
Instead I downloaded the apple sample CocoaInCarbon (which includes
the already built app)
http://developer.apple.com/samplecode/CocoaInCarbon/CocoaInCarbon.html
and get a similar kind of behavior. When I use the menu command Open
Cocoa Window, the window that opens has a text field. When I
activate the field, I get an ibeam, when I leave the field, it stays
an ibeam. Even after I leave the window it stays an iBeam. If I
click in the menu bar, it turns back into a pointer, when I mouse
back over the text field, it does not turn back into an iBeam.
This is quite confusing to users - is there a way to fix it? I
tested under both 10.4.2 and 10.3.9.
Alan
On Jul 26, 2005, at 9:44 AM, Daniel Jalkut wrote:
On Jul 26, 2005, at 9:13 AM, Alan Dail wrote:
Any ideas on this? When I run the dialog in interface builder,
cursor tracking works fine. When I call the dialog from carbon,
cursor tracking is all messed up. We're trying to migrate our app
to cocoa, but we can't move the whole thing at once. Is it
possible that our carbon code (MacApp) is simply receiving an
event intended for my cocoa window and isn't passing it on to the
window?
I have noticed that some Carbon applications aggressively change
the cursor back to arrow at regular time intervals. Could this be
something MacApp is doing on your behalf? Can you try creating a
simple Carbon application (not MacApp based) and see if displaying
your Cocoa dialog from that works as expected?
Daniel
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden