I think UI items have a "visible" attribute or something like that. Hiding the item is safer than deleting it if you're planning on making it re-appear later on.

D

David Torno

Legend

Thank you Xavier, for the suggestion. I think I will try to integrate your second example. It seems like the least complicated.

Going through all of this, I am left with the question of how to save the 'state' of the ui when a user "OK"s the window. Since this particular ui is a modal, and has a good deal of user interaction, I want to save the state of the UI so that when they bring it back up, it's as if they never left it. I thought that I would make a global variable that stored an object describing the state of the UI. Is that the best practice?

Pretty good idea Xavier.

I am left with the question of how to save the 'state' of the ui when a user "OK"s the window.

I usually use the native pref file for stuff like this. Depending on the setup I will also use dedicated text docs instead, but that's more involved.

app.settings.haveSetting("myScriptPrefCategory", "myControl"); //Check for saved pref value

app.settings.saveSetting("myScriptPrefCategory", "myControl", "controlValue"); //Saves a pref value

app.settings.getSetting("myScriptPrefCategory", "myControl"); //Retrieves a pref value

Depending on how many controls you are trying to save, you can setup an array of the master control objects, then loop through them grabbing the values. If you have a variety of control types (dropdownlist vs. checkbox) then things get a little more complicated, but still doable.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded