the program was started. To
correct it on openstack I would check their visibility and
if it was true I would hide them.
What would be nice is each control had an option that
could be checked true or false. If it was true they way
you had the settings of the control would always be
used at startup
the program was started. To
correct it on openstack I would check their visibility and
if it was true I would hide them.
What would be nice is each control had an option that
could be checked true or false. If it was true they way
you had the settings of the control would always be
used at startup
Thanks, it looks like I will take your good advice. But
it would be nice to be able to just make it a selection
with the other control settings.
-=JB=-
On Jul 29, 2008, at 9:06 AM, Pierre Sahores wrote:
JB,
Why don't you report the objects hilite state to a preference stack
you can save
in a given part of the app, and sets the
necessary properties.
Best,
Mark
On 29 Jul 2008, at 17:22, -= JB =- wrote:
Thanks, it looks like I will take your good advice. But
it would be nice to be able to just make it a selection
with the other control settings.
-=JB=-
On Jul 29, 2008, at 9
quit and restart I want the original
control settings to be opened with the rather than settings
the user changed the last time he/she used it.
For instance I might have a button the user clicks it sets
the hilite true and the user does what they want, quits and
then starts the program up again I
the original
control settings to be opened with the rather than settings
the user changed the last time he/she used it.
For instance I might have a button the user clicks it sets
the hilite true and the user does what they want, quits and
then starts the program up again I want the hilite to already
