Q Light Controller+

While digging into my problem explained here viewtopic.php?f=5&t=9132 (still appreciating some answers ) another question came to my mind.
When adding a slider in level-mode with "observing" (I still don't know the proper term in english) enabled, I'm not able to control it. It is jumping to 0 immediately. Is this behaviour as expected?
If yes, what would be a typical use case?

This should neither be judicial nor request for a change. I'm simply not able to imagine a use case for a slider I'm not able to use.

I really would appreciate any explanation/example workbench

In fact oberving sliders have the less priority. In your workspace, you have a slider "playback" which holds the function value to a given number, and as it is activated, you cannot really use the other slider. But in the case you have some buttons that allow you to jump to certain values of the channel controlled by your slider, you will be able to use the slider only when all the buttons are unactivated.

At first, thanks for your reply!

Craounch wrote:In fact oberving sliders have the less priority.

That's good to know! "The less priority" towards which other control or is it the least priority in general?

Craounch wrote:In your workspace, you have a slider "playback" which holds the function value to a given number, and as it is activated, you cannot really use the other slider.

That's ok so far, but even if I remove the slider in playback mode vom the vc, the other slider (in level mode) has no effect. Shouldn't in this case the slider in level mode be able to control the level if there is nothing else which controls anything?

Craounch wrote:But in the case you have some buttons that allow you to jump to certain values of the channel controlled by your slider, you will be able to use the slider only when all the buttons are unactivated.

Sorry but I don't get this. There are buttons that can control channels?
"all buttons unactivated" should be equal to "no button is present in the vc", am I right? And in that case I'm not able to move the slider in level mode, neither.

EDIT: Attached a workspace-file with only one slider (level mode, observing active) in vc.

Oh yeah, there is a HTP/LTP problem too...

My explanation works for LTP channels.
For HTP channels, it seems that a permanent "0" value is sent and that makes the slider always "observing" the value 0 instead of observing nothing. So it sticks to 0.

Craounch wrote: For HTP channels, it seems that a permanent "0" value is sent and that makes the slider always "observing" the value 0 instead of observing nothing. So it sticks to 0.

But where does this "0" come from?

Again I'm asking for a use case of this functionality, I'm not able to imagine anything. Especially because in LTP it's impossible to use scenes: On fading it over 0 the value of the controlled channel immediately goes to full on.
I don't know if I got something wrong or approaching this from a completely wrong point

siegmund wrote:Especially because in LTP it's impossible to use scenes: On fading it over 0 the value of the controlled channel immediately goes to full on.

Could you explain a bit more that part ? I didn't understand.

For a use case : look at that workspace - it only contains a fogger. You have some buttons that allow you to quicly jump to predefined settings, but you can also decide to put custom values on your sliders if you disable all the buttons.

Craounch wrote:

siegmund wrote:Especially because in LTP it's impossible to use scenes: On fading it over 0 the value of the controlled channel immediately goes to full on.

Could you explain a bit more that part ? I didn't understand.

Take a lot at the workspace file attached (observing_LTP.qxw): Same situation, one slider in level mode, one in playback mode. Dragging the slider in level mode (with observing enabled) works fine, but when dragging the slider in playback mode, the red channel associated to the red scene will not fade, it goes immediately to 255.

Craounch wrote: For a use case : look at that workspace

ObservingSliderUseCase.qxw
(5.17 KiB) Noch nie heruntergeladen

- it only contains a fogger. You have some buttons that allow you to quicly jump to predefined settings, but you can also decide to put custom values on your sliders if you disable all the buttons.

Ok, got that, thank you!

So everything works as expected by developers, but it wasn't working the way I would attempt to use it.
What came to my mind when I read about that feature first, was to bring the click&go widget and some RGB sliders together. From the widget to the sliders there is no problem when using observing, but the other way seems impossible.
The question remaining to me is: Is there a way to adjust an observing slider, which is "following" a click&go widget?