You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
speeds (or thicknesses, volume of material, etc...) seem to be random rather than in a gradient. as a result it is difficult to read what is happening in a slice.
could you make it in a gradient instead, for example HSV based (hue saturation value) ?
it will make it easier to see at a glance what speed (...etc..) the printing is going at.
thanks again !
The text was updated successfully, but these errors were encountered:
DrLex0
added a commit
to DrLex0/gCodeViewer
that referenced
this issue
Feb 16, 2020
Get rid of the repeating colors and use a gradient instead.
Also sort the speed listings.
Also fix missing initialization of mm^3/sec arrays that caused bogus
values to be displayed.
I bet multiple people have already done something similar in their
forks, but I'd like to see this on http://gcode.ws/.
Hello there !
thanks for the good job on http://gcode.ws !
speeds (or thicknesses, volume of material, etc...) seem to be random rather than in a gradient. as a result it is difficult to read what is happening in a slice.
could you make it in a gradient instead, for example HSV based (hue saturation value) ?
it will make it easier to see at a glance what speed (...etc..) the printing is going at.
thanks again !
The text was updated successfully, but these errors were encountered: