On Fri, 28 Apr 2006 09:35:05 +0330, Micha Nelissen <[EMAIL PROTECTED]>
wrote:
Felipe Monteiro de Carvalho wrote:
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.
Yes, but instead of in the LCL, have it in the interface backend.
Probably the widgetset itself stores it for you, even. I still have to
see these performance problems, until then: write the simple code
(always convert if you have to) and when things are slow *then* we are
going to optimize, and not any earlier.
Well currently as i am working on compiler to fix unalignment problem,i've
seen the codes it produce.
The compiler is generating very general codes and still so far from an
optimized one,so i really dont think using utf-16 can make anything more
slower!
And as i said,being on ansi is always making things slower,becouse of need
to call wince apis,and copying one string to another!
using widestring,might add another performance penalty,but i am pretty
sure it will be still faster than those win api and conversion calls!
We can easily have it on interface backend,but as far as user set captions
in lazarus to ansi properties,i see no use of them.
Yes maybe if we instruct programmer to do text/caption assignment all in
code.
And yes currently we are doing the very same thing,i have to admit i
havent seen any thing being slow,but well i am on emulator still.
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
