Well first, there is the issue of standalone. I am sure you have seen prior posts, but make sure your actual application stack is not the main stack as the main stack in a standalone will not be editable.
If you set a custom property, either of the card or the stack, it will persist through quit and startup. You only need to create an initialization routine in a pre-openstack or openstack handler to initialize the states of your controls. Bob On Sep 16, 2011, at 7:58 PM, Charles Szasz wrote: > I have an app that consists of a launcher stack and an app stack. In the app > stack, the user uses an Option button to make a selection for mileage > reimbursement rate. Nothing is save in the stack except the User Preferences > in a substack of the app stack. How can I save the user's mileage > reimbursement rate when the app stack is closed so that the mileage rate will > be automatically selected when the app is launched the next time? > > Charles Szasz > [email protected] > > > > > > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
