Qtvcp GUI and hal pins

What I still haven't been able to understand is why QTDragon in neither of its two versions can execute subroutines from MDI with o<XXXXX> call, while with AXIS it does execute them. I think, and I'm not wrong, that it's because QTDragon looks for those subroutines in some specific directory different from the one set in the INI in SUBRUTINE_PATH.

If you run qtdragon in debugging mode (-d) and run from a terminal or use debugging mode and look at the system log on the status page you should get more info on where qtdragon is looking to do it's checks when the INI MDI button fails.

Indeed, QTdragon defaults to the linuxcnc/nc_files folder, regardless of the path set in SUBRUTINES_PATH.
Sometimes more information is needed about this, because unlike other GUIs, the path for these subroutines in QTdragon is always the same.
It would also be good to add information on how to use Bridge_HAL and how to connect these new pins to external buttons, thus expanding their use and not limiting them only to inputs that can be controlled through the HALUI pins.
In fact, no online documentation for QTdragon clearly includes this feature.
This might seem very simple to someone experienced with LNC, but from what I constantly read on the forum, there are many people, like myself, who initially don't know how to use these features.

QtDragon doesn't steer the oword/mdi path searches.
It does a check to see if the oword is path is valid from the info in the INI.
But even if the path isn't valid, it still passes it to linuxcnc's motion controller.

linuxcnc searches in this order:
[DISPLAY] PROGRAM_PREFIX
[RS274]SUBROUTINE_PATH
[RS274]USER_M_PATH

The 'File not open' error is from the motion controller not Qtdragon.
Maybe Qtdragon is polluting the command, but i can't know that without more information - like the debugging code I spoke about above.

As for docs...
What do you suggest I could add to this?:
linuxcnc.org/docs/devel/html/gui/qtdragon.html#sec:bridge

Chris

After reading it a bit more closely, I think the current QtDragon documentation regarding Bridge_HAL is clear. It would only be helpful to add an example of the use of Oword subroutines to the [MDI_COMMAND_LIST] section, so it's understood that in addition to macros like G0 Z25;X0 Y0;Z0, subroutines can also be used.

Something I'd like to see, though I'm not sure if it's possible, is that AXIS has some functions that are executed through Key Bindings, which are very restricted in QtDragon. For example, in my case, I designed a control panel with a keyboard and external buttons. AXIS has the function to clear the plot, and if there's an error, a window appears on the screen indicating it. In AXIS, you can simulate closing this window with an external button, but in QtDragon, you can only close it using the mouse or the touchscreen. The same applies to deleting the plot; in QtDragon, you can only delete it by clicking the button.

I just added the ability to clear the display and shutdown the screen with HAL pins to hal_bridge.

It's a start.