Nice logo, Clark ;-)
> 3/23/95
>
> Just wondered if anyone has run into a limit on the number of active
> scrolling-field pointers in MetaCard.
>
> In HC, if you have a number of cards with scrolling fields that have had
> their scroll values set to something other than 0, apparently HC keeps
> only a limited number of those active. It seems that the limit is about
> 15 cards or 30 fields. If one goes to the 16th card in a sequence, the
> card opens with the scrolling fields at 0 scroll and then immediately
> scrolls them to their assigned value. (This causes grief when one is
> "show"ing or printing cards.)
>
> If there is such a limit in MetaCard, perhaps it should/could be setable
> by the user, even if there is a tradeoff choice to make.
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
> Sincerely,
> _ __
> / )/_ _ / /__)_ _ _ _
> (__((// /( / (// _) ()/)_) , MS11
> ======================================================================
> PH: (303) 229-3323 <+> FAX: (303) 229-2838 <+> email: clarkp@fc.hp.com
> "Yes, there is FUN in helpFUlNess, FrUitionN, and thoughtFUlNess?"
> ======================================================================
-- *********************************************************************** * Scott Raney 303-447-3936 Remember: the better you look, * * raney@metacard.com the more you'll see -- Lidia * ***********************************************************************