After playing around with stuff, I realized that this was probably the best
option. It means tweaking my model slightly, but it'll probably be the better
option in the long run.
Thanks, Graham!
Dave
On May 7, 2010, at 11:07 PM, Graham Cox wrote:
> Why not cache the count anyway? If it is tak
On May 08, 2010, at 12:14 AM, Dave DeLong wrote:
> So in a nutshell:
>
> How can I reliably know when dragging begins and ends?
>
> Thanks,
>
> Dave
You can subclass NSOutlineView and call to your delegate on the
NSDraggingSource protocol methods:
- (NSDragOperation)draggingEntered:
- (NSDr
On 08/05/2010, at 2:14 PM, Dave DeLong wrote:
> I could tell all my objects to start caching this count, and then return that
> cached value until I finish dragging.
Why not cache the count anyway? If it is taking a long time to evaluate the
count, caching it will give general performance ben
On May 7, 2010, at 9:14 PM, Dave DeLong wrote:
> How can I reliably know when dragging begins and ends?
NSDraggingSource protocol?
--
Seth Willits
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or modera
Hi everyone,
I've got an outlineView that's displaying some managed objects for me. One of
the properties being displayed is a countForFetchRequest: integer. Whenever
the outlineView reloads, this count is re-evaluated by querying the
managedObjectContext.
I have a problem when I start dragg
