Peter Kümmel wrote:
I've applied attached patch which only eats page up/down keys on x11
and fixes the scrollbar scrolling bug. This is a conservative approach.
And because we really need more testing until the release it
is now in svn (I know, I know, I know,... but somehow this
thread must fin
Dov Feldstern wrote:
> Peter Kümmel wrote:
>> I've applied attached patch which only eats page up/down keys on x11
>> and fixes the scrollbar scrolling bug. This is a conservative approach.
>>
>> And because we really need more testing until the release it
>> is now in svn (I know, I know, I know,.
Peter Kümmel wrote:
I've applied attached patch which only eats page up/down keys on x11
and fixes the scrollbar scrolling bug. This is a conservative approach.
And because we really need more testing until the release it
is now in svn (I know, I know, I know,... but somehow this
thread must fin
I've applied attached patch which only eats page up/down keys on x11
and fixes the scrollbar scrolling bug. This is a conservative approach.
And because we really need more testing until the release it
is now in svn (I know, I know, I know,... but somehow this
thread must find an end, and we could
On Fri, Jun 01, 2007 at 01:44:32PM +0300, Martin Vermeer wrote:
> On Thu, May 31, 2007 at 11:22:56PM +0200, Lars Gullik Bjønnes wrote:
...
> > | keys, and Martin had a counter-argument, 'word completion':
> >
> > then put my queue of events back in and we can controll the events
> > ourselves. q
On Thu, May 31, 2007 at 11:22:56PM +0200, Lars Gullik Bjønnes wrote:
> Peter Kümmel <[EMAIL PROTECTED]> writes:
>
> | Peter Kümmel wrote:
> | >> | Or happens the dropping only to auto repeated keys?
> | >>
> | >> Only auto-repeated keys.
> | >
> | > OK, if you are really sure only auto-repeated k
Lars Gullik Bjønnes wrote:
> Peter Kümmel <[EMAIL PROTECTED]> writes:
>
> | Peter Kümmel wrote:
> | >> | Or happens the dropping only to auto repeated keys?
> | >>
> | >> Only auto-repeated keys.
> | >
> | > OK, if you are really sure only auto-repeated keys will be dropped,
> | > I think your pa
On Thursday 31 May 2007 22:05:31 Lars Gullik Bjønnes wrote:
> Yes, quite sure
>
> + if (e->isAutoRepeat()) {
> + ...
> + }
Could you shove it in, please?
> --
> Lgb
--
José Abílio
Peter Kümmel <[EMAIL PROTECTED]> writes:
| Peter Kümmel wrote:
| >> | Or happens the dropping only to auto repeated keys?
| >>
| >> Only auto-repeated keys.
| >
| > OK, if you are really sure only auto-repeated keys will be dropped,
| > I think your patch should go into RC1.
|
| BUT, I also had
Lars Gullik Bjønnes wrote:
> Peter Kümmel <[EMAIL PROTECTED]> writes:
>
> | Lars Gullik Bjønnes wrote:
> | > Peter Kümmel <[EMAIL PROTECTED]> writes:
> | >
> | > | > If you go aab
> | > | > then the b, might be dropped. I have not tested.
> | > | >
> | > | > B
Peter Kümmel wrote:
>> | Or happens the dropping only to auto repeated keys?
>>
>> Only auto-repeated keys.
>
> OK, if you are really sure only auto-repeated keys will be dropped,
> I think your patch should go into RC1.
BUT, I also had a Qt based patch which only discards auto repeated
keys, and
Peter Kümmel <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Peter Kümmel <[EMAIL PROTECTED]> writes:
| >
| > | > If you go aab
| > | > then the b, might be dropped. I have not tested.
| > | >
| > | > But sure, quite a few will be dropped. (w
Lars Gullik Bjønnes wrote:
> Peter Kümmel <[EMAIL PROTECTED]> writes:
>
> | > If you go aab
> | > then the b, might be dropped. I have not tested.
> | >
> | > But sure, quite a few will be dropped. (which is just what we
> | > want if we are too slow to ge
Peter Kümmel <[EMAIL PROTECTED]> writes:
| > If you go aab
| > then the b, might be dropped. I have not tested.
| >
| > But sure, quite a few will be dropped. (which is just what we
| > want if we are too slow to get them in.)
| >
|
| What if you have a
Lars Gullik Bjønnes wrote:
> Peter Kümmel <[EMAIL PROTECTED]> writes:
>
> | Peter Kümmel wrote:
> | >
> | > And no keys will be dropped?
> | >
> | > We could also put in your patch, as it is only a problem on Linux.
> | > Do you think we could use QApplication::synxX() instead of the X11
> | > c
Lars Gullik Bjønnes wrote:
> Peter Kümmel <[EMAIL PROTECTED]> writes:
>
> | Lars Gullik Bjønnes wrote:
> | > Peter Kümmel <[EMAIL PROTECTED]> writes:
> | >
> | > | José Matos wrote:
> | > | > On Thursday 24 May 2007 18:17:37 Peter Kümmel wrote:
> | > | >> The event_1 patch gives better results
Peter Kümmel <[EMAIL PROTECTED]> writes:
| Peter Kümmel wrote:
| >
| > And no keys will be dropped?
| >
| > We could also put in your patch, as it is only a problem on Linux.
| > Do you think we could use QApplication::synxX() instead of the X11
| > call?
|
| The Qt code:
|
http://websvn.kde.o
Peter Kümmel <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Peter Kümmel <[EMAIL PROTECTED]> writes:
| >
| > | José Matos wrote:
| > | > On Thursday 24 May 2007 18:17:37 Peter Kümmel wrote:
| > | >> The event_1 patch gives better results on systems
| > | >> with a fast enough grap
Peter Kümmel wrote:
>
> And no keys will be dropped?
>
> We could also put in your patch, as it is only a problem on Linux.
> Do you think we could use QApplication::synxX() instead of the X11
> call?
The Qt code:
http://websvn.kde.org/*checkout*/trunk/qt-copy/src/gui/kernel/qapplication_x11.cpp
José Matos <[EMAIL PROTECTED]> writes:
| On Thursday 31 May 2007 20:50:54 Lars Gullik Bjønnes wrote:
| > My patch works for all "key" variants. that is entered through
| > auto-keying. Basically all key events that we failt to handle because
| > auto-repeat is too fast are dropped.
|
| What is
Lars Gullik Bjønnes wrote:
> Peter Kümmel <[EMAIL PROTECTED]> writes:
>
> | José Matos wrote:
> | > On Thursday 24 May 2007 18:17:37 Peter Kümmel wrote:
> | >> The event_1 patch gives better results on systems
> | >> with a fast enough graphic card(?) but does not work
> | >> an older systems.
>
On Thursday 31 May 2007 20:50:54 Lars Gullik Bjønnes wrote:
> My patch works for all "key" variants. that is entered through
> auto-keying. Basically all key events that we failt to handle because
> auto-repeat is too fast are dropped.
What is the drawback then?
> --
> Lgb
--
José Abí
Peter Kümmel <[EMAIL PROTECTED]> writes:
| José Matos wrote:
| > On Thursday 24 May 2007 18:17:37 Peter Kümmel wrote:
| >> The event_1 patch gives better results on systems
| >> with a fast enough graphic card(?) but does not work
| >> an older systems.
| >>
| >> Jose feel free to do what you wa
On Thursday 31 May 2007 20:35:06 Peter Kümmel wrote:
> But one patch which at least fixes the pageup/down-key scrolling
> should go in before RC1.
I intend to release RC1 really soon now, so this patch must wait for RC2.
> Peter
--
José Abílio
José Matos wrote:
> On Thursday 24 May 2007 18:17:37 Peter Kümmel wrote:
>> The event_1 patch gives better results on systems
>> with a fast enough graphic card(?) but does not work
>> an older systems.
>>
>> Jose feel free to do what you want.
>
> What is the outcome of your email exchange with
On Thursday 24 May 2007 18:17:37 Peter Kümmel wrote:
> The event_1 patch gives better results on systems
> with a fast enough graphic card(?) but does not work
> an older systems.
>
> Jose feel free to do what you want.
What is the outcome of your email exchange with Helge and Lars on this
subj
No ideas any more--also the last patch does not work
(Helge's private reply).
I've reverted the first patch,
http://www.lyx.org/trac/changeset/18376
because it introduces this bug,
http://marc.info/?l=lyx-devel&m=117944188219722&w=2
detected by Dov.
The event_1 patch gives better results on syste
On Wed, May 23, 2007 at 12:13:16PM +0200, Helge Hafting wrote:
> Dov Feldstern wrote:
> >Peter Kümmel wrote:
> >>
> >>I'm running out of ideas...
> >>Is this patch better (the flush call is new)?
> >>Or with processEvents instead of flush?
> >>
> >
> >event_2.patch works for me --- but then again e
Dov Feldstern wrote:
Peter Kümmel wrote:
I'm running out of ideas...
Is this patch better (the flush call is new)?
Or with processEvents instead of flush?
event_2.patch works for me --- but then again event_1 did, too. Again,
this is on linux. Scrolling appears to be fine (both with arrow k
José Matos wrote:
> On Tuesday 22 May 2007 7:26:37 pm Peter Kümmel wrote:
>> The current svn code is not correct, even when this patch isn't perfect,
>> should I apply it?
>
> Could you get more people to test it, please?
>
> This is a sensitive area, just like walking on thin glass. :-)
>
>
On Tuesday 22 May 2007 7:26:37 pm Peter Kümmel wrote:
> The current svn code is not correct, even when this patch isn't perfect,
> should I apply it?
Could you get more people to test it, please?
This is a sensitive area, just like walking on thin glass. :-)
If by Friday you don't have any
Dov Feldstern wrote:
> Peter Kümmel wrote:
>>
>> I'm running out of ideas...
>> Is this patch better (the flush call is new)?
>> Or with processEvents instead of flush?
>>
>
> event_2.patch works for me --- but then again event_1 did, too. Again,
> this is on linux. Scrolling appears to be fine (b
Peter Kümmel wrote:
I'm running out of ideas...
Is this patch better (the flush call is new)?
Or with processEvents instead of flush?
event_2.patch works for me --- but then again event_1 did, too. Again,
this is on linux. Scrolling appears to be fine (both with arrow keys and
page-up and p
Helge Hafting wrote:
> Peter Kümmel wrote:
>> Abdelrazak Younes wrote:
>>
Is this your only comment?
>>> Yes. Sorry, don't have the time to do much more. I thought I'd share my
>>> opinion ;-)
>>>
>>
>> Sorry, too - for my harsh reply.
>>
>>
Anyway I don't think there
Helge Hafting wrote:
> Peter Kümmel wrote:
>> Abdelrazak Younes wrote:
>>
Is this your only comment?
>>> Yes. Sorry, don't have the time to do much more. I thought I'd share my
>>> opinion ;-)
>>>
>>
>> Sorry, too - for my harsh reply.
>>
>>
Anyway I don't think there
Abdelrazak Younes wrote:
Martin Vermeer wrote:
BTW what do you mean by 'input methods? Here I have a choice of virtual
keyboard and handwriting recognition. How is that relevant?
Input methods are used in the CJK world to help the writing. The
technique is very similar to autocompletion metho
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Is this your only comment?
Yes. Sorry, don't have the time to do much more. I thought I'd share my
opinion ;-)
Sorry, too - for my harsh reply.
Anyway I don't think there is a simpler solution, at least I will
not look for it, t
Martin Vermeer wrote:
On Sun, May 20, 2007 at 07:08:59PM +0200, Peter Kümmel wrote:
Abdelrazak Younes wrote:
...
OK, I've found a better solution ;)
I had to test if it was worth to upgrade to 1GB ram.
I can understand that. I was thinking of collecting the scroll events
and cancelling th
On Sun, May 20, 2007 at 07:08:59PM +0200, Peter Kümmel wrote:
> Abdelrazak Younes wrote:
...
> OK, I've found a better solution ;)
> I had to test if it was worth to upgrade to 1GB ram.
>
> >
> > I can understand that. I was thinking of collecting the scroll events
> > and cancelling them if a
Peter Kümmel wrote:
Dov Feldstern wrote:
Peter Kümmel wrote:
On slow/loaded systems the last patch floods the
event queue with timer events instead of key/scroll events.
I hope attached patch will now really fix the problem.
Peter
This works for me (timer_scroll_4.patch) --- at least for wha
Dov Feldstern wrote:
> Peter Kümmel wrote:
>>
>> On slow/loaded systems the last patch floods the
>> event queue with timer events instead of key/scroll events.
>> I hope attached patch will now really fix the problem.
>>
>> Peter
>>
>
> This works for me (timer_scroll_4.patch) --- at least for wh
Abdelrazak Younes wrote:
>> Is this your only comment?
>
> Yes. Sorry, don't have the time to do much more. I thought I'd share my
> opinion ;-)
Sorry, too - for my harsh reply.
>
>>
>> Anyway I don't think there is a simpler solution, at least I will
>> not look for it, this bug has cost me al
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Peter Kümmel wrote:
Next try. To see how it works change the event_delay_ms
variable in the constructor to 3000 and use -dbg 12.
This looks way too complicated Peter. There must be a simpler solution.
Abdel.
Is this your only comment?
Yes. Sor
Peter Kümmel wrote:
On slow/loaded systems the last patch floods the
event queue with timer events instead of key/scroll events.
I hope attached patch will now really fix the problem.
Peter
This works for me (timer_scroll_4.patch) --- at least for what I'm
testing, namely, cursor movement b
Peter Kümmel wrote:
Dov Feldstern wrote:
The truth is, I don't know that this is directly related to the machine
on which it's running. My machine is quite powerful --- it's a Pentium
IV 3.0 GHz; and I don't see any jump in the system load when I start
scrolling, either: not when I start and the
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>> Next try. To see how it works change the event_delay_ms
>> variable in the constructor to 3000 and use -dbg 12.
>
> This looks way too complicated Peter. There must be a simpler solution.
>
> Abdel.
>
You could start with some like the attached
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>> Next try. To see how it works change the event_delay_ms
>> variable in the constructor to 3000 and use -dbg 12.
>
> This looks way too complicated Peter. There must be a simpler solution.
>
> Abdel.
>
Is this your only comment?
Anyway I don't t
Peter Kümmel wrote:
Next try. To see how it works change the event_delay_ms
variable in the constructor to 3000 and use -dbg 12.
This looks way too complicated Peter. There must be a simpler solution.
Abdel.
On Sat, May 19, 2007 at 10:53:39AM +0200, Peter Kümmel wrote:
>
> > +#include
> >
>
> not needed will remove it
>
> > class QWidget;
>
> > + ///
> > + QTimer delayed_scrollbar_sync;
> > + ///
> > + QTimer delayed_key_event;
> > + struct key_info { QKeySymbol* sym; Qt::KeyboardModi
Peter Kümmel wrote:
> Next try. To see how it works change the event_delay_ms
> variable in the constructor to 3000 and use -dbg 12.
>
>
> Please test if scrolling works when
>
> - moving the slider with the mouse
> - clicking in the scroll bar
> - pressing page up/down keys
> - arrow keys
> - a
> +#include
>
not needed will remove it
> class QWidget;
> + ///
> + QTimer delayed_scrollbar_sync;
> + ///
> + QTimer delayed_key_event;
> + struct key_info { QKeySymbol* sym; Qt::KeyboardModifiers mod; };
> + std::vector delayed_keys;
> };
Andre, any tips how to
Next try. To see how it works change the event_delay_ms
variable in the constructor to 3000 and use -dbg 12.
Please test if scrolling works when
- moving the slider with the mouse
- clicking in the scroll bar
- pressing page up/down keys
- arrow keys
- arrow buttons on the scroll bar
- using the
Andre Poenitz wrote:
> On Fri, May 18, 2007 at 08:43:12AM +0200, Peter Kümmel wrote:
>> Andre Poenitz wrote:
===
--- src/frontends/qt4/GuiWorkArea.cpp (revision 18380)
+++ src/frontends/qt4/GuiWorkArea.cpp (wor
Andre Poenitz wrote:
> On Fri, May 18, 2007 at 08:12:33AM +0200, Peter Kümmel wrote:
>> I also realized this while working on this bug. So I dropped my first
>> patches and now use isAutoRepeated in the committed patch, by this
>> a keystroke produced by a user will never get lost.
>> All typed key
On Fri, May 18, 2007 at 08:43:12AM +0200, Peter Kümmel wrote:
> Andre Poenitz wrote:
> >> ===
> >> --- src/frontends/qt4/GuiWorkArea.cpp (revision 18380)
> >> +++ src/frontends/qt4/GuiWorkArea.cpp (working copy)
> >> @@ -161,
On Fri, May 18, 2007 at 08:12:33AM +0200, Peter Kümmel wrote:
> I also realized this while working on this bug. So I dropped my first
> patches and now use isAutoRepeated in the committed patch, by this
> a keystroke produced by a user will never get lost.
> All typed keystrokes are in the event qu
Peter Kümmel wrote:
> What hasPendingEvents returns makes no sense to me.
> Isn't it that there is a queue for all events, and when one
> is handled (event-accept()) it is done and removed from the
> queue? The truth isin the Qt source code, but who could
> read it?
>
Could this be part of the p
On Fri, May 18, 2007 at 03:56:30PM +0300, Martin Vermeer wrote:
> On Fri, May 18, 2007 at 01:51:40PM +0200, Peter Kümmel wrote:
> > > Yes, maybe I could... instead, I used '-dbg key' and entered
> > > the strings 'appropriate' and 'laboratories' into an empty file.
> > > by typing 'app' and
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>>
>> So we can't use isAutoRepeat also not hasPendingEvents. Best idea
>> I have is to revert.
>
> I think so too :-( But that was a nice idea ;-)
isAutoRepeat doesn't work because of the word completion, it only
returns true for the repeated letter
Dov Feldstern wrote:
>
> The truth is, I don't know that this is directly related to the machine
> on which it's running. My machine is quite powerful --- it's a Pentium
> IV 3.0 GHz; and I don't see any jump in the system load when I start
> scrolling, either: not when I start and the cursor is s
On Fri, May 18, 2007 at 01:51:40PM +0200, Peter Kümmel wrote:
> Martin Vermeer wrote:
> > On Fri, May 18, 2007 at 12:38:19PM +0200, Abdelrazak Younes wrote:
> >> Martin Vermeer wrote:
> >>> On Fri, May 18, 2007 at 09:58:59AM +0200, Abdelrazak Younes wrote:
> Martin Vermeer wrote:
> >>> ...
> >
Peter Kümmel wrote:
So we can't use isAutoRepeat also not hasPendingEvents. Best idea
I have is to revert.
I think so too :-( But that was a nice idea ;-)
The keyReleaseEvent() solution in bugzilla is probably the best solution.
The scrollbar events could be filtered out.
Abdel.
Peter Kümmel wrote:
Peter Kümmel wrote:
Dov Feldstern wrote:
Peter Kümmel wrote:
Dov Feldstern wrote:
Peter Kümmel wrote:
Dov Feldstern wrote:
Again, to reproduce, just hold down any of the arrow keys, and keep
holding it down. At some point it will just stop moving --- I assume
this will h
Martin Vermeer wrote:
> On Fri, May 18, 2007 at 12:38:19PM +0200, Abdelrazak Younes wrote:
>> Martin Vermeer wrote:
>>> On Fri, May 18, 2007 at 09:58:59AM +0200, Abdelrazak Younes wrote:
Martin Vermeer wrote:
>>> ...
>>>
>>> Another scenario: I am typing on my Nokia 770 Internet tablet
>>
On Fri, May 18, 2007 at 12:38:19PM +0200, Abdelrazak Younes wrote:
> Martin Vermeer wrote:
> >On Fri, May 18, 2007 at 09:58:59AM +0200, Abdelrazak Younes wrote:
> >>Martin Vermeer wrote:
> >
> >...
> >
> >Another scenario: I am typing on my Nokia 770 Internet tablet
> >over a
> >vnc co
Peter Kümmel wrote:
>> No :(, if anything it's worse: now holding a key is *always* processed
>> as only a single keypress, there's not even an initial period when the
>> cursor zooms along...
>>
>
> Seems we could not use QCoreApplication::hasPendingEvents() to check if
> the system is busy.
Is
Peter Kümmel wrote:
> Dov Feldstern wrote:
>> Peter Kümmel wrote:
>>> Dov Feldstern wrote:
Peter Kümmel wrote:
> Dov Feldstern wrote:
Again, to reproduce, just hold down any of the arrow keys, and keep
holding it down. At some point it will just stop moving --- I assume
this
Helge Hafting wrote:
> Peter Kümmel wrote:
>> Andre Poenitz wrote:
>>
+///
+QTimer& delayed_scrollbar_sync;
>>> A _reference_? Why?
>>>
>>> Andre'
>>>
>>>
>>
>> Here a updated patch.
>>
>>
> I checked out todays svn and applied this.
>
> It does *not* help
>
Peter Kümmel wrote:
Andre Poenitz wrote:
+ ///
+ QTimer& delayed_scrollbar_sync;
A _reference_? Why?
Andre'
Here a updated patch.
I checked out todays svn and applied this.
It does *not* help
when holding the mouse down in the jump-scroll area of the scrollb
Dov Feldstern wrote:
> Peter Kümmel wrote:
>> Dov Feldstern wrote:
>>> Peter Kümmel wrote:
Dov Feldstern wrote:
>
>>> Again, to reproduce, just hold down any of the arrow keys, and keep
>>> holding it down. At some point it will just stop moving --- I assume
>>> this will happen on any machin
Peter Kümmel wrote:
Dov Feldstern wrote:
Peter Kümmel wrote:
Dov Feldstern wrote:
Again, to reproduce, just hold down any of the arrow keys, and keep
holding it down. At some point it will just stop moving --- I assume
this will happen on any machine if you hold the key long enough. From
the
Martin Vermeer wrote:
On Fri, May 18, 2007 at 09:58:59AM +0200, Abdelrazak Younes wrote:
Martin Vermeer wrote:
...
Another scenario: I am typing on my Nokia 770 Internet tablet
over a
vnc connection. It does 'word completion', which is like very
fast typing... and indeed, in LyX 1.4 charact
Dov Feldstern wrote:
> Peter Kümmel wrote:
>> Dov Feldstern wrote:
>>> Try navigating by holding down one of the arrow keys. The cursor zooms
>>> along (which is what we usually want), until at some point the mechanism
>>> added here kicks in, and then the cursor suddenly stops moving. From
>>> thi
On Fri, May 18, 2007 at 09:58:59AM +0200, Abdelrazak Younes wrote:
> Martin Vermeer wrote:
...
> >>>Another scenario: I am typing on my Nokia 770 Internet tablet
> >>>over a
> >>>vnc connection. It does 'word completion', which is like very
> >>>fast typing... and indeed, in LyX 1.4 characters
I'll try, but how do I do this? Is there some svn command for
reverting to a specific version?
i'm not aware of any direct revert command of svn.
however you can checkout particular revision of the svn tree
(i.e. the 18265 revision).
svn up -r VERSION
In order to revert a spe
Abdelrazak Younes wrote:
> Helge Hafting wrote:
>> Abdelrazak Younes wrote:
>>> Helge Hafting wrote:
>>>
I did this, and recompiled. It did not help, the
resulting LyX still have that horrible lagging problem.
>>>
>>> It is true that LyX has lost some performance lately. The UserGuide
>>
Peter Kümmel wrote:
Dov Feldstern wrote:
Try navigating by holding down one of the arrow keys. The cursor zooms
along (which is what we usually want), until at some point the mechanism
added here kicks in, and then the cursor suddenly stops moving. From
this point on, key press events are only h
Helge Hafting wrote:
Abdelrazak Younes wrote:
Helge Hafting wrote:
I did this, and recompiled. It did not help, the
resulting LyX still have that horrible lagging problem.
It is true that LyX has lost some performance lately. The UserGuide
PageDown scrolling test is 30 seconds for me right
Abdelrazak Younes wrote:
Helge Hafting wrote:
I did this, and recompiled. It did not help, the
resulting LyX still have that horrible lagging problem.
It is true that LyX has lost some performance lately. The UserGuide
PageDown scrolling test is 30 seconds for me right now while it was 15
> "Peter" == Peter Kümmel <[EMAIL PROTECTED]> writes:
Peter> I also realized this while working on this bug. So I dropped my
Peter> first patches and now use isAutoRepeated in the committed
Peter> patch, by this a keystroke produced by a user will never get
Peter> lost. All typed keystrokes ar
Andre Poenitz wrote:
>> +///
>> +QTimer& delayed_scrollbar_sync;
>
> A _reference_? Why?
>
> Andre'
>
Here a updated patch.
--
Peter Kümmel
Index: src/frontends/qt4/GuiWorkArea.cpp
===
--- src/frontends/qt4/GuiWorkArea.c
Dov Feldstern wrote:
> Try navigating by holding down one of the arrow keys. The cursor zooms
> along (which is what we usually want), until at some point the mechanism
> added here kicks in, and then the cursor suddenly stops moving. From
> this point on, key press events are only handled one at a
Dov Feldstern wrote:
> Peter Kümmel wrote:
>> Now I have found the best solution:
>>
>> Full control to the user, means all key events
>> produced by the user are processed but generated
>> ones are ignored if the system is busy.
>>
>> Could it go into beta3?
>>
>> Peter
>>
>
> It's good this is i
Peter Kümmel wrote:
> Andre Poenitz wrote:
>>> ===
>>> --- src/frontends/qt4/GuiWorkArea.cpp (revision 18380)
>>> +++ src/frontends/qt4/GuiWorkArea.cpp (working copy)
>>> @@ -161,7 +161,7 @@
>>>
>>> GuiWorkArea::GuiWorkA
Martin Vermeer wrote:
On Fri, May 18, 2007 at 08:55:15AM +0200, Peter Kümmel wrote:
Martin Vermeer wrote:
On Thu, May 17, 2007 at 10:41:56PM +0200, Andre Poenitz wrote:
On Thu, May 17, 2007 at 12:57:29PM +0200, Peter Kümmel wrote:
I would feel more comfortable is this were restricted to scrol
On Fri, May 18, 2007 at 08:55:15AM +0200, Peter Kümmel wrote:
> Martin Vermeer wrote:
> > On Thu, May 17, 2007 at 10:41:56PM +0200, Andre Poenitz wrote:
> >> On Thu, May 17, 2007 at 12:57:29PM +0200, Peter Kümmel wrote:
> I would feel more comfortable is this were restricted to scrolling,
> >>
Martin Vermeer wrote:
> On Thu, May 17, 2007 at 10:41:56PM +0200, Andre Poenitz wrote:
>> On Thu, May 17, 2007 at 12:57:29PM +0200, Peter Kümmel wrote:
I would feel more comfortable is this were restricted to scrolling,
but I take it you extensively tested it with 'usual typing'
>>> Curre
On Thu, May 17, 2007 at 10:41:56PM +0200, Andre Poenitz wrote:
> On Thu, May 17, 2007 at 12:57:29PM +0200, Peter Kümmel wrote:
> > > I would feel more comfortable is this were restricted to scrolling,
> > > but I take it you extensively tested it with 'usual typing'
> >
> > Currently all generated
Andre Poenitz wrote:
>> ===
>> --- src/frontends/qt4/GuiWorkArea.cpp(revision 18380)
>> +++ src/frontends/qt4/GuiWorkArea.cpp(working copy)
>> @@ -161,7 +161,7 @@
>>
>> GuiWorkArea::GuiWorkArea(int w, int h, int id,
Andre Poenitz wrote:
> On Thu, May 17, 2007 at 12:57:29PM +0200, Peter Kümmel wrote:
>>> I would feel more comfortable is this were restricted to scrolling,
>>> but I take it you extensively tested it with 'usual typing'
>> Currently all generated events are dropped which couldn't become
>> visible
Peter Kümmel wrote:
Now I have found the best solution:
Full control to the user, means all key events
produced by the user are processed but generated
ones are ignored if the system is busy.
Could it go into beta3?
Peter
It's good this is in beta-3 ;) , because I've just found a very annoy
Andre Poenitz wrote:
On Thu, May 17, 2007 at 10:53:16PM +0200, Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Andre Poenitz wrote:
On Thu, May 17, 2007 at 12:57:29PM +0200, Peter Kümmel wrote:
I would feel more comfortable is this were restricted to scrolling,
but I take it you extensively
On Thu, May 17, 2007 at 10:53:16PM +0200, Abdelrazak Younes wrote:
> Abdelrazak Younes wrote:
> >Andre Poenitz wrote:
> >>On Thu, May 17, 2007 at 12:57:29PM +0200, Peter Kümmel wrote:
> I would feel more comfortable is this were restricted to scrolling,
> but I take it you extensively teste
Abdelrazak Younes wrote:
Andre Poenitz wrote:
On Thu, May 17, 2007 at 12:57:29PM +0200, Peter Kümmel wrote:
I would feel more comfortable is this were restricted to scrolling,
but I take it you extensively tested it with 'usual typing'
Currently all generated events are dropped which couldn't
Andre Poenitz wrote:
On Thu, May 17, 2007 at 12:57:29PM +0200, Peter Kümmel wrote:
I would feel more comfortable is this were restricted to scrolling,
but I take it you extensively tested it with 'usual typing'
Currently all generated events are dropped which couldn't become
visible immediately
On Thu, May 17, 2007 at 02:03:55PM +0200, Peter Kümmel wrote:
> Here a new patch to address Helge's scrolling bug.
> The important comment:
>
> "We circumvent the event queue for scrolling events.
> This avoids scrolling after the user has stopped
> scrolling, but scrolling proceeds because the
>
On Thu, May 17, 2007 at 12:57:29PM +0200, Peter Kümmel wrote:
> > I would feel more comfortable is this were restricted to scrolling,
> > but I take it you extensively tested it with 'usual typing'
>
> Currently all generated events are dropped which couldn't become
> visible immediately. But coul
On Thursday 17 May 2007 13:03:55 Peter Kümmel wrote:
> I've found no problems on Win and Linux, but it
> should be tested more intensively, so it would be
> good to ship it with beta 3, but I assume I'm too
> late.
You are right on both accounts. :-)
If this works and after independent confir
Here a new patch to address Helge's scrolling bug.
The important comment:
"We circumvent the event queue for scrolling events.
This avoids scrolling after the user has stopped
scrolling, but scrolling proceeds because the
event queue is full of scroll events.
We trigger the scrolling by a timer wh
Andre Poenitz wrote:
> On Thu, May 17, 2007 at 09:37:53AM +0200, Peter Kümmel wrote:
>> Now I have found the best solution:
>>
>> Full control to the user, means all key events
>> produced by the user are processed but generated
>> ones are ignored if the system is busy.
>>
>> Could it go into beta
1 - 100 of 130 matches
Mail list logo
