jogging after homing

Before homing you are jogging "joints" (0 , 1, 2,...)
After homing you are jogging axes (x, y, z, ....) , which run through the kinematics module, to calculate joint positions.
For a cartesian setup this distinction might seem pointless, but it save ambiguity in a lot of parts of the code.

Your jogging setup might be more convoluted than necessary.
If you _must_ use GUI buttons for jogging (hardware buttons are more reliable) then I would suggest using HAL buttons (ie, GUI elements that toggle a HAL pin) then wiring those HAL pins to the HAL jog inputs that operate independently of the GUI code.
The absolute most reliable way to jog is using MPGs that send counts to the "motion" module jog-counts pins. That is realtime all the way.
But if you want increment/continuous jogging from a button then you can use the "halui" pins.


The reason that I dislike keyboard jogging (which you are emulating, in some ways) is that it is possible for the GUI to miss the "key-up" event, and then the axis doesn't stop when you release the key.

Anyway, if using the halui inputs the answer to your original question is to wire the input to both joint and axis.

pseudo-code (I haven't checked what the actual GUI putput pin would be called)