mirror of
https://github.com/Ultimaker/Cura.git
synced 2025-07-06 22:47:29 -06:00
8d13cfb5d6
This way, if travel moves are not currently visible in the layer view, the travel moves don't get counted with the limits to determine the colour spectrum to grade each line with. Quite often, travel moves had a much greater speed than other moves, like 120mm/s instead of the fastest printed line 60mm/s. This caused all of the layer view to be pushed into the lower end of the spectrum. It makes it hard to distinguish the differences in speed and line width because travel moves influence the spectrum so much. This way, the travel moves only influence the spectrum if they are visible. If they are visible, it might be relevant to the user. Otherwise, the user gets the full spectrum to differentiate between all the line widths and speeds. This currently doesn't update correctly yet. That is something we'll need to fix. |
||
|---|---|---|
| .. | ||
| resources | ||
| __init__.py | ||
| layers.shader | ||
| layers3d.shader | ||
| layers3d_shadow.shader | ||
| layers_shadow.shader | ||
| LayerSlider.qml | ||
| NozzleNode.py | ||
| PathSlider.qml | ||
| plugin.json | ||
| SimulationPass.py | ||
| SimulationSliderLabel.qml | ||
| SimulationView.py | ||
| simulationview_composite.shader | ||
| SimulationViewMainComponent.qml | ||
| SimulationViewMenuComponent.qml | ||
| SimulationViewProxy.py | ||