Saving configuration changes
Posted: 30 May 2014 10:26
I know Lemur does not have any file I/O support built in. However, I want a user to be able to save configuration information specific to a template. For example, it would be nice if the user could select a MIDI Target, MIDI Channel, (and in my case) a specific Device ID for the gear at the other end of the wire.
I would have thought that if the user went into the Lemur menu and saved the template back to the same name, it would preserve everything that has been changed, but that doesn't seem to be the case.
So, what exactly does Lemur save when you overwrite an existing template on the iPad?
Does it matter if the variables have pre-set values or if the template starts up with them uninitialized and then subsequently sets them?
Are vectors treated differently than singletons?
Are object attributes and expression variables treated different than user defined variables?
thanks for any insights. It would be nice if a user didn't have to worry with editing the template in an editor just to select a different MIDI Target or MIDI channel every time the template started up.
I would have thought that if the user went into the Lemur menu and saved the template back to the same name, it would preserve everything that has been changed, but that doesn't seem to be the case.
So, what exactly does Lemur save when you overwrite an existing template on the iPad?
Does it matter if the variables have pre-set values or if the template starts up with them uninitialized and then subsequently sets them?
Are vectors treated differently than singletons?
Are object attributes and expression variables treated different than user defined variables?
thanks for any insights. It would be nice if a user didn't have to worry with editing the template in an editor just to select a different MIDI Target or MIDI channel every time the template started up.