On May 4, 2020, at 15:33:28, Gabriel Zachmann via Cocoa-dev <cocoa-dev@lists.apple.com> wrote: > >> run in a normal app that can deactivate, hide, minimize, etc, you're >> throwing it all kinds of things it isn't designed to handle. >> >> If you really want to run your screensaver animation in a non-screensaver >> app, you'll need to control the animation, > > 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? 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, call your mix-in class methods from your ScreenSaverView subclass. -- Steve Mills Drummer, Mac geek _______________________________________________ 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
