Persistent variables?

[22hn]

Sometimes when using variables to store a state of something, I would like that variable to be persistent between EG sessions. I don't want to loose the state just because of an EG restart...

So let's say I have set the variable eg.globals.LightsON = True, is there a way to store that value on EG exit and reload it when EG is started again?

The best would be if I could store the whole collection eg.globals without having to specify each subname...

[stottle]

You have to create a plugin to store variables, as it is the plugin loading that retrieves the previous values.

Within the plugin, you create a class like so:

Code: Select all

class Config(eg.PersistentData):
    position = None
    size = (550, 400)
    splitPosition = 210

The values listed above are the defaults (None, (550, 400), 210), which are overwritten when so set the value to something else.

From then on, Config.position with be whatever it was set to last, even from a previous run of EG. And you can set its value just like a normal variable.

As for storing all of eg.globals, why on earth would you want to do that? You should look at this post regarding that idea....

Good luck.

Brett

[22hn]

Thanks Brett, I'll give it a try...!

Hakan

[krambriw]

Code: Select all

class Config(eg.PersistentData)

STottle, this is great, I have looked for something like this. I have a couple of plug-ins I can upgrade where I currently use Python function pickle for persistent data but this will be much, much simpler

Do you have any idea where the data actually is stored?

Best regards, Walter

[stottle]

On Vista/Win7 it's in C:\Users\<USER>\AppData\Roaming\EventGhost. AppData is a hidden folder, btw....

I forget on XP.

Brett

[Livin]

Would be nice to have a plug-in that created system wide variables any event could set/read and use as a condition.

[22hn]

I've made a first version of a plugin called pVar. (persistent variables)

Works like this:

You can set a variable in two ways.
* Use the action SetGlobalsVar and enter your variable name and value
* In a python script, use eg.plugins.pVar.SetGlobalsVar('varname', value)

This will set eg.globals.varname = value and then save the var/value to yourconfigname.pvar

The next time you start EG, all variables will be restored to it's previous value.

It also checks for obsolete variables (once stored to file but no longer used in your config), and remove those from the pvar file automatically.

[Livin]

I've made a first version of a plugin called pVar. (persistent variables)

Works like this:

You can set a variable in two ways.
* Use the action SetGlobalsVar and enter your variable name and value
* In a python script, use eg.plugins.pVar.SetGlobalsVar('varname', value)

This will set eg.globals.varname = value and then save the var/value to yourconfigname.pvar

The next time you start EG, all variables will be restored to it's previous value.

It also checks for obsolete variables (once stored to file but no longer used in your config), and remove those from the pvar file automatically.

nice job!

I suggest an option for non-persistence on a per variable basis. I can foresee the need to have some variables clear when the session ends.

[22hn]

I suggest an option for non-persistence on a per variable basis. I can foresee the need to have some variables clear when the session ends.

If you don't want the variable to be persistent, don't set it with pVar...!

just set eg.globals.varname = value, then pVar won't save it.

[Livin]

For those not technically inclined (a lot of EG users) it would be nice to provide a GUI to do so and avoid a Python script object. Up to you

[eatmeimadanish]

I get an error when setting a variable to a string. Anyone else having this issue?

Example : NameError: name 'test' is not defined

[eatmeimadanish]

Nevermind, fixed your code that was broken. Here is the new version, remember to delete the .pyc and relaunch EG. This will work for both integers and strings now.