Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!ut-sally!utah-cs!t-jacobs
From: t-jacobs@utah-cs.UUCP (Tony Jacobs)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: HyperCard feature
Keywords: graphics field
Message-ID: <5224@utah-cs.UUCP>
Date: 27 Jan 88 22:05:32 GMT
References: <702@PT.CS.CMU.EDU> <19563@felix.UUCP>
Reply-To: t-jacobs@cs.utah.edu.UUCP (Tony Jacobs)
Organization: University of Utah ME Dept
Lines: 17


I have found a need in a number of cases for a foreground as apposed to a
background.  In some cases I have wanted a field which changes each time you
enter a card. I don't need or want to use the extra space that a background
field uses. What I did was use a button as a field. Background buttons don't
normally contain different information from card to card where as a background
field does and it uses up more space for more cards.

I'm thinking this forground would be global to the whole stack and not
something you use as a template space for a database like the background is.

You could use this forground to do special filters for any kind of object. The
background has this ability but only if the message gets passed on to it. The
forground would be the first layer in all message paths and could thus
intercept anything, do it's filtering and then pass the message on.

-- 
Tony Jacobs * Center for Engineering Design * U of U * t-jacobs@ced.utah.edu