Bummer.
That means the layer height field(s) should probably be limited to 3 digits as well.
I wouldn't have known without dissecting the gcode output.
Bummer.
That means the layer height field(s) should probably be limited to 3 digits as well.
I wouldn't have known without dissecting the gcode output.
14 hours ago, ahoeben said:CuraEngine works in whole microns internally. A micron is a 1000th of a mm. Making CuraEngine more precise than the micron level is going to take a LOT of refactoring and will likely decrease its performance significantly and/or cause rounding issues elsewhere.
And not to mention a ton of extra memory usage.
I got it. Obviously I am trying to mimic a known profile.
It does surprise me that I didn't get a warning when I entered 0.1925 as a layer thickness and it allowed the entry.
A simple UI fix would make this clear up front.
Where do we submit ongoing bug fixes and enhancements?
https://github.com/ultimaker/cura/issues
Note that in this case, even after 1000 layers, you are still talking about a discrepancy of half a millimeter. Even “splitting hairs” is many times more than the “bug” you are talking about. I don’t think it will get much attention.
It is a matter of completeness in the UI. I have a pet peeve in in that direction coming from that ilk.
Some people care about that 0.5mm. A 1,000 layers is an every day thing under fine settings.
I could go on but it isn't worth the wasted bits in the cyber universe.
Just leave it to say that it would be a fit-n-finish enhancement request.
If something is not correct, it should be fixed. Especially if it is something like this - I suppose Qt (the GUI framework of cura) does have easy options for implementing the right behaviour.
3 hours ago, P3D said:If something is not correct, it should be fixed. Especially if it is something like this - I suppose Qt (the GUI framework of cura) does have easy options for implementing the right behaviour.
Unfortunately, there are always more things that are incorrect then there is time/resources to actually fix them with.
How to implement this (probably): Use http://doc.qt.io/qt-5/qregexpvalidator.html (PyQt4 Code snippet - should also work in the PyQt5 used - see answer to this thread: https://stackoverflow.com/questions/34399485/qlineedit-accepts-only-character-in-pyqt4). I have zero Qt/Cura coding experience unfortunately, otherwise I'd probably just try to fix that myself and commit it to github...
Edited by P3DI've posted the enhancement request at GetHub for an entry field validation.
I'm perfectly fine with the micron level precision now that I know.
Recommended Posts
ahoeben 1,981
CuraEngine works in whole microns internally. A micron is a 1000th of a mm. Making CuraEngine more precise than the micron level is going to take a LOT of refactoring and will likely decrease its performance significantly and/or cause rounding issues elsewhere.
Link to post
Share on other sites