Helge Hafting wrote:
Georg Baum wrote:
Abdelrazak Younes wrote:
Georg Baum wrote:
No. And AFAIK Abdel never claimed that qt4 was fast on linux. Moving
the
scrollbar thumb of the userguide takes several (more than 5) seconds
for
me until it moves with qt4. with gtk there is only a little delay (less
than one second). That is not perfect, but acceptable. qt4 is unusable,
but I don't have the time nor the qt4 knowledge to debug this.
Is this a post or pre-unicode behaviour?
post. And qt3 is not much better. It really looks like the unciode
conversion (at least how it is done currently) is too expensive.
And I though qt supported unicode directly, so there would be no more
conversions while running than there was before unicode.
I am complete a newbie in this field so please take my words with caution.
Qt4 is uses ucs2 and lyx ucs4 so a conversion to/from ucs4 is necessary.
These conversions are supposed to be cheap but
Isn't that
possible with a suitable internal representation of the text strings?
I proposed to use ucs2 conditionally at compile time to avoid the above
conversion but Lars is furiously against that. I really don't know how
we are going to represent an ucs4 characters on screen with Qt4 so I
don't see the reason to use that. Or is there a way to do that?
Abdel.
Of course there might be a one-time conversion when loading the
document, but why is it considered necessary to do conversions while
painting the screen? Does it have to be that way?
IMHO no but as I said I am an ignorant.
Abdel.
