Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: HITextView vs naked TXNObject


On Nov 27, 2004, at 6:24 PM, Jan Brittenson wrote:

I've run into a few cases where I want an EditText control, except
with unicode/MLTE handling instead of ASCII.  So I looked through
the TXN* interfaces in the MLTE docs, and am wondering if there's
any reason other than pre-10.3 compatibility why I should use these
directly rather than an HITextView?  They seem to have the same
TXNObject under the hood, and the HITextView in addition plays
nice with other HIView's.  The limitations in the HITV TXNObject
don't seem that onerous to me.  Plus it would allow me to factor
the code more cleanly with only one set of interfaces.  I guess I'm
wondering what the additional HITextView overhead is if any, and
whether HITextView is suitable for many small text fields like
name and address entry.

As Fred said, if all you need is a simple "edit field" control then the best option is the Unicode Edit Text Control. It's ideal for single line, single style, input.

Otherwise, to answer your question, there's no reason at all not to use HITextView over TXNObject that I can think of. The advantage of having a TXNObject fully wrapped in a view and supporting the various view semantics out of the box are more than worth any tiny bit of overhead (if any really) that the HITextView might impose.

Bryan

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden

This email sent to email@hidden
References: 
 >HITextView vs naked TXNObject (From: Jan Brittenson <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.