Bug in the 3.2.0.5 API?
Posted: Fri Oct 14, 2022 2:53 pm
Think I found a bug.... on the 3.0.2.5. API. Perhaps it was already there in earlier versions, I never tried so I don't know.
I made a console app that loads the DLL, logs in, sets a button state, waits for a split second, logs out, unloads the DLL, and exits.
When using the API to set the 'Value' on a 'Mode 2P' Macro Button using either VBVMR_MACROBUTTON_MODE_DEFAULT or VBVMR_MACROBUTTON_MODE_TRIGGER, setting a value (either 0.0f or 1.0f, doesn't matter) doesn't clear (0) or set (1), but instead it TOGGLES it.
This makes it difficult to SET or CLEAR the button. I would expect a value of 1 to set it and a value of 0 to clear it. Or is this an incorrect assumption?
When just setting STATEONLY, 1 does set and 0 does clear, but I need "Trigger In" and "Trigger OUT" to run, to set the Button.Color appropriately as I can't do this remotely via the API.
When using this on MODE PUSH buttons, I do see the effect I expect where a 1 sets and a 0 clears.
My usecase is where I want to get the initial button states correct, so from the 'request for initial state', I run my console app that fetches a remote state and tries to set the Macro button state accordingly.
As a workaround, I GET the state and if it is not what I want it to be, I toggle it.
When I manually launch my app that works 10 times out of 10 but when I have the "Request for initial state" run my app, my app runs but the setting often doesn't work.
So actually 2 bugs, one where the set and clear both toggle, and the other where setting (or clearing) during startup often fails.
Any ideas?
Cheers,
David
I made a console app that loads the DLL, logs in, sets a button state, waits for a split second, logs out, unloads the DLL, and exits.
When using the API to set the 'Value' on a 'Mode 2P' Macro Button using either VBVMR_MACROBUTTON_MODE_DEFAULT or VBVMR_MACROBUTTON_MODE_TRIGGER, setting a value (either 0.0f or 1.0f, doesn't matter) doesn't clear (0) or set (1), but instead it TOGGLES it.
This makes it difficult to SET or CLEAR the button. I would expect a value of 1 to set it and a value of 0 to clear it. Or is this an incorrect assumption?
When just setting STATEONLY, 1 does set and 0 does clear, but I need "Trigger In" and "Trigger OUT" to run, to set the Button.Color appropriately as I can't do this remotely via the API.
When using this on MODE PUSH buttons, I do see the effect I expect where a 1 sets and a 0 clears.
My usecase is where I want to get the initial button states correct, so from the 'request for initial state', I run my console app that fetches a remote state and tries to set the Macro button state accordingly.
As a workaround, I GET the state and if it is not what I want it to be, I toggle it.
When I manually launch my app that works 10 times out of 10 but when I have the "Request for initial state" run my app, my app runs but the setting often doesn't work.
So actually 2 bugs, one where the set and clear both toggle, and the other where setting (or clearing) during startup often fails.
Any ideas?
Cheers,
David