Re: Refreshing windows as often as possible, but not too often

[Ben Laurie <ben algroup co uk>]

Chris Jones wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi
> 
> > Hmm. But the effect I really want is to use as much CPU as is
> available,
> > but leave some when needed for stuff like moving the pointer. I can
> > write a non-X app that doesn't chew the _whole_ CPU when someone
> else
> > wants it, why can't it be the same with X?
> 
> Surely if the program is a video capture app you have a target "frames
> per second" rate you want to capture the image at? If that is the case
> (and it should be - capturing video "as fast as possible" will just
> lead to a naff playback) you can use a gtk_timeout to invoke the
> capturing function so many times a second.

I'm not after a nice playback, I'm processing the images, so "as fast as
possible" is exactly what I do want.

> In my experience, the BT848 (the most common Brooktree in use) rarely
> captures at more than 30fps and even then only at tiny resolutions
> (could be hard disk related through).

I think it is vast amount of data related :-)

> You might like to take a look at the source for XawTV which captures
> avi's from bttv cards

The point I'm getting at is I want to update a window as fast as
possible _without_ trashing the user interface. That I happen to be
updating it with captured video is not really the important point.
Surely there's a way to do this?

Cheers,

Ben.

--
http://www.apache-ssl.org/ben.html

"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
     - Indira Gandhi