🚀 go-pugleaf

In article <1748@watcgl.waterloo.edu> kdmoen@watcgl.UUCP (Doug Moen) writes:

>Here's my problem.  I prefer not to edit the script of every single
>button in my database to add this code.  I have tried putting the code
>into the stack script, where it will be inherited by every button in
>the stack.  This works, but unfortunately, it also gets inherited by fields,
>which is not what I want.  Any suggestions?

You can write a script that will poke the script you want into the buttons.
Put the desired script into a field. Then use 
  get the script of button i
  put newscript after it -- newscript contains the additional code
  set script of button i to it
with the appropriate loops to get you through cards and buttons
You can also be more selective with
  if the name of button i contains the chars "whatever" then set script ...
so you can decide if the button will have the property when you name it.

I haven't tried this, but I think it will work.
--ron.
 Ron Beloin, Ecosystems Research Center, Corson Hall, Cornell, Ithaca,NY 14853
 >> opinions << BITNET:BELOIN@CRNLTHRY; INTERNET:beloin@tcgould.tn.cornell.edu
 >> are mine << UUCP:{cmcl2,shasta,uw-beaver,rochester}!cornell!tcgould!beloin