• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Cursor above siblings
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cursor above siblings


  • Subject: Re: Cursor above siblings
  • From: Quincey Morris <email@hidden>
  • Date: Sat, 10 Jan 2015 20:25:07 +0000

On Jan 10, 2015, at 11:42 , ecir hana <email@hidden> wrote:
>
> And that is where it stops working, no need to visit Neptune. The part of custom view over the textview stops displaying the defined cursor, at shows I-beam cursor instead.

Excellent! (Not that it fails, but that you have something specific to work on.)

Have you checked to see whether your custom view’s cursorUpdate: is called at all, when it doesn’t work? There’s a difference between not being sent the message, and being sent the message but having your cursor change made irrelevant by the other view changing the cursor afterwards.

> I have single one custom view and its tracking area covers the whole [self bounds].

If you literally set the tracking area to self.bounds, that is not such a good idea, generally. The bounds might be different at different times. You should really use the option to track the visibleRect automatically.

The other thing you should be looking into:

If the text view uses NSTrackingArea (and my understanding is that it does so, but I don’t know for sure), then it shouldn’t be getting any cursorUpdate: messages *while the cursor is already inside its tracking area*. Therefore, there might be different behavior depending on whether the cursor enters:

— the text field tracking area first, then the custom tracking area deeper inside the text field area, or
— vice versa, or
— both tracking areas simultaneously, because the boundaries are in the same place

Note that the answer is potentially different for each of the 4 edges of the tracking area rect, and for each direction of movement (towards inside/towards outside).

BTW, if the text field is changing the cursor on mouseMoved: events, which is possible, then your attempts to control the cursor with cursorUpdate: seem doomed to failure.

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden


  • Follow-Ups:
    • Re: Cursor above siblings
      • From: email@hidden
References: 
 >Cursor above siblings (From: ecir hana <email@hidden>)
 >Re: Cursor above siblings (From: Uli Kusterer <email@hidden>)
 >Re: Cursor above siblings (From: ecir hana <email@hidden>)
 >Re: Cursor above siblings (From: Uli Kusterer <email@hidden>)
 >Re: Cursor above siblings (From: ecir hana <email@hidden>)
 >Re: Cursor above siblings (From: Quincey Morris <email@hidden>)
 >Re: Cursor above siblings (From: ecir hana <email@hidden>)

  • Prev by Date: Re: Cursor above siblings
  • Next by Date: Mouse tracking under a transparent view still working
  • Previous by thread: Re: Cursor above siblings
  • Next by thread: Re: Cursor above siblings
  • Index(es):
    • Date
    • Thread