Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Abdelrazak Younes wrote:
| > Lars Gullik Bjønnes wrote:
| >> Georg Baum
| >> <[EMAIL PROTECTED]>
| >> writes:
| >>
| >> | 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.
| >>
| >> What is a scrollbar thum?
| >>
| >> PageDown - PageUp is quite snappy here.
| >>
| >> (Except that the screend dow not update of course... but you can see
| >> the scroll going on the info line at bottom)
| > By the way, USE_EVENT_PRUNING is still set to 0, do you want me to
| > turn it on for linux.
|
| Or do you prefer this patch? If it works for you I am willing to put
| it in and remove the event pruning code.
Then you would remove the reason for the event pruning code... to
prune events... IMHO two quite different problems.
The event pruning is there to stop scrolling immidiately when I
release PageDown, or stop inserting chars the second I release a key.
I know and with unicode the event pruning may well be necessary again.
But before that it was not necessary at all because repainting was fast
enough (i.e. no need to prune events). Don't you remember that the
UserGuide test was 22s with event pruning and 15 second without?
_BUT_ the problems is related.
| Abdel.
| Index: GuiWorkArea.C
| ===================================================================
| --- GuiWorkArea.C (revision 14809)
| +++ GuiWorkArea.C (working copy)
| @@ -430,7 +430,7 @@
|
| void GuiWorkArea::update(int x, int y, int w, int h)
| {
| - viewport()->update(x, y, w, h);
| + viewport()->repaint(x, y, w, h);
| }
I did test this and it solved most of the problems, but I cannot
remember how event pruning (or really the reverse) got affected by
this.
I'll test it. But I don't have much time today.
OK. I'll wait until you have time then.
Thanks,
Abdel.
