Hi Torsten- You might consider something like the coalescing described in this blog entry:
http://www.takingnotes.co/blog/2013/01/03/coalescing/ In short, you'd be using performSelector:withObject:afterDelay: to make the desired method call, and cancelPreviousPerformRequestsWithTarget:selector:object: to prevent the calls from piling up. Hope this helps! John On May 28, 2013, at 8:41 AM, Torsten Curdt <[email protected]> wrote: >> Quick question: how often are you calling setValue:? Every time it changes >> or is it inside an NSTimer/CADisplayLink? > > Every time the user moves the slider. > >> Can you give us more information on this particular flow? > > If I execute the "setValue:" on each value change of the slider the UI > feels too slow. > > What I currently have in mind is to just store the latest value. Then > enqueue "update" calls in an async queue and in the update blocks only > perform the update if the value is different from the previous/current > one. > Any easier or more elegant way you could think of? > > cheers, > Torsten > _______________________________________________ > > 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/john%40positivespinmedia.com > > This email sent to [email protected] _______________________________________________ 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]
