On 4/27/06, roozbeh gholizadeh <[EMAIL PROTECTED]> wrote:
> Anyway,is it a good idea to add widetext and widecaption to all wince
> controls?
> Anyway the overhead in wince is using ansistring,becouse the whole system
> is unicode.
I have another idea. To have another property for caption seams just
confusing. Instead, we could have hidden (protected ?) widecaption and
widetext properties.
So, utf-8 or iso widgetsets update the caption and text properties and
utf-16 widgetsets update the widecaption and widetext properties.
And when someone reads Caption or Text on a utf-16 widgetset what
really happens is that LCL converts the widecaption / widetext to
utf-8.
This way we are only converting when we absolutely must convert.
And the same software can use utf-8 accross all platforms. If we have
widecaption public then we have a inconsistency with the "write once,
compile everywhere" principle.
thanks,
--
Felipe Monteiro de Carvalho
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
