Path: utzoo!attcan!uunet!wuarchive!zaphod.mps.ohio-state.edu!ub!boulder!serre
From: serre@boulder.Colorado.EDU (SERRE GLENN)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: Getting text into a script (was Re: fields script)
Summary: why not use clickText? -- I'm dense, that's why.  :-)
Keywords: field, script
Message-ID: <28865@boulder.Colorado.EDU>
Date: 29 Oct 90 19:18:01 GMT
References: <485@caslon.cs.arizona.edu> <1990Oct29.002315.3491@sics.se> <28840@boulder.Colorado.EDU> <1990Oct29.143215.10128@sics.se>
Sender: news@boulder.Colorado.EDU
Reply-To: serre@tramp.Colorado.EDU (SERRE GLENN)
Organization: University of Colorado, Boulder
Lines: 18

In article <1990Oct29.143215.10128@sics.se> ollef@sics.se (Olle Furberg) writes:
>  I don't understand why you fool around with this sort of scripts when you
>use HC 2.0. What's wrong with the built-in clickText, clickChunk and clickLine
>functions?

Nothing, except that
1) For non-locked fields one needs a way to start the script. Using
command-click is an easy way (for me) to send a mouseUp to the field (It's 
faster than those mouseWithin handlers).  
2) I have only had HC 2.0 for 1 week (this is an excuse for item 3 below).
3) I was too stupid to try to get the clickText after I had the mouseUp.  

Thanks!  I now send mouseUp with the command-click and then get the 
clickedText.   


--Glenn Serre
serre@tramp.colorado.edu