I am currently developing a little program to control all the technical stuff around a TV-style game (you know, with candidates, questions, buzzers, sound, video and... light
). When having to deal with the light part came to our mind, I thought "It should be possible to do something with QLC+, it has built-in web access and API through WS...". So I tested to connect my program to QLC+, and it works well : I can get specific widgets from VC and map them to specific events of the game...However (here comes the issue), I found a (very) little issue in the behaviour of the API used to activate/deactivate VCButtons.
QLC+ 4.11.1, W10 64b (but doesn't matter here
)The test page for API ( http://qlcplus.org/Test_Web_API.html ) says something like that :
However, this is not true for Buttons : the value is not taken into account, so when you send your api call, it just presses the button. If it was On, it will be Off, and vice-versa, without looking at the value sent in the call. It might be useful in certains cases to keep the possibility to send an absolute state (ie. the 0/255 = off/on as said on the test page).High rate APIs > Basic widget value set wrote:The value to set depends on the widget type itself. Buttons and Audio triggers will only support values 0 (= off) and 255 (= on) while Sliders will accept all the values in the 0-255 range.
Of course I could not resist, and I looked at the code, all seem to take place here :
- Getting value of the API call : https://github.com/mcallegari/qlcplus/b ... s.cpp#L693
- Dealing the "Button" case without looking at the value : https://github.com/mcallegari/qlcplus/b ... s.cpp#L699
It seems to be nothing (just a few lines of code), I might be able to do it soon (in a few days, after our show
), but I'd like to make sure I don't miss something. Thanks again for the good work here, once again we'll be able to perform a great show with QLC+ !
Sylvain.