Saving settings

I've taken a look at the NPA file (and removed the link above).  Could you give me a detailed step by step on how to reproduce the problem?  It is a fairly large and impressive project file and I'm not sure where exactly to start.  Also, I'll put the link back after you confirm that you and the customer are ok with it being public.  Or, better yet, cut the project back to the minimum necessary to demonstrate the issue, make it generic, and repost it.  Thanks!

I did notice that previous thread concerning default settings, but no one ever uses the defaultuser account. Usually the pwadmin account is used to make backups that are saved to disk. I was also using the pwadmin account when trying to replicate the problem. The pwadmin account has all privileges. The pwadmin password is nware, the pwtech password is nion.

Here's the process by which I replicate the problem:

The file is deployed and running as normal.

I, or one of the techs, log on. Nware or kiosk is fine. At this point it could be any account save for the defaultuser. No one knows about that account and I'm pretty sure it's never used.

Navigate to the Preset tab and open up one of the preset's setup window. Now, for example, select/unselect some parameters and save the preset. This will cause the preset's script to record the selected parameters' current live settings to a generic string control. If you look under the System tab in the associated preset's block, you should find the string control that is used for storage.

Another way we make/modify Preset data is in the Offline Editor block at the bottom of the Preset tab. If you open that up it will allow you to load and save presets into a set of dummy controls. This allows the modification of presets without disturbing the operation of the park. Either way, live or offline, causes changes in the preset storage strings and the presets' parameter enables, which are just a bunch of boolean generics.

Now, either go online or upload and go online with Nware using the pwadmin account. Save default settings and then save(to disk). As I understand it, this should save the current settings of everything internally in the Nion so that it would reboot into its current state and I now have a backup of the project, with the current state, on my computer.

I would then take this file and emulate it on my laptop. I guess you could also redeploy it, but at the time I could not interrupt the system. In any case, the data *SHOULD* be the same as what is currently running, but it is not.

As far as making the file public, I thought this was a private support forum. Anyway I've never asked the client. If you guys at PDR have it to work with, I guess that's all I need.

Sorry for the confusion about my nomenclature. I am using the term 'preset' as a mechanism that allows the user to store and recall values for a desired set of controls. I do not mean the global or subpreset devices.

Because global/sub preset devices and snapshots did not provide the needed functionality, I wrote a set of scripts to do it. These scripts use a string generic control to hold the stored values. The main problem I am having is when I save the file, the values of these string generic controls don't seem to be saved.

I'll send you an email with a link to the project file.

Ok, so I tinkered around some more and think I may have narrowed it down. It seems that the problem may have something to do with the last time the project was compiled. Here's the test I did:

1. Opened up the project and emulate.

2. Make some changes and note the resulting value in one of the generic string controls.

3. Save default settings and save the file.

4. Close Nware.

5. Open the project up and note the value in the string, which was the same when I saved it. So far so good.

6. Emulate.

The string value reverts back to some older setting.

Now I don't think that is the way things should operate, but I may be wrong. Here's the second test I did:

Repeat steps 1-5. Same results as before, good.

Instead of just emulating, force a recompile and emulate. Now the string value stays the same. This is what I understand should happen but without the recompile.