Re: How to cleanup visual feedback from setDropRow
Re: How to cleanup visual feedback from setDropRow
- Subject: Re: How to cleanup visual feedback from setDropRow
- From: Steve Cronin <email@hidden>
- Date: Wed, 1 Mar 2006 13:09:49 -0600
Subclassing to support keyDown and awakeFromNib dragType
registration - that's it
IB - both tableViews are subViews of NSBoxes which are themselves the
subViews of an NSSplitView
On Mar 1, 2006, at 1:01 PM, Corbin Dunn wrote:
On Feb 28, 2006, at 9:30 PM, Steve Cronin wrote:
Folks;
I've got tableViews, 2 of 'em actually, that support dropping items.
One does NSTableViewDropAbove and the other does NSTableViewDropOn.
Both exhibit the same problem, a residual visual indicator if the
drag leaves the target while still hovering over a valid proposed
row which has responded with a NSTableViewDropOperation.
draggingExited doesn't give me access to the proposed row.
Even if it did, there is no NSTableViewDropOperation which would
allow me to say: None.
How do I clean up this stray (boxed row) or (line indicator) when
the drag source leaves the tableView?
The cleanup should automatically happen. Are you subclassing or
doing anything strange? Does the DragNDropOutlineView demo app work
fine for you?
-corbin
_______________________________________________
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