I have a problem with an application that creates a initial popup
window and starts another application. The window for the second
application is completely covered by the initial popup window.
Investigating the problem, I found that the popup window is not
managed by the window manager and no oth
On Thu, 2005-04-14 at 20:44 +0200, Alexandre Julliard wrote:
>
> The WM_TIMER cannot "remain in the queue", it's never put there in the
> first place, it's generated on the fly. If you really see a WM_TIMER
> in the posted message queue, it's because someone has done a
> PostMessage on it, and th
On Thu, 2005-04-14 at 19:49 +0200, Alexandre Julliard wrote:
> WM_TIMER messages are not posted, so the message can't possibly be
> removed by get_posted_message. It will be handled in
> find_expired_timer, which will return a new message and restart the
> timer.
>
Yes, the first time that Peek
On Thu, 2005-04-14 at 15:53 +0200, Alexandre Julliard wrote:
> Jose Alonso <[EMAIL PROTECTED]> writes:
>
> > for (;;)
> > {
> > (1) if (PeekMessageW( &msg, 0, 0, 0, PM_NOREMOVE ))
> > ...
> >
If a Menu is accessed and the application used the function
SetTimer, then the application and the wineserver use 100% of
the CPU (loop of sending and receiving WM_TIMER).
function used: SetTimer(NULL, 0, 100, TimerProc)
Description of the loop:
dlls/user/menu.c
MENU_TrackMenu
while (!fEndMe
