I meant using 2 NumberStates AND also having a RightButton connection. In Shade 1024x768 for example, I only see that on the Play/Pause button.
Let me try to explain the EmitOnDownPress a little bit. The reason you have to have two connections, one with EmitOnDownPress as true and one with false for the hotcues is that when there is a connection with it true, it will set the control to 1 when you hit the button, when it is false, it will set the control to 0 when you release the button.
Some parts of Mixxx require that the control first be set to 1 when the button is pressed, and then it be set to 0 when the button is depressed. That is the reason why some connections need to be doubled with EmitOnDownPress true and false.
It's very silly that the skin.xml mappings work this way, but it's been that way since before I joined the project :).
Jus:
I meant using 2 NumberStates AND also having a RightButton connection. In Shade 1024x768 for example, I only see that on the Play/Pause button.
Let me try to explain the EmitOnDownPress a little bit. The reason you have to have two connections, one with EmitOnDownPress as true and one with false for the hotcues is that when there is a connection with it true, it will set the control to 1 when you hit the button, when it is false, it will set the control to 0 when you release the button.
Some parts of Mixxx require that the control first be set to 1 when the button is pressed, and then it be set to 0 when the button is depressed. That is the reason why some connections need to be doubled with EmitOnDownPress true and false.
It's very silly that the skin.xml mappings work this way, but it's been that way since before I joined the project :).