Blender "long operation" pop-up in case of freeze
Hey, I’ve been working with an addon that involves long loading times (Blosm, which downloads 3D tiles from Google Maps). It took me a while to realize that Blender’s long “freeze” during terrain import was actually normal ( thought it kept crashing)—it was just processing in the background (loading was at least 30 minutes) I know there have been several discussions about adding loading bars in different contexts, and each sparked debate, but I think this is yet another situation where they could be genuinely useful. Maybe Blender's API could let addon devs implement their own warning message?
Example 1 (no percentage)
Example 2: this would be ideal
8 Comments
There's a WIP PR for that here , and a discussion on devtalk here , so the developers seem to be planning to add this eventually.
They also have a WIP feature to support recovering from too long blocking operations #124595
Ah cool! Displaying the text in the status bar seems more elegant (though less visible?), hope this will be implemented as well!
honestly, I feel like the UI should always be responsive... if a long operation is happening it should only lock up the parts of the UI that would disrupt the operation, but maybe that's quite difficult to detect.. I wish the UI was always on a dedicated thread and the program didn't allow taking enough CPU that the entire PC freezes
Obviously cannot disagree, but I suspect this would involve significant work
I've read other thoughts similar to this, and honestly don't understand the thought process.
If I'm doing Operation A and it's taking some time, I can't move on to Operation B until it's complete - because i need the result OF A to continue.
Like - unless it something like "I want to paint a image map, which the phyics are calculating" - which, I think is rather edge case. You'd just be slowing down the physic calculation.
i guess mainly, my goal would be the ability to either:
A. stop, pause, or undo the operation because it's taking too long or
B. save my file just in case it's about to crash
So what's next? Because that's really the goal we need to work toward. Blender needs a rewrite, but I don't know if they'll ever do it... The geometry nodes are taking up too much of their time.