• 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: Confused about NSTrackingAreas with autoscroll
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Confused about NSTrackingAreas with autoscroll


  • Subject: Re: Confused about NSTrackingAreas with autoscroll
  • From: Luke Evans <email@hidden>
  • Date: Tue, 3 Feb 2009 14:14:53 -0800

This really looks like the tracking areas established on the view when the original mouse down event (that starts the drag) are cached and remain in play during the drag operation.
Can anyone confirm if this is the case?


Overtly updating the tracking areas after calling '-autoscroll:' by directly calling -updateTrackingAreas on the table, does not seem to affect what tracking areas fire events so long as I remain in the drag. Everything returns to normal as soon as the drag operation completes.


On 2-Feb-09, at 5:42 PM, Luke Evans wrote:

I have an overridden -updateTrackingAreas to compute some tracking areas in a table view. This is being called when I move the vertical scroll bar, but I have an event loop to handle drag operations in which I start NSPeriodic events and call -autoScroll on the view when the use drags outside the visible rectangle of the table. When this happens, I recompute my tracking areas (because a new row is probably visible).
The odd thing is that when the mouse just returns to the visible table view (still in the drag operation), say from dragging off the bottom of the visible table area, the tracking area for prior last visible row is activated (in its old location, even though this rectangle in table view coordinates is now scrolled higher up in the viewport).


This behaviour is as if the table view (or something) isn't taking the scroll view offset of the table coords into consideration (while the mouse is down and I'm running my own event loop). Certainly everything seems to work when I'm not dragging (i.e. using the scroll bar then mousing over the tracking areas).

Is it possible that some extra events have to be manually requested/ dispatched while I'm in my drag event loop in order to allow an - autoscroll: (or for that matter a -scrollRectToVisible:) to work properly?

Cheers

-- Lwe



_______________________________________________

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: Confused about NSTrackingAreas with autoscroll
      • From: Quincey Morris <email@hidden>
References: 
 >Confused about NSTrackingAreas with autoscroll (From: Luke Evans <email@hidden>)

  • Prev by Date: re: Core Data: arrangedObjects for multiple selections
  • Next by Date: Re: what does LSUIElement really do?
  • Previous by thread: Confused about NSTrackingAreas with autoscroll
  • Next by thread: Re: Confused about NSTrackingAreas with autoscroll
  • Index(es):
    • Date
    • Thread