how about a universal abort system?
Sometimes when I accidently set resolution too high, or screw up a simulation, or anything that causes a too-long hangup, I'm forced to close-quit blender window (and tell it not to report a Windows bug) then attempt to recover with an autosave. Some kind of granular setting in Preferences that allows me to chose the trade-off between calculation time and the overhead of checking for user input would be great. I have a feeling though that it may be impossible to set up user abort interrupts at arbitrary depths of calculations/memory requests. But I can sure wish for it!
3 Comments
agreed, but this has been requested numerous times.
blender.community/c/rightclickselect/lRPj/
blender.community/c/rightclickselect/7Zgbbc/
blender.community/c/rightclickselect/3nhbbc/
blender.community/c/rightclickselect/MKgbbc/
blender.community/c/rightclickselect/K2gbbc/
blender.community/c/rightclickselect/g2dbbc/
blender.community/c/rightclickselect/HYcbbc/
etc
etc
They've gone nowhere. You can't expect users to successfully track down every existing suggestion that vaguely resembles theirs when the suggestion could be phrased a hundred ways.
Canceling operations that render the program unresponsive isn't some obscure niche functionality, it's a fundamental QOL feature that should've been implemented years ago. So far requesting it has attracted the interest of maybe two dozen users and produced a sum total of 0 seconds of work. Once a suggestion is older than a few weeks, what potential does it have to be noticed or acted upon? Maybe in five years somebody will ask for a 1000th time and that will be the one that finally gets acknowledged.
good point, let's post 90 proposals on RCS with 5 upvotes each, that'll work much better.