Qtvcp GUI and hal pins

I can now call macros with external buttons, but unlike the buttons created and displayed on the main screen, which automatically switch QTDRAGON to MDI when clicked, with external buttons you have to manually switch to MDI for them to run. Another problem I'm having is that it can't execute macros defined as `O <XXXXXXXXX> call`. The status screen always shows "File not open," and the terminal debugs this error:

[QTvcp.QTVCP.WIDGETS.ACTION_BUTTON][DEBUG] INI MDI COMMAND #: 7 (action_button.py:717)
[QTvcp.QTVCP.QT_ACTION][DEBUG] COMMAND= O <touch_plate_z> call (qt_action.py:234)
[QTvcp.QTVCP.QT_ACTION][DEBUG] CALL_INI_MDI command:O <touch_plate_z> call (qt_action.py:249)
emc/task/emctask.cc 70: interp_error: File not open
File not open
The path where the macros are executed is defined in SUBROUTINE_PATHS= There are .ngc files to run those macros.

Ok I pushed work to master to allow selecting auto switch to MDI for macro buttons and HAL pin macros on Qtdragon's setting page.

I didn't get a change to push it to the other Qtdragon variations.
I have not looked into the O word problem yet.

Can't see an oword problem, but have added some oword path checks to help to see if it's just a path problem. qtdragon will complain if the oword path is not found.

 This is one of the macros that isn't working for me. I've tried running them with Axis and it won't run either. They work with others, but I don't understand the exact reason.
 

You can't use uppercase letters in oword names

The error when one calls a macro like o<x_touch> call keeps appearing
[QTvcp.COMMON.HAL_GLIB][DEBUG] REQUESTED:{'FUNCTION': 'request_macro_call', 'ARGS': 'ini-mdi-cmd-5'} (hal_glib.py:408)
[QTvcp.QTVCP.WIDGETS.ACTION_BUTTON][DEBUG] INI MDI COMMAND #: 5 (action_button.py:717)
[QTvcp.QTVCP.QT_ACTION][DEBUG] COMMAND= x_touch call (qt_action.py:234)
[QTvcp.QTVCP.QT_ACTION][DEBUG] CALL_INI_MDI command:x_touch call (qt_action.py:249)
emc/task/emctask.cc 70: interp_error: File not open.

I've already verified that the path is correct, and macros of type o<XXXX> call run fine with Axis.
Could it be that, as the error [QTvcp.QTVCP.QT_ACTION][DEBUG] CALL_INI_MDI command:x_touch call] indicates, it's trying to execute the x_touch call command and not o<x_touch> call?