Helge Hafting <[EMAIL PROTECTED]> writes:
| 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. Isn't that
| possible with a suitable internal representation of the text strings?
|
| 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?
If we are to retain the ability to have different frontends: yes.
If we are to have the ability to support all of unicode: yes.
Qt does not support full unicode, the lyx core does.
(ucs-2 vs. ucs-4)
And my scrolling is quite fast, mouse or keybord.
It is far from as fast as xforms were, but absolutely usable.
--
Lgb
