blocking an input source

[Asmodeus_001]

Hello,

I was wondering what the best/recommended practice is for blocking an input source.

There is a topic from two years ago indicating at some point there would be a null mapping for the remapper array, as at present the null maps to 0/controller 0 and the procedure was instead to map to accel_2_Z instead, is this still the case?


The other ideas I had (in pseudocode not rigorous syntax) were

set_value(input, 0.0)

will this set the value permanently, until another set_value or the like is called or would I need to do something like


if get_value(input -> set_value(input, 0.0)


or while get_value(input) do set_value(input, 0.0)


will this be constantly running and have a noticeable performance drop or cause a lag or stutter?

This seems an inelegant solution.

I know there is also an inhibit command, but according to the reference this requires a time argument

Inhibit (inhibit, 1000)

block it for 1 sec

but is it possible Inhibit (input)

without the time would block it permanently?
or would it have to be

inhibit (gyro_x, 1000)
loop every second forever


this also seems bulky as well.

Also,

I had tried to have two remapper matrices, one for the pedals and one for a stick,

one for port B and one for Port A, and then called them sequentially, but after experimenting it seems you can only have one remapper, and it just takes the last one called. Is this true?

Thanks.

[Mad]

If you want to completely disable both input/output you would use remapper_disable.
You can also create an input translator and remap or disable there.

If you still want input you can use set_val or inhibit both work the same and same amount of bytecode. You can use -1 for permanent block on inhibit.

[DontAtMe]

You can use -1 for permanent block on inhibit.

This is only for the case of buttons.
Values lower than 20% will still register for sticks.