Solo Frames behavior

A place where updates of QLC+ activities and technical articles are posted as if it was a blog
Post Reply

What is the behavior that you prefer ?

Poll ended at Mon Jul 24, 2017 4:22 pm

old behavior (pre 4.11.0)
2
25%
the current behavior
6
75%
 
Total votes: 8
User avatar
mcallegari
Posts: 4807
Joined: Sun Apr 12, 2015 9:09 am
Location: Italy
Real Name: Massimo Callegari
Contact:
Contact mcallegari

I need to write this, cause with 4.11.0 I changed one tiny line of code that made some users unhappy.
Basically it affects the behavior of Buttons in Solo Frames.
For some reasons, over the years we ended up having cases where it was possible to have more than one button active at the same time in a Solo Frame.
While this allowed specific usage cases to be covered, it was clashing with the original idea written in the documentation:
A Solo Frame is almost exactly the same kind of a container as a normal Frame in that can hold various widgets and other frames inside. However, the difference with Solo Frame is that it treats any Buttons inside it differently by allowing only one button to be enabled at a time.
Attached a simple workspace showing what was possible (Chaser and Scenes in a Solo Frame). With 4.11.0 it doesn't work anymore.

So I decided to allow you to vote what you want. My opinion is not relevant here, as what counts the most for me is to have happy QLC+ users.
Attachments
SoloFrame.qxw
(7.38 KiB) Downloaded 653 times
Top
Freasy
Posts: 62
Joined: Sun Jul 12, 2015 2:10 pm
Real Name: Jan F

What about an option to choose what behaviour you want?
Top
User avatar
mcallegari
Posts: 4807
Joined: Sun Apr 12, 2015 9:09 am
Location: Italy
Real Name: Massimo Callegari
Contact:
Contact mcallegari

In this case I would say no.
I can't even image the description for the option in the configuration dialog.
Top
athomsen
Posts: 5
Joined: Sun Jul 12, 2015 2:47 pm
Real Name: Anders Thomsen

As the original author of SoloFrame I can confirm that the way of the current version (>=4.11) is what was intended back in 2010 :)
Top
User avatar
mcallegari
Posts: 4807
Joined: Sun Apr 12, 2015 9:09 am
Location: Italy
Real Name: Massimo Callegari
Contact:
Contact mcallegari

athomsen wrote: ↑Sun Sep 03, 2017 9:31 am As the original author of SoloFrame I can confirm that the way of the current version (>=4.11) is what was intended back in 2010 :)
Hi Anders ! Wow, I didn't even know solo frames were a contribution. I thought they were Heikki's work.
Well, I'm glad after 7 years I finally brought them to what they were supposed to be ! :)
Top
janosvitok
Posts: 1330
Joined: Mon Apr 13, 2015 7:05 am
Location: Bratislava, Slovakia
Real Name: Jano Svitok
Contact:
Contact janosvitok

https://sourceforge.net/p/qlc/mailman/q ... sg26363821
https://github.com/Andersbakken/qlc-svn ... fa0e5355d3
https://github.com/Andersbakken/qlc-svn ... 6a3079eec8

qlc trac seems lost...
Top
steveh
Posts: 2
Joined: Sat Sep 16, 2017 9:48 pm
Real Name:

Hi,

While on the topic of solo frames, something that has been bothering me lately: Can solo frames be set to enforce one of the solo buttons to be active at all times? My use case is as a DJ. I have a solo frame with each button in the solo frame representing a different lighting effect. The buttons are triggered by external midi control. Touching any button switches to that effect. Perfect. The problem is when I hit the same button twice, all the lights turn off (as no effect is active), which makes the room go black, which is bad, and it's quite easy to do.

Is there another way to configure QLC to accomplish this?

If a blackout option were required, one could program one of the solo frame buttons to be 'no effect' (or blackout).

thanks

/steve
Top
siegmund
Posts: 703
Joined: Mon Nov 02, 2015 11:03 am
Location: Germany
Real Name: Lukas

Hey Steve,

as far as I know this is not possible at the moment.
Top
Post Reply

Return to “Blog”