>> >> That is what I'm doing. >> I start my own timer, which periodically calls -animateOneFrame. >> I call -stopAnimation when the app is hidden, etc. > > Are you calling the base class' startAnimation or stopAnimation methods? Or > do you override those and never call the base class?
I override them in my subclass of ScreenSaverView and call those from my app. I never call any method of ScreenSaverView from my app. Well, in my own -startAnimation, I do [super startAnimation]; and in my -initWithFrame:, I do [super initWithFrame ...] and so on. > > In the end, you'd be better off just using your own mix-in class for doing > your own animation. If you still need to build a real screensaver, That's a good question. I was beginning to ponder that myself ... Given the harsh limitations real screensavers have under Catalina (no key events, no access to Photos, ...), I was wondering whether it might be better to implement kind of a "watch dog" that checks whether the user has been idle for some time and then just starts my application. (And any real screensaver would just be turned off in SystemPreferences.) Best regards, Gabriel _______________________________________________ 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
