2.4 Release – bug with saving custom printer settings

[yellowshark 153]

This was OK with the beta versions of 2.4 but does not work with the Release.

I installed 2.4R and setup my custom printer – actually the sequence was 1. Install 2.4R; 2 delete my custom printer files abc.stack.cfg and abc.settings.inst.cfg from the …cura/machine_instances folder ; 3. setup my custom printer definition including importantly my start and end gcode statements– and everything works.

BUT I cannot modify the gcode statements once setup, i.e. I change them, hit the Close button but they are not saved. All the Settings above the gcode boxes are saved if they are changed. If I change the nozzle size and a line of gcode and hit the Close button – when I redisplay the printer settings, the new nozzle size is displayed but the gcode change is not there.

Currently I am changing my z offset statement frequently so this is a real pain as I have to remember to change it in the gcode file.

Fyi @nallath

[ahoeben 2,016]

Something to try: after editing the gcode snippet and before pressing "Ok", use the Tab key to change the focus to anothe control. Then press "ok".

Let me know if that fixes it.

[yellowshark 153]

Hi @ahoeben. I just tried that but it still did not update. I investigated a bit more. I checked the printer file abc_settings.inst.cfg in folder ....cura/machine_instances and saw that the timestamp for the file had been updated. I opened the file and saw that my changed gcode statement had been saved correctly .

I then loaded a model and checked the generated gcode and this was using the old gcode not the new gcode stored in the ....settings.inst.cfg file. Double checking the machine settings in Cura, they were showing the old gcode.

So it seems like the settings are being updated but the file that is saved by Cura is not the file that Cura is using.

[yellowshark 153]

Hi @ahoeben, any progress on this bug? For me at least it is a real PIA