Re: Limit to number of active scrolling field pointers?
Boyd Sweeney ((no email))
Mon, 27 Mar 1995 16:37:50 -0600 (CST)
> Unlike HyperCard, but like SuperCard, MetaCard doesn't retain the
> scroll position and the hilitedLines of a field when a card is closed
> and then reopened. In most cases this doesn't matter, and can even be
> a "feature" in some cases, but it can be annoying if you're flipping
> between documentation cards and trying to compare some paragraph at
> the bottom of some field on both cards.
>
> So, for 2.0 we'd like to consider adding this. Would this be a good
> thing? Should the scroll position and/or the hilitedLines be
> preserved even across closing and reopening the stack? Even across
> exiting and restarting MetaCard?
> Scott
>
It would be nice to have the scroll position retained when moving
between cards. I don't see much of a need to save this property to file
though. The hilitedLines is a different story! I'd like to see this
property persist across closed cards and saved stacks.
One issue that you don't mention is how this would work with fields in
groups displayed on multiple cards. Would the hilitedLines be unique for
the field for each of the cards it appears on? I don't think that it
would work well to have fields without shared text enabled to display the
same text selections.
On the other hand, if I have a list box displayed on multiple cards, I
might want it's selectedLines the be maintained across cards. How about
the addition of a sharedHilite property for fields?
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
_/ Boyd Sweeney Scientist, Nichols Research Corporation _/
_/ sweeneyb@puzzler.nichols.com (205) 955-7292 _/
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/