On Mon, Mar 03, 2008 at 02:49:39PM +0100, Brice Figureau wrote:
> I feel that this may not be the proper fix. I suppose that the event
> loop should call rxvt_refresh_vtscr_if_needed more often than it does
> right now.
> Adding an Xevent counter shown that with the regular 10ms quick timeout,
> and doing a text selection, it can process more than 50 X mouse events
> before doing any refresh... Breaking the loop for 5 X events in a row,
> also eliminates the issue...
That sounds good. Just to be sure I got it right, it boils down to the
following, isn't it?
(with 10 events instead of 5, but that was enough according to my
quick test).
Index: src/command.c
===================================================================
--- src/command.c (revision 259)
+++ src/command.c (working copy)
@@ -2355,7 +2355,7 @@
if( select_res > 0 )
{
/* Select succeeded. Check if we have new Xevents first. */
- if( selpage == -1 && XPending( r->Xdisplay ) )
+ if( selpage == -1 && XPending( r->Xdisplay ) > 10)
continue;
/* Read whatever input we can from child fd's*/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Materm-devel mailing list
Materm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/materm-devel
mrxvt home page: http://materm.sourceforge.net
