erratum: in your context, initializing tracking w/ NSTrackingCursorUpdate & defining cursorUpdate is probably more appropriate. &, on further reflection, this technique does not inhibit the sending of mouseMoved in the parent view. an interesting problem—should you discover a solution i hope you will post it.
On Apr 23, 2014, at 1:16 PM, edward taffel <[email protected]> wrote: > if i understand you correctly: you want to adjust the cursor in your view > based on state, but embedded controls should set the cursor independently. > you might try subclassing the controls in question, register a tracking area > (for controls that do not already have one, only) & define mouseEntered (set > the cursor here) for each. i’ve done similar w/ custom views but your results > may vary w/ stock controls. > > hope this helps. > > > On Apr 23, 2014, at 9:48 AM, Sean McBride <[email protected]> wrote: > >> Hi all, >> >> I'm trying to determine how to manage the mouse cursor in the case of >> overlapping sibling views. >> >> I have a custom NSView that needs to change its cursor depending on mouse >> position and internal state. The sibling views (which all draw on top of my >> view, thus appearing sorta like subviews) are simple standard Cocoa controls >> (ex: push buttons, popup menus). Since those siblings views are always 'on >> top', I want them to decide the mouse cursor if the cursor is above them, >> but Cocoa still calls my mouseMoved: method, which I guess is not >> unreasonable since the cursor is in fact above several views at the same >> time. >> >> I haven't been able to find any docs about how cursor handling works with >> overlapping views, anyone know? >> >> Thanks, >> >> -- >> ____________________________________________________________ >> Sean McBride, B. Eng [email protected] >> Rogue Research www.rogue-research.com >> Mac Software Developer Montréal, Québec, Canada >> >> >> >> _______________________________________________ >> >> Cocoa-dev mailing list ([email protected]) >> >> Please do not post admin requests or moderator comments to the list. >> Contact the moderators at cocoa-dev-admins(at)lists.apple.com >> >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/cocoa-dev/etaffel%40me.com >> >> This email sent to [email protected] > > _______________________________________________ > > Cocoa-dev mailing list ([email protected]) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/etaffel%40me.com > > This email sent to [email protected] _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
