>>As to your other comments - switching from browse to pointer tool (switching
>>from edit to run) or going to another card forces the object with the
>>current focus to lose focus, so there's nothing technically wrong with the
>>way MC is acting. If you need to store the current selections so that when a
>>card is displayed it will display the selections properly, you can store the
>>hilitedLines in a custom property of the list field and then restore it on
>>openCard.
>
>I see. I guess my HyperCard background caused me to misinterpret
>what I read in the docs. In HyperCard, a field does not loose
>selection when going to another card and back. I need to program
>this behavior in my MC stack.
A followup to the above. I did program this behavior only to find out
that the selected line flashed when OpenCard script ran but then it
got unselected again. To make the story short, I have eventually
figured out that resizing the field (geometry management) causes the
selection to be removed. If I do not do size adjustment, I can go to
another card and come back without loosing the selection.
What I am puzzled about is that the geometry management handler is
called at all. I call it only from the resizeStack handler. Why is
this handler called when I switch cards? It is obviously called after
openCard.
I have once found in the docs what messages and in what order are
sent during some standard events. I can't seem to locate this
information anymore (looking thru index, concepts, and reference).
Robert
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
