Cura: Is there a way to NOT to recalculate the printing time immediately during the sizing number is changed?

[Rejutka 4]

Great as cura is, it's bothersome that whenever I change the size of a model, it immediately starts to recalculate the printing time - I haven't even finished deleting the previous numbers, and it already starts, almost freezing my computer.

Couldn't it wait until I leave the input field?

Sorry to start posting with a complaint - but you know how it is - most people don't bother complaining about things that don't really interest them :-)

[Nicolinux 288]

Sadly you can't. But this is a good idea for a future version.

[nallath 1,124]

Well, it shouldn't freeze up your computer. We have some changes in the newest version that should solve that issue (eg; it will still re-calculate, but it shouldn't freeze the GUI as much / anymore)

[neotko 1,417]

I really don't get the idea behind the recalculation because:

It don't show the gcode preview fast enough, it doesn't show a ghost of how it was before, and most of the time automagicall stuff it's not user friendly.

Let me do a control-z to see a fast view of the gcode of how it was before with a history, then we talk

And options that are forces to the user, without the posibility to disable it, create a psycological negative response.

Please, I beg ultimaker, get a UI master, he will teach you how to develop and create how thinks work.

I been working 15 years as graphic designer and I can smell a user interface made by programers and coders by a mile. You must stop thinking as programers and think as a user, and for that there are experts of usability, ergonomics. You don't need something beautifull, but with a good foundation.

[nallath 1,124]

Please, I beg ultimaker, get a UI master, he will teach you how to develop and create how thinks work.

 

We have multiple people working on this. This is why @ahoeben is now working for us. So you are definitely wrong with respect to the interface being made by programmers / coders (The old Cura was, the new one is not)

 

You must stop thinking as programers and think as a user, and for that there are experts of usability, ergonomics.

 

I've actually been trained as both. I don't claim to know the 'truth' about how these things should be done, but I know of no explicit reason why (from the perspective of the user) we should disable certain automatic proceses.

All that being said; I'd like to extend an open invitation for anyone to work on Cura. Just because Ultimaker decides certain things does not mean that Cura -has- to be in a certain way. Design changes could also be contributed by people in the comunity.

[neotko 1,417]

No, there's no truth, that's the first truth. Also it's a matter of felling it.

When something starts to works behind the user, it does a psychological distress. That's why automatic stuff, should be allowed to be disabled. It creates the subconscious need to do it right. Specially since the computer starts to freeze (something you said that will be fixed).

What I would do?

If it's a imperative to have it working, let it work, but with two notes. Don't tell the user, let it run behind, don't slow down UI, and when the user press 'Generated gcode, print, any term you prefer' then, you show the gcode, and if it's still working, just show the %. This way you hide the generation and urge to 'go go go' and also you show a faster gcoding process, since it was already working.

This it's like the big range of options that are hidden and must be click click click click to infinity to show all hidden. And when you do, they are very weirdly organized. I tryed to make a rearrange screen with all the options but lately I'm bottle up with all this new shop and orders.

Anyhow, that's my 5cents. I might be wrong ofc, but it's a 'felling' you get when you start to use something. It works, it flows, or you get stuck and you need a manual.

Also... Cura need's a manual. Even simplify3d that never had anything documented, they after a year did a series of posts on forums explaining all their options. It's a long read, but it can be read.

And also, old cura, it's light years from the user side than the new cura, sorry, but it was focused on working, not looking good, and it works and it lets the user use it. And what I mean by programers style, it's the need to PUT PUT PUT PUT info info info info, and not just, the important info, correctly shorted on a manner that one user can access to it, not 3 scroll downs, lots of clicks, many options capped, and stuff that can only be modified by editing outside the program. That's what I mean =)

Edited January 18, 2016 by Guest