RelToAbs

[jonasBoss]

needs tests

[jonasBoss]

This should be a good example for a RelToRelHandler

[sezanzeb]

"Remove the Analog Output Axis when specifying an macro or key output"

Is this error message related to this PR? I don't know what to do there

[sezanzeb]

ah, I had to switch to "Key or Macro" and clear the text input. Can we say that in the error message?

Now it shows a different error:

__root__ missing macro or key: the combination = <EventCombination (2, 1, -1)> specifies a key input, but no output macro or key is programmed (type=value_error)

[jonasBoss]

Those have nothing to do with this PR. I created #468 for this, there we can collect all the problematic error messages and fix them.

[sezanzeb]

what should I do about the second error message in order to try the RelToAbs handler out?

[jonasBoss]

You need to configure the input as axis Analog input. Go to the Advanced Input Configuration and set the switch to "Use as Analog"

[sezanzeb]

If no input is used as analog, but the mapping maps to "Analog Axis", can we default to using the first analog input as analog axis?

I think user experience is really one of the most important things in software. If we can somehow make it easier for people to use it I'm all for it.

[jonasBoss]

I can see what I can come up with.

[jonasBoss]

I just updated the GUI. It will now show a message when the user switches between "Key or Macro" and "Analog axis" and it will remove the macro input or the axis input to avoid errors. It is not perfect, the user still needs to update the input accordingly but hopefully it clears up some confusion.

This needs some integration tests.

[jonasBoss]

@sezanzeb can you have another look at this? Should be ready.

[sezanzeb]

great! Thanks. It was easy to set it up

Can you please add a tooltip to "Output Axis" that says something like "Available output axes are affected by the Target setting."? I'll merge it then

[sezanzeb]

I just started working on the new UI, I'll add the tooltip later