Revolution back to HyperCard

Timothy Miller gandalf at
Fri Oct 14 21:04:38 EDT 2005

All true. But, in my experience, most of the time the find stack is 
too darned slow to be useful, even if I limit the search to field 
text-only, and even if I don't check "case sensitive" and so on.

Regarding hyperCard's SS (searchScript) I just did a quick test. 
You're right about searching a stack's scripts. I got 150 hits in a 
few seconds with Rev's find stack. That is indeed faster than SS, 
though SS was always fast enough.

OTOH, Rev's find stack took 90 seconds to find 43 hits in a 
field-text-only search. I previously reported the same search is 59 
times faster with a simple script using the "find" command. If I do a 
field text search using the "find" command in the msg box, hitting 
the return key repeatedly, I can find all 43 hits in less than ten 
seconds -- pretty much as fast as I can hit the return key.

That's why it seems to me that Rev's Find stack should include 
simpler, faster scripts for more specialized purposes, in addition to 
the current complex, versatile script. The user shouldn't have to 
choose between speed and versatility. The user should be able to 
choose either, as needed.



>Agreed the Rev Find and Replace stack is not the same animal as the HC
>however, it allows you to choose to search only fld text, and combine it
>with the power of regular expressions.  For me the real power of this tool
>is to use "script only" chkbox, then a regular expression and get a list of
>all the script containers that match (even in multiple stacks), then dbl
>click to open that script.
>(or use the replace feature to do repair work without opening it, but I find
>that rather dangerous)
>This is much more of a developer tool for scripting and design, than a user
>Remember the "ss" or searchscript command in HC?  Rev Find and Replace is
>really much better and far faster, and more intuitive.
>Jim Ault
>Las Vegas
>On 10/14/05 3:44 PM, "Timothy Miller" <gandalf at>
>>  I have complained here before that the find stack is absurdly slow,
>>  in many instances. In HyperCard, command-f got you the find command.
>>  In Rev, command-f gets you the find stack.
>>  To get the equivalent of hyperCard's command-f in Rev, type command-m
>>  to get the message box. Type 'find "whatever"' or 'find string
>  > "whatever"' or 'find whole "whatever'' and so on. Then hit return.
>>  It's cumbersome, typing the quotation marks and stuff yourself.
>>  Sarah suggested an improvement, which I use constantly.
>>  put the following script in a button:
>>  on mouseUp
>>     go to cd "Single Line" of stack "Message Box"
>>       put "find " & quote & quote into fld "Message Field" \
>>           of cd "Single Line" of stack "Message Box"
>>       put " select char 7 to 6 of fld " & quote & "Message Field" \
>>           & quote & " of cd " & quote & "Single Line" & quote & " 
>>of stack " \
>>           & quote & "Message Box" & quote into tCmd
>>       send tCmd to me in 30 ticks
>>  end mouseUp
>>  It would make sense to label the button "Find". Put copies of this
>>  button wherever you might want a hyperCard-like find. Instead of
>>  command-f, just click the button. The script types the command in the
>>  message box, including quotation marks, and places the cursor between
>>  them, so it's just type and go.
>>  It searches all fields in the top stack, until it gets to the last
>>  card. You can keep hitting return to search for the next instance,
>>  until you find what you want. It starts with the current card, and
>>  stops when it gets to the last card in the stack. If you want to
>>  search all fields in the stack, type command-1 first, to go to the
>>  first card. It doesn't search button contents, scripts, etc., as far
>>  as I know.
>>  The other possibility is to write your own "find" stack. The "find"
>>  command in a script is fast enough. The native Rev find stack is
>>  probably so slow because it tries to do too many things with one
>>  script. Several separate find scripts with more specialized purposes
>  > would likely be much faster. I keep meaning to write a stack like
>>  that, but never find the time. No doubt someone else already has, but
>>  I don't know who.
>>  HTH
>>  Tim
>>>  What you describe there is the find stack.
>>>  The find command simply takes you directly to the card that contains the
>>>  information and hilites it with a rectangle...
>>>  cheers
>>>  Xavier
>>>  use-revolution-bounces at wrote on 13/10/2005 09:39:10:
>>>>   How does the find function works? Does it only list the cards where the
>>>  word
>>>>   searched is found?
>>>>   Thank you very much in advance for your cooperation.
>>>>   _______________________________________________
>>>>   use-revolution mailing list
>>>>   use-revolution at
>>>>   Please visit this url to subscribe, unsubscribe and manage your
>>>>   subscription preferences:
>>>  -----------------------------------------
>>>  Visit us at
>>>  Internet communications are not secure and therefore Clearstream
>>>  International does not accept legal responsibility for the contents of
>>>  this message.
>>>  The information contained in this e-mail is confidential and may be
>>>  legally privileged. It is intended solely for the addressee. If you are
>>>  not the intended recipient, any disclosure, copying, distribution or
>>>  any action taken or omitted to be taken in reliance on it, is
>>>  prohibited and may be unlawful. Any views expressed in this e-mail are
>>>  those of the individual sender, except where the sender specifically
>>>  states them to be the views of Clearstream International or of any of
>>>  its affiliates or subsidiaries.
>>>  _______________________________________________
>>>  use-revolution mailing list
>>>  use-revolution at
>>>  Please visit this url to subscribe, unsubscribe and manage your
>>>  subscription preferences:
>>  _______________________________________________
>>  use-revolution mailing list
>>  use-revolution at
>>  Please visit this url to subscribe, unsubscribe and manage your subscription
>>  preferences:
>use-revolution mailing list
>use-revolution at
>Please visit this url to subscribe, unsubscribe and manage your 
>subscription preferences:

More information about the Use-livecode mailing list