Scripts turns off operations on completion

Archive of the non-categorized posts related to the QLC+ technical support.
Please do not create new threads here, instead, use the categories above !
Post Reply
Jimmy T.
Posts: 20
Joined: Wed Apr 15, 2015 8:28 pm
Location: Douglasville, GA
Real Name: Jimmy Traylor
Contact:

Hi All,

Using 4.9.1 on MAC & Win

I have scripts that stop all my lights then turn on another scene, chase or a series of lights. With this version which I'm now sitting down with the scripts turn on the fixture but then turn them off at the end of the script.

I had to go back to 4.8.5 and it would run the scripts without turning everything off at the end.

Thanks
Jimmy
MAC (OSX)
Windows10
RPi (Raspberry 1.2B+, 2.0B. 3.0B)
ENTTEC USB PRO
User avatar
mcallegari
Posts: 4827
Joined: Sun Apr 12, 2015 9:09 am
Location: Italy
Real Name: Massimo Callegari
Contact:

Hi Jimmy, this is weird cause the last changes on the Script function have been done in Dec 2014.
Can you attach a simple workspace to reproduce what you see ?
Jimmy T.
Posts: 20
Joined: Wed Apr 15, 2015 8:28 pm
Location: Douglasville, GA
Real Name: Jimmy Traylor
Contact:

Mr M.

Here is a sample I did to show it.

1. Press Yellow and light comes on.
2. Press Stop and Yellow should go off and red come on according to the script.
Script Ends and fixtures go off.qxw
(3.35 KiB) Downloaded 54 times
If you put a wait statement in it it will hold until the wait ends.
I'm using chasers as a work-around right now.
Be interested to know whats going on here.

Thanks
MAC (OSX)
Windows10
RPi (Raspberry 1.2B+, 2.0B. 3.0B)
ENTTEC USB PRO
User avatar
mcallegari
Posts: 4827
Joined: Sun Apr 12, 2015 9:09 am
Location: Italy
Real Name: Massimo Callegari
Contact:

Hey Jimmy,
I've checked your project.
What you see is actually the correct behaviour. I know it might look awkward, but here's the techy insight:
A Script is a Function like all the others in QLC+. Internally, it keeps track of the (children) Functions it starts.
When the whole Script code has been processed, all the Functions ran by the Script are stopped, thus triggering the Script stop event as well

If a Script wouldn't do that, you would have running functions in QLC+ that you can't stop anymore from the Virtual Console, except by using the Stop All button (which might stop also Functions that you don't want to stop)

So basically the concept of a Script is that when it ends, QLC+ goes back to the state it was before running the Script.
User avatar
lorenzoandreani
Posts: 101
Joined: Tue Sep 01, 2015 9:19 am
Location: Marina di Carrara
Real Name: Lorenzo Andreani

Ok, that's right!

It's possible add a command, in the script, to remains active until the button (who initiated the script) is clicked again (or slider goes to 0) ?
plugz
Posts: 637
Joined: Sun Apr 12, 2015 6:30 pm
Real Name: David

You can put a wait at the end, with a big number.
User avatar
lorenzoandreani
Posts: 101
Joined: Tue Sep 01, 2015 9:19 am
Location: Marina di Carrara
Real Name: Lorenzo Andreani

Yes, i know it is, but not the same thing (also it takes an active timer).

For now i have bypassed it by inserting the script in a collection.
Attachments
Script Ends and fixtures go off.qxw
(3.38 KiB) Downloaded 55 times
Post Reply