> Yikes, that scares me the only thing that actually draws reasonably fast,
> text wise, are fields. If MACR makes them antialiased it would probably
> result in such a big performance hit that I'd have to find a new authoring
> package. I'd be more satisified if they could get on with increased
> performance by text members and just give them the same lingo for access as
> fields use, plus any additional features that text members have. Everytime
> I hear JD say that fields are going to get phased out I cringe. Ever tried
> using an editable text member, everytime the member loses focus and regains
> it, the entire text member's text gets selected. Making them darn near
> completely useless if you want to begin typing at a specific point. Mind you
> I like the fact that they use the proper selection color but I just can't
> use the d@#$ things for anything. Not to mention that a text member can't
> have background transparent ink applied to it while entering text etc.......
Agreed. I use no text members at all. The speed hit is huge if you are
dynamically changing text, parsing text, etc. The minimal window dressing
that anti-aliasing at 12 or 14 points provides is not nearly enough of an
advantage to balance the speed issue.
-Kurt
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
