Hi All, I have a master/detail table setup. When I select a row in the master, there are one or two detail tables that need to be updated. There are also a bunch of conditions that need to be checked to know what you can do to the master and the details. I have just finished a lot of optimization but the act of selecting a row is still a pretty heavy operation. Although I've managed to go from 0.3 seconds to 0.02, I'm still behind the key repeat interval.
I notice that in Mail, if I hold the down arrow and let it repeat, it does *not* update the row until I stop. I don't really know how it does that. My first thought is that I check for a key repeat event in tableViewSelectionDidChange: and skip updating until the user stops. It does not appear to be that easy. Maybe I need to subclass the tableview and handle the keyDown event? That doesn't seem so easy either since I'm using bindings and tableViewSelectionDidChange: is called from NSNotificationCenter via a set of private methods on NSTableView (looks like [NSTableView _doSelectIndexes:byExtendingSelection:indexType:funnelThroughSingleIndexVersion:]). Can anyone point me in the right direction on this? How can I prevent tableViewSelectionDidChange: from being called when the user is holding the up or down arrow and trying to scroll rapidly through the table so I only update when they stop? Thanks a lot Marc _______________________________________________ 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]
