qtdragon pins?

Ok sure. Could you post the error message?

I don't have any error message.
QtDragon starts normally but the HAL pins aren't created as defined in "qtdragon_handler.py".
Furthermore, It seems that the HAL pins from a former test file are still there.
They don't disappear even when I delete "qtdragon_handler.py" and "resources.py" files in the directory /..../qtvcp/screens/qtdragon/
Is a "reset" required in some kind of way?
Or do I need to force the reading of "qtdragon_handler.py". somewhere?

I added the slider "MAX_VEL_OVERALL?
Can you check if I did well for this slider?
Is here another definition required for "MAX_VEL_OVERALL"?
    def init_pins(self):
        super().init_pins()
        self.FEED_RATE_ENABLE = 0
        self.SPINDLE_RATE_ENABLE = 0
        self.ANGULAR_JOG_RATE_ENABLE = 0
        self.JOG_RATE_ENABLE = 0
        self.RAPID_RATE_ENABLE = 0
self. ????? = 0
 

I seem to be  wrong, the widgets are named the same. I tested and the script work for both GUIs.
I fix the max velocity pin name in this version.

I see the 'turtle' pins still set the rate too high or too low in your version. One of the versions I posted has that fixed.

if you run linuxcnc from a terminal and change the INI to add -i (ie DISPLAY = qtvcp -i qtdragon)
It  will tell you the path of the files you are using. Makes it easy to make sure it's using the file you wanted.

If you get extra pins then qtvcp is loading a modified handler file somewhere.

Turtle pin: One of your posted version had that fixed?
You mean
self.w.btn_jog_a_slow.setChecked(not state) which I changed into
self.w.btn_jog_a_slow.clicked.emit(state)?
then it is just the other way around, no?

BUT: It works! Thanks! QtDragon and QtDragon_hd are functional.
I don't know why thou. I loaded with the -i option and everything seemed ok to me.
So I started playing around with remap M6 (which didn't work at that moment) and suddenly QtDragon started also perfectly.

REMAP M6:
The docu in linuxcnc.org/docs/html/gui/qtdragon.html#_user_tab is not clear concerning the SUBROUTINE_PATH.
The sim.qtdragon.qtdragon_tool_probe has set me on the right track.
Almost there, but not quite..
(Fault when touching of during M6 Tx measurement)