Qtvcp GUI and hal pins

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?

No that is an error of the logger color formatter. I have pushed a fix for that now.

That type of instruction executes correctly; the problem only occurs when executing one of type o<XXXX>. I tried executing it from the MDI in the form o<xxxxx> call and it also gives me an error.

Thank you for your support. One more silly question: how do I get updates? By updating to the latest version 2.10 of LNC?

I actually don't know - I always use run-in-place compiled version.

Hopefullt someone else will chime in to help.

But ye the latest 2.10 (master) branch should have the latest code.s

To update to master in Debian 12, add an entry to /etc/apt/sources.list
deb buildbot2.highlab.com/debian/ bookworm master-uspace 2.9-uspace
then apt update ; apt upgrade