If only we had proper Lua global variables

[robmac 173]

If only global variables were available. Why not?

Please login or register to see this code.

[Bamsefar 13]

Not 100% sure what you are after? The time it takes to write to the global variable, or?

[robmac 173]

You can not store lua reference in a Fibaro style global variable. But proper lua state is not maintained across instances of a scene.

The setTimeout(lua state, int). Passes the state as a hidden parameter.

Now if when a new instance of a scene was created it is given the state of the instances running we would have global across instances of the same scene. So

Please login or register to see this code.

Would not be maintained as it would be scene instance environment specific but

Please login or register to see this code.

Would be

So in my example the ref to the first timeout woul be available to a second instance of the scene that could cancel it.

It would be a matter of on creation of a new instance of a scene passing the state shared by current instances to the new instance.

I can create a plugin to do this generic turnoff after delay but it would be more flexible from a scene

[petergebruers 1,268]

I'd say a form of message passing between scenes or scene instances (not counting setglobalvariable) would allow for cleaner code. I'm experimenting with a different usage pattern: create a main scene that does state detection and a slave scene that does tiling and use killscene to abort the timer. It works, but is doesn't look nice.

[robmac 173]

Hi,

Yes that is what I put in a couple of years ago. The logic here is for if the machine is switched on off and then on again so that the counter is restarted. Similar idea though.

master

Please login or register to see this code.

slave

Please login or register to see this code.

Was wanting to tidy it up.

Do you think killing a scene that has a setTimeout registered is safe? I think I may leave as is.

[petergebruers 1,268]

The logic here is for if the machine is switched on off and then on again so that the counter is restarted.

Yes, that is quite similar to what I am trying now. I see no real objection to starting/killing scenes. I am also not religiously against splitting up code over 2, 3 or more scenes. But I share with this "uneasy feeling":

Do you think killing a scene that has a setTimeout registered is safe?

Well... I found out that when your scene has no more work to do, except for some setTimout job, it is still running. It will die only when the function registered with the setTimout exits. But that of course doesn't guarantee that cleanup of aborted scenes is working.

You know what? This calls for a HC2 torture test!

Please login or register to see this image.

/emoticons/default_icon_cool.gif" alt="8-)" /> I'll do some experiments and I'll try to answer your question...

[robmac 173]

Yes I noticed a new property killable so I am not surprised that it does not die. Think I will leave them with sleep as I know that is safe.

I think it is plugin time to make it tidy but that will have to wait for a while.

[petergebruers 1,268]

As promised... a simple stress test

Please login or register to see this image.

/emoticons/default_icon_smile.gif" alt=":-)" />

Please login or register to see this link.

Didn't want to hijack your thread.