On May 05, 2016, at 10:07 AM, Ken Thomases <k...@codeweavers.com> wrote:
Well, my only suggestion was to set usesThreadedAnimation to NO. It may be that that causes Cocoa to use a timer internally, but you shouldn't be doing anything explicit with a timer with respect to the progress indicator. Yes, we only did usesThreadedAnimation:NO - nothing weird. Don't do that. You must always shunt such work to the main thread. Hmm. Has that always been the case with OS X and/or Cocoa? I know an app should not do any drawing from anything but the main thread, but I thought that all the cocoa controls were smart enough to not draw directly when their set* methods are called. E.g., calling setStringValue will set the internal string and do nothing more than call setNeedsDisplay:YES, deferring drawing to the next time the main thread gets some time. Did I forget or never learn something more critical than that? Sent from iCloud's ridiculous UI, so, sorry about the formatting _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
