What about keeping track of the current visible groups/fields. You could use
a custom property to store names of fields when shown and delete when
didden. This is a horrible workaround but would save a bit of searching time
because before the search you would know what to search in.
Hi Alan,
In reply to my question regarding a problem with characters from the
extended character set not displaying correctly in a Mac standalone even
though they did display correctly in the stack, Scott Raney answered:
I'm not sure I follow this completely (I don't see how a standalone
could work any
Steve,
I wrote a simple chat program that may help you. You can modify it to send
what ever kind of data you wish. It is commented pretty well to explain
what each section does. If you want it, write me off list and I will e-mail
it over to you.
-Mark Talluto
I had a simple idea but it it
Hi Alan,
A few minutes ago I posted my own temporary solution in message
"finally: effective vis"
before I was able to look at the Metacard digest 196 and your message.
There are some similarities in our solutions, among them breaking the
consecutive number
of "ofs" either by using brackets or
Apparently, a MetaCard standalone cannot "save" itself. All changes made to a
standalone are thus forgotten as soon as the user quits. EVERYTHING is forgotten,
including changes made to the CONTENT of the fields.
The only alternative that I can think of for saving changes made to metacard
