3 ms·
It works as intended the dev can choose if he wants to invoke NSTerminateNow, NSTerminateCancel or NSTerminateLater if someone hits cmd+q. Writing condescending
by theCrowing 4y ago
It works as intended the dev can choose if he wants to invoke NSTerminateNow, NSTerminateCancel or NSTerminateLater if someone hits cmd+q. Writing condescending comments instead of contributing to the topic is also really helpful. bleh.
- amichail 4y agoMy reason for quitting Podcasts is to reduce CPU usage from the refresh. Having to quit it from Activity Monitor after cmd-q is very annoying.
- theCrowing 4y agoYou can force close it instead of Command+q by using Option+Command+Esc. @anigbrowl looks like the question really was how he can force close it..........
- amichail 4y agoInterestingly, you don't need to force quit in Activity Monitor. After cmd-q in Podcasts, sending a normal quit signal via Activity Monitor works.
- theCrowing 4y agoIt's mainly because Activity Monitor and Force Close Apps send "terminate" instead of the "applicationShouldTerminate" from cmd+q.
- amichail 4y agoThanks for clarifying the issue! I consider this a bug in Podcasts then since a refresh can be very CPU intensive and the user would naturally quit the app to reduce CPU usage but doing that surprisingly doesn't work.