settings of the control

-= JB =- sundown at pacifier.com
Tue Jul 29 11:22:04 CDT 2008


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 and retrieve by a simple start using stack  
> "prefrences.rev" each time your standalone starts up ? I use this  
> way all the time at start time of my Win32 and OSX standalones, to  
> save texts and buttons preferences change states with all the  
> security and confort expected.
>
> No sure, Edimburg would have to set up this kind of features for  
> us, at least ifor me ;-)
>
> Hope this help,
>
> Kind Regards,
> --
> Pierre Sahores
> mobile : 06 03 95 77 70
> www.sahores-conseil.com
>
>
> Le 29 juil. 08 à 17:45, -= JB =- a écrit :
>
>> Here is a question that if it can't be done easily now might
>> be a good idea for a simple improvement to Rev;
>>
>> Let's say I have a stack that uses many different buttons &
>> groups the state of these controls changes during using
>> the program but when I 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 want the hilite to already
>> be set to false even though the last time used it was true.
>>
>> I know in hypercard I would have a group of buttons and
>> fields showing that I didn't want to be showing when the
>> program starts.  So if the program crashed, power failure
>> or the user quit etc. while they were showing they would
>> be showing the next time 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 and false at startup the last setting of
>> the control would be used like they are now.
>>
>> -=>JB<=-
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your  
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>
>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>




More information about the use-livecode mailing list