Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!oberon!pollux.usc.edu!kurtzman
From: kurtzman@pollux.usc.edu (Stephen Kurtzman)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: Wish List item for HyperCard 2.0
Message-ID: <16367@oberon.USC.EDU>
Date: 7 Apr 89 15:02:27 GMT
References: <1100@atux01.UUCP> <89096.04:03:29.AXS101@PSUVM> <1114@atux01.UUCP>
Sender: news@oberon.USC.EDU
Reply-To: kurtzman@pollux.usc.edu (Stephen Kurtzman)
Organization: University of Southern California, Los Angeles, CA
Lines: 34

In article <1114@atux01.UUCP> jlc@atux01.UUCP (J. Collymore) writes:

>The fields that I was referring to are NOT locked text fields, they are fields
>that the user CAN add data to.  HOWEVER, I want to be able to have the field
>sense either a mouseClick, or KeyClick so that it will be able to tell me when a
>user has modified (i.e., tampered with a data in that field)!

Try putting openField and closeField handlers in your field scripts.
For instance, try the following:

on openField
  global oldFieldName,oldText
  put the name of the target into oldFieldName
  put me into oldText
end openField

on closeField
  global oldFieldName,oldText

  -- first check to make sure we have text from the proper field
  if (the name of the target) <> oldFieldName then
    -- the last openField executed was not for this field, so punt
    exit closeField
  endif

  put me into newText

  if newText <> oldText then
   -- do processing for changed data
  endif

end closeField

Hope that helps.