How to disable buttons in Probe Basic

I am trying to figure out a clean way to disable some buttons in the Probe Basic UI. We currently use an old version on our machine with a few buttons disabled. With the older version, it was as simple as adding something like "self.tool_diameter_probe_Btn.setEnabled(False)" to a properly setup custom_probebasic.py file in the config folder. On the new version installed via apt, this does not work to disable buttons. Our machine gets used by people who may or may not be trained on all aspects of it so I would like to limit some things. I am happy to go and comment out things in order to use buttons when I am working on the machine. Is there a "right" way to do this?

Is your old install with the old version still intact?

Why do you want to upgrade?

What version is the "old version", what version is the "new version"?

I do not mess with working configs. Currently testing on a VM. I'm trying to solve a problem with the old interface locking up after probing.
Your comment is supremely unhelpful. If I was someone who had just broken a working install and I was desperate to get it working again, maybe making them feel dumb is the wrong approach.
Not sure what version of probe basic the old one is but I am testing on the latest available installed via apt based on the documentation.

Perhaps a reinstall of the same version is the solution?

Is the locking up after probing a version-related problem?

Sorry about getting mad, it just annoys me when people totally reinstall over their current system and then can't go back if stuff breaks.

I did not intend to make anybody feel dumb.

A reinstall unfortunately does not solve the issue. I am also not sure that this is a new problem. It looks like the running version is probe-basic_0.5.3-216. We never tried using the probing part of the interface until a few days ago. After the probing routine completes, the ui stays in the busy state indefinitely if I had it set to update the WCO. If it is only set to measure, it works fine. I can find no significant differences between the old and the updated probing routines. Also, probing with my own custom routines works fine. It is only when I click a probing routine on the probing tab with it set to update the WCO that it locks up. If I comment out the G10 line, the ui does not stay locked. I have tried running linuxcnc from the terminal to see if there is any debug output but no luck there either.

I figured that support from the people who make it for what appears to be a bug in a version from 2023 would be a long shot. It is from before installing from apt was even an option. There are also a few modifications I no longer have to do because they have become features. I have not connected the new version to the machine to test if probing behaves the same way yet. Wanted to make sure I could get everything to behave the way we have trained people. I have a little mini pc set aside to for that once I get a copy of the config modified for our machine.

Appreciate that it can be tiresome to see the same stuff repeatedly. Everyone is at a different point in their journey of learning.

I'm guessing your previous install was a version prior to Python 3. The py2 versions worked with a pip install as run in place where apt installs in root. Your custom py file should still work though. It may be a py2 file needed updating to py3?

It is definitely a python 3 version. If I remember correctly, it was shortly after the pip install method stopped working and the install documentation was in a little bit of flux at the time. The new version I am working on does not throw an error when I try to disable a button, It just does nothing.

I will preface this next part by saying that I have just enough skill in reading and understanding code to get into trouble. I haven't used AI stuff because I don't have the skill to double check it. I found when digging through the source that sub call buttons reference issue_mdi.bindOk which references some stuff in the status plugin.

With guess and check I have found that on SubCallButtons I can do this:

STATUS.homed.onValueChanged(lambda: self.probe_spindle_nose_subcallbutton.setEnabled(False))

With this added to the top section of the file:

STATUS = getPlugin('status')

I don't know if this is a good way to do it but it does disable the button.