Re: [Mutt] #2899: progress display is now too slow for common

To: jhawk@xxxxxxx, pdmef@xxxxxxx, safari-mutt-trac-ex35v2hyr32ewf3uqa4z2h4h6icei57rqlgd2diz@xxxxxxxxxxxxxxx, brendan@xxxxxxxxxx
Subject: Re: [Mutt] #2899: progress display is now too slow for common
From: Mutt <fleas@xxxxxxxx>
Date: Tue, 06 Nov 2007 22:55:49 -0000
Cc: mutt-dev@xxxxxxxx
In-reply-to: <037.612b0d12caeeb30d3d28a97fdf09f64d@xxxxxxxx>
List-post: <mailto:mutt-dev@mutt.org>
List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-dev"
Mail-followup-to: fleas@xxxxxxxx
References: <037.612b0d12caeeb30d3d28a97fdf09f64d@xxxxxxxx>
Reply-to: fleas@xxxxxxxx
Sender: owner-mutt-dev@xxxxxxxx

#2899: progress display is now too slow for common operations

Changes (by brendan):

  * component:  mutt => display

Comment:

 I think what I'd like to see is a version of this patch that self-tunes.
 I'm thinking it could start by skipping updates less than 40ms apart or so
 (25 frames per second), and if the time between calls is greater than the
 configured delay by some margin, automatically increase the delay (with a
 cap at maybe around 1000ms). Thoughts?

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/2899#comment:4>

References:
- [Mutt] #2899: progress display is now too slow for common operations
  - From: Mutt

Prev by Date: Re: [Mutt] #2985: segfault in mx_update_context
Next by Date: Re: [Mutt] #2899: progress display is now too slow for common
Previous by thread: Re: [Mutt] #2899: progress display is now too slow for common
Next by thread: Re: [Mutt] #2899: progress display is now too slow for common
Index(es):
- Date
- Thread