> On Mar 11, 2015, at 3:40 PM, Matthieu Beghin <[email protected]> > wrote: > > if I do nothing in the timer, it's called as often as when a screen is > connected (120 times per second) > if I do some processing, it gets called 20 times per second, but CPU usage > is very low
This sounds like some kind of Qt behavior, not anything intrinsic to OS X. I’m not aware of anything to do with NSTimer that would depend on whether external screens are connected. I wonder if Qt is misusing some kind of CoreGraphics blanking-interval timer that’s meant to be used for animation. Why do you need a timer that gets called that often? —Jens _______________________________________________ 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]
