Page 1 of 1

VkbDevCfg + Gl.NXT Prem - Bug with Tm3 mapping?

Posted: Sat Mar 12, 2022 4:24
by analog
Not sure if this is a bug or user error. Can someone please advise? Thank you.

Environment:
NXT Premium "Right Stick". XT v2.0.90
VkbDevCfg v0.92.17

Issue:
Lines in Tm3 physical layer mapping revert to automapped or duplicate values for their logical buttons

Steps to repeat:
map Tempo3 functions to each direction on the A3 HAT (down/up/left/right).
Set mappings as follows
21
#1 --- 21
#2 --- 41
#3 --- 42

22
#1 --- 22
#2 --- 43
#3 --- 44

23
#1 --- 23
#2 --- 45
#3 --- 46

24
#1 --- 24
#2 --- 47
#3 --- 48

Save config

Expected behavior

Tempo 3 mappings are set to the values above
wiz21-before.PNG


What Happened Instead

When using the button mapping wizard, after each mapping is edited, the lines in the cell that were previously edited revert to automapped values in some instances or just different values:

wiz21-after.PNG


In addition, the lines occasionally have the same logical number / mapping. They seem to be linked. Clicking the up / down incrementing control also increments / decrements the line next to it.

Re: VkbDevCfg + Gl.NXT Prem - Bug with Tm3 mapping?

Posted: Sat Mar 12, 2022 4:41
by analog
This is solved for me. I suppose this is user error.

It seems the way to make it work is like the following example for physical button 21:
But2 = 41
#1 -- automapped (21)
#2 -- 41
#3 -- 42