Problems trying to customize safe_height.setRange(...) via qtplasmac_custom.py

Hi all-

I'm trying to enable qtplasmac to allow a safe_height smaller than 0.75 inches. I followed the basic gist of the advice at forum.linuxcnc.org/plasma-laser/51568-in...xcnc?start=10#297618 which suggests something like the following in a file named qtplasmac_custom.py in the config directory:with my specific line in the qtplasmac_custom.py file being:
I have customized a label in the same qtplasmac_custom.py file, so I think that shows that the qtplasmac_custom.py file is being processed via github.com/LinuxCNC/linuxcnc/blob/56e137...smac_handler.py#L365.

However, I see that the self.set_spinbox_parameters() call happens in that same method but later:

github.com/LinuxCNC/linuxcnc/blob/56e137...smac_handler.py#L380

and it is in the the set_spinbox_parameters method where the regular setting of the safe_height setRange happens: self.w.safe_height.setRange(0.75, int(self.maxHeight))

github.com/LinuxCNC/linuxcnc/blob/56e137...mac_handler.py#L3238

I am wondering due to this call sequence if actually is possible to override the safe_height.setRange(), or if I'm doing something wrong.

Thanks!

Scott

Thanks for the explanation. I'll try this and report back.

This worked half way. I added a USER_COMMAND_FILE = qtplasmac_custom_post.py with the python code to set the range:

self.w.safe_height.setRange(0.125, int(self.maxHeight))

I can start QtPlasmaC and interactively set and save a Safe Height value as low as 0.125". However, if I save any value less that 0.75", when I reload QtPlasmaC the value is reset to 2" (my maxHeight).

I think this is happening because the load_plasma_parameters method that loads the value from the prefs file into memory (github.com/LinuxCNC/linuxcnc/blob/56e137...py#L2901C16-L2901C27) happens after set_spinbox_parameters which sets the defaults but before the USER_COMMAND_FILE (I'm not yet sure how that file gets invoked with QtPlasmaC to be honest).

This leaves me at a bit of a loss as to how to customize this. I could just write a sed script to change the python code for now, but that seems like a bit of a hack. Anyone have other thoughts as to how this might be achieved?

Thanks!

Scott

Thanks Phillip! I thought of something to try and hopefully I'll be at the machine later today to try this. If I re-set the safe height from the prefs after changing the range in the USER_COMMAND_FILE then I think it should work fine.

So then the user command file would be:
I'll let you know of that works, so no need for you to try and come up with something for now, but thank you!

Scott

I was on the right track with the idea above, but it still did not fully work. Since the self.load_plasma_parameters() call also happened before the self.w.safe_height.setRange(...) call the in-memory prefs data was still respecting the built-in safe_height range that was in effect when it was initially loaded. The solution is to call self.load_plasma_parameters() again after updating the safe_height.setRange.

That worked. I could change, save, and reload Safe Height values below 0.75".
But looking at this now I think I could ditch the explicit self.w.safe_height.setValue(..) call since that is already being called in the self.load_plasma_parameters(). I'll try that next time I'm at the machine, but the good news is I think there is a way to customize the Safe Height using the stock customizations methods.

Thanks for the help Phillip!

Scott

I confirmed that just the following in a USER_COMMAND_FILE works:

Thanks!

Scott