mirror of
https://github.com/Ultimaker/Cura.git
synced 2025-07-06 22:47:29 -06:00
96ca3b1417
Instead of re-uploading the mesh each time the range changes, handle the range in the shaders with the new draw-range parameters. This does however, mean the range has to be in vertices, not in elements. This necessitates some changes to the simulation-view, and some added bits deeper in the base code. Mainly, since each time the type of a line changes, there is an extra vertex, there needs to be a type-change count available to get from 'paths' to range indices. |
||
|---|---|---|
| .. | ||
| 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 | ||