Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!dali.cs.montana.edu!ogicse!qiclab!percy!tektronix!reed!niski From: niski@reed.edu Newsgroups: comp.sys.mac.hypercard Subject: Re: What comes first the buttons or fields? Message-ID: Date: 11 May 91 00:10:54 GMT References: <1991May1.025303.16314@latcs2.lat.oz.au> Sender: nobody@reed.UUCP Reply-To: niski@reed.bitnet (Joe Niski) Organization: Reed College, Portland, OR Lines: 25 Return-Path: In article <1991May1.025303.16314@latcs2.lat.oz.au> jacob@latcs2.lat.oz.au (Jacob L. Cybulski) writes: >I am writing an application which in response to user actions >constructs the graphics with a lot of buttons and fields for each card. [deletions...] >How can I compare the relative position of buttons and fields, or >force them to assume a particular position without a menu call. >Perhaps there is an alternative way to efficeintly generate buttons >and fields fast? One thing i've done is to create template cards that the user doesn't access by browsing the stack; it's often much faster to trap the "newCard" message, and copy the template card you want into the right spot in the stack; then you can empty fields, or delete buttons, etc. In my not-so-extensive experience, if you have more than 8 buttons & 8 to 10 fields, this is faster than waiting for all those "new button" messages to execute. re: numbering items - if you have a bunch of buttons and delete one or two i think the numbering adjusts. ------------------------------------------------------------------------------- Joe Niski niski@reed.edu Mac Support Coordinator Reed College, Portland, OR 97202 503-777-7525