M62-M65 (or likewise) from qtvcp panel during gcode execution

A real noob on qtvcp I will say

From a qtvcp panel, is it possible to modify the motion.digital-out-xx HAL pins with M62-M65 during AUTO mode, as in when the machine is cutting, without going into MDI mode?

I would like this to have the ability to manually raise or park a Z independent dust shoe during cutting. The dust shoe is normally controlled with M62-65 during tool changes.

So m65 commands operate a dust cover and you want to override the controls manually while in auto mode?

You can control m65 directly while in auto mode other then with gcode.
But could you put some logic components between motion pins and the dust control pins that the control panel can control. Something like an OR component?

Yes, that is exactly what I'm after.

Yes, I have full control over the HAL files. I have actually got it to "work" decent, but it's a bit ugly. I convert both the park and follow command from the qtvcp panel, as well as the digital-out HAL pin to pulses with edge HAL components. The pulses go into or2 components. This way I have one "set" (track) command and one "reset" (park) command, but those are just pulses. I feed those signals into a flipflop component that is then actually controlling the shoe movement. See attached schematic. "ds" is my qtvcp panel, so ds.track and ds.park is the momentary panel buttons. text on the lines are the net names, text over the blocks are the component name. 

It's working, but I get into the situation that the motion.digital-out pin is not reflecting the status of the shoe if overriding it from the panel. It actually is a minor thing, as my M6 remap always park and then activating the shoe again. But I would like to have the motion pin reflecting actual state, just for sanity

edit: adding the attachement
 

Another way that I've used is to create a couple of hal pins (an input and an output) that control the output in the gui python script. Then useing a couple of user defined M-codes to setp the value of input pin to setp the value of the input pin. This was able to allow the either the gui or the G-code to override the other like your flipflop example. Essentially the same thing, except the flipflop lives in the gui code instead of using a hal component.

 
It should have said you can not control. Sorry.