On Thu, 25 May 2000, Alexandre Julliard wrote:
> michael cardenas <[EMAIL PROTECTED]> writes:
>
> > Here's another small patch, written by Phil Landman (one of our
> > programmers) for PeekMessage that solves the problem of winelib apps
> > taking 99% of the cpu when they're idle. It's just a counter that waits
> > a little bit if we haven't recieved any messages in a while. You'll
> > see... Anyway, it works well, we only use 5% when we're in the background.
>
> Well, if your app is sitting in a PeekMessage loop I'd expect it to
> take 99% of the CPU... I don't think this is anything wrong with
> PeekMessage itself.
Nonetheless there's a problem in there somewhere. When I was trying to
compile JWPCE under Winelib a while back, the difference was plain - the PE
binary took no noticeable CPU while idle, but the ELF Winelib compiled
binary always took 100%. Very smooth, but still taking up far too much CPU...
On an unrelated speed note, did someone (Ulrich?) light a very big fire
under the DibSection handling since I was last paying attention? Invaders95
(one of my standard Wine tester programs) now runs at incredible interactive
speed...
Cheers,
-Matt.
