The slicing is a background process. For the most part that is. Python is inherently single threaded (or well; it has multiple threads, but only one of them is active at any given moment). The slicing itself is a stand alone process.
So the sending of the data is the only task that could block the GUI from reacting. We have some ideas how to fix that in the future, by not re-sending the model every time something is changed, but simply sending changed rotation / scale / position together with settings. This would save pumping over a ton of data every time. Such a change would also allow for faster slicing, as we don't have to re-calculate everything every single time.
Recommended Posts
SkyKorp 6
Sometimes you can solve things in ways the user would never think about...
Just like the nest thermostat you can log the user's interactions and make good guesses on how to leverage the computer resources based on facet count, model size, toolpath settings. If my model is large and complex, and I type an extra zero for layer height, I will wait and crash no doubt.
You could keep auto slicing on as you wish, but change the hooks to the UI so cura never disrupts the user's visual focus. Keep it a background process. Then , when a click the button, it is so fast because it is already queued and ready.
It reminds me of a time I optimized a startup routine such that the the company brand and logo flashed so instantly, that marketing had a fit saying I killed the built in commercial at bootup time. I fought it and lost, and it kills me to this day to see this device slow bootup when I know just a counter inside I replaced it with. Haha.
A feature isn't a feature unless there is value. Otherwise it is technical debt.
The same is also said of audio design in games. If someone finds it good they don't notice it, but if they find it bad, all hell breaks loose. I've used cura back in the day where the auto slicing wasn't an option yet (you had to press the slice button every time), which was fairly annoying. I think the current problem with the auto slicing is that the message pops up and pops down again, which is quite distracting.
For all the developers shouting that they want this feature, I've yet to see a pull request. We're considering adding an energy saving mode which disables auto slicing, but due to the feature freeze we're in at the moment, it won't be added until the 16.01 release.
I don't think this has anything to do with bravery so i don't quite understand what that has anything to do with this discussion.
Link to post
Share on other sites