sysop@stech.UUCP (10/26/87)
I thought I'd move this message to the new group, figuring that we ought to use it (we asked for it loudly enough!) Chuq - thanks for your suggestion about using words within a field as an array. As you suggested, I can use before and after to implement a straight-insertion sort. There is, however, one problem that I can forsee. Perhaps you or someone else has a suggestion. The calculations that require the arrays should be invisible to the user. If I use a field to store the data, then that field has to be on a card somewhere. Even if the field is transparent and very small, the first few characters of data will still show up whenever the user looks at the card to which the field is attached. Is there some way to have a totally invisible field? (Pardon my dumbness if I'm overlooking something very obvious here.) Or, is there some way to include a card that a user can never get to? Jan Harrington, sysop Scholastech Telecommunications ihnp4!husc6!amcad!stech!sysop or allegra!stech!sysop ******************************************************************************** Miscellaneous profundity: "No matter where you go, there you are." Buckaroo Banzai ********************************************************************************
chuq@plaid.UUCP (10/29/87)
>The calculations that require the arrays should be invisible to the user. If >I use a field to store the data, then that field has to be on a card somewhere. >Even if the field is transparent and very small, the first few characters of >data will still show up whenever the user looks at the card to which the field >is attached. >Is there some way to have a totally invisible field? (Pardon my dumbness if >I'm overlooking something very obvious here.) Or, is there some way to include >a card that a user can never get to? Fields and buttons have a 'visible' attribute. what you can do is bring up the message box and type: set the visible of background field "field Name" to false And it'll go away. VERY convenient. I also have a script I put in my home stack that will walk through all of the cards and backgrounds of a stack and make everything visible again -- it turns out that once you make something invisible, it is almost impossible to find again. I'll have to upload it in the next couple of days. chuq --- Chuq "Fixed in 4.0" Von Rospach chuq@sun.COM Delphi: CHUQ
russ@hpcea.CE.HP.COM (Russ Thomas) (11/06/87)
Use the command "hide" to make fields or buttons disappear. During
debugging I found it best to have all fields showing so you can see the
values change as your scripts execute. Likewise with "lockscreen".
Once everything works, insert your "hide" and "lockscreen" commands.
-------------------------------------------------------------------------
Russ Thomas UUCP: {...ucbvax!}hplabs!hpcea!russ
HP Corporate Engineering ARPAnet: russ%hpcea@hplabs.hp.com
AT&T: 415-857-2638