"Slicing Result" panel shows the previous project's numbers after loading a new project and re-slicing
Version: QIDIStudio 02.07.02.10 (Win64), GUI.
Mode: loading a new project over an already-open one, then clicking Slice plate.
Summary
After loading a different project (replacing whatever was previously open) and clicking "Slice plate," the GUI's Slicing Result panel can display the previous project's numbers, byte-identical (same weight/time to the decimal), even though the newly-sliced project has materially different settings and a genuinely different result. There is no loading spinner or refresh failure visible — the panel simply doesn't update, and looks exactly like a normal completed slice.
Repro
- Open project A, slice it, note the reported weight/time in the Slicing Result panel.
- Load project B (different settings, e.g. different layer height — expected to change total time by tens of minutes).
- Click "Slice plate" again.
- Compare the panel's reported numbers to A's.
Expected: the panel reflects project B's actual slice result.
Actual: observed at least one case where the panel still showed project A's exact numbers (4h57m / 114.93g) after B was sliced, when B's real result differed by 66 minutes.
Impact
This is dangerous specifically because a stale-but-plausible result gives no visual signal of failure — it looks like a normal, completed slice. Anyone trusting the panel (rather than re-opening result.json or the gcode header) can act on the wrong numbers, e.g. quoting print time/material to a customer.
Workaround (in use here)
Never trust the Slicing Result panel as the sole source after a project switch — verify from the exported gcode header or File → Export → Export plate sliced file (Metadata/plate_1.gcode) instead. Treat an identical-looking result immediately after a real settings change as a red flag, not confirmation.
Suggested fix
Force the Slicing Result panel to clear/invalidate on project load, and/or tag each displayed result with the project/file it came from so a stale result is visually distinguishable.
"Slicing Result" panel shows the previous project's numbers after loading a new project and re-slicing
Version: QIDIStudio 02.07.02.10 (Win64), GUI.
Mode: loading a new project over an already-open one, then clicking Slice plate.
Summary
After loading a different project (replacing whatever was previously open) and clicking "Slice plate," the GUI's Slicing Result panel can display the previous project's numbers, byte-identical (same weight/time to the decimal), even though the newly-sliced project has materially different settings and a genuinely different result. There is no loading spinner or refresh failure visible — the panel simply doesn't update, and looks exactly like a normal completed slice.
Repro
Expected: the panel reflects project B's actual slice result.
Actual: observed at least one case where the panel still showed project A's exact numbers (4h57m / 114.93g) after B was sliced, when B's real result differed by 66 minutes.
Impact
This is dangerous specifically because a stale-but-plausible result gives no visual signal of failure — it looks like a normal, completed slice. Anyone trusting the panel (rather than re-opening
result.jsonor the gcode header) can act on the wrong numbers, e.g. quoting print time/material to a customer.Workaround (in use here)
Never trust the Slicing Result panel as the sole source after a project switch — verify from the exported gcode header or
File → Export → Export plate sliced file(Metadata/plate_1.gcode) instead. Treat an identical-looking result immediately after a real settings change as a red flag, not confirmation.Suggested fix
Force the Slicing Result panel to clear/invalidate on project load, and/or tag each displayed result with the project/file it came from so a stale result is visually distinguishable.