Bug when using multiple "while held" set selector buttons, is this meant to work?

Post Reply
ulti42
Posts: 1
Joined: 26 Feb 2013, 21:20

Bug when using multiple "while held" set selector buttons, is this meant to work?

Post by ulti42 »

Code: Select all

;--- Xpadder Profile File ---
DataType=Profile
Version=2012.05.01

[Profile Settings]

[Set Settings]

[Assignments]
Set1Button1SetSelect=1
Set1Button2SetSelect=2
Set2Button1SetSelect=0
Set2Button2SetSelect=3
Set3Button1SetSelect=3
Set3Button2SetSelect=0
Set4Button1SetSelect=2
Set4Button2SetSelect=1


My profile has four sets:

Set 1 should be active when no buttons are held
Set 2 should be active when the A button is held
Set 3 should be active when the B button is held
Set 4 should be active only when both A and B are held

Start in Set 1 with no buttons held. Pressing A selects Set 2. Now, release A at the same time you press B. As only the B button is currently held, this should select Set 3. However, if your timing is right it will sometimes select Set 4. In other words, it didn't notice that we let go of A and thinks it's still held. Also, if you release B it will go back to Set 2, not Set 1.

Maybe this kind of use was unintended, but it would be great if it were more reliable!
Last edited by Primal Fear on 27 Feb 2013, 23:21, edited 1 time in total.
Reason: wrapped profile into code box


Post Reply

Return to “Sets”