Stored information in rollouts

Submitted by JokerMartini on Sat, 2010-08-14 12:06

How do I take this script and make it work right and it being done efficiently.
This is a small portion of a larger script so ideal I'm hoping to store the information for all the controls in each tab in an efficient way that I'll be able to apply to a larger amount of controls.

Problem:
Once each dialog is (removed) it's values and properties for the controls/spinners/colorpicker, all that information is lost. So when I go to click the create button it does not have the customized controls information stored anywhere. That is where my first idea came into possibly using a structure to store the variables somehow.

I could store the information in Local variables but that could easily and quickly become lengthy. What are your thoughts?

John Martini

AttachmentSize
storeinformation.ms3.62 KB
‹ Scripting-noob has questions WM3_MC_GetMorphPoint. What the?! ›

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Anubis's picture
Submitted by Anubis on Sat, 2010-08-14 18:08.

Hi John, when the rollout is

Hi John, when the rollout is closed/removed the values of its ui controllers is strored (not lost), and you still can get it.

rollout test "test"
(
	edittext edt1 "Type something:"
)
createDialog test
test.edt1.text = "Hello!"
destroyDialog test
test.edt1.text --> "Hello!" (the value is stored)

my recent MAXScripts RSS (archive here)

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.