Script Improvement Advice

[Stephen Quinn Barncard]

Why hasn't anyone suggested user properties for this? Hidden fields 
aren't needed for this! This is an example of a good use for them....


>Paul,
>
>There's a minor problem with a part of my script...the field is 
>locked. So, in order to edit it, you would have to first unlock it. 
>Sorry...I missed that little detail.  ;=)
>
>Perhaps a better way, anyway (since you would be allowing the "user" 
>to change things), would be to create a text file to hold the data, 
>formatted in the same manner.  On openStack, this file could be 
>opened, read and placed into the hidden field.  Then, remove the "if 
>the oprionKey is down" portion of the code in the card and leave the 
>field hidden.  This approach would also allow the user to save those 
>changes to the text file when he/she closes the stack...assuming 
>you'll be building a standalone from this.
>
>Best Regards,
>
>Tim Ponn
>
>
>Paul Charlesworth wrote:
>
>>Cool! I'll need to read a little more to understand the "getline" 
>>part of the script, but the idea of allowing an end user to edit 
>>the content would be useful if they want a different number of sig 
>>figs for example. Not only that, but it would save me a lot of 
>>"put" and "set" commands.
>>
>>Thanks,
>>
>>Paul
>>
>>
>>On Thursday, June 5, 2003, at 09:12 AM, T. R. Ponn wrote:
>>
>>>Hello Paul,
>>>