Does wine send window messages without waiting apps to reenter userdll?

[Javier Pimás]

Ok, that should be 39182 <https://bugs.winehq.org/show_bug.cgi?id=39182>. I
downloaded wine source applied the patch and compiled (first time I ever do
that), but the output of the test didn't change.

On Sun, Aug 30, 2015 at 5:36 AM, Sebastian Lackner <sebastian at fds-team.de>
wrote:

> Thanks for providing the testcase. It indeed looks like a wine bug. Would
> you
> mind to open a bug report on bugs.winehq.org with your testcase and
> explanation?
> Feel free to add me as CC.
>
> The following quick & dirty hack fixes the issue (but will very likely
> break
> other stuff): http://ix.io/kx0
>
> Does it also help for your app?
>
> Regards,
> Sebastian
>
> On 28.08.2015 17:52, Javier Pimás wrote:
> > I wrote a small test which I attach here, very small program where you
> can
> > see if WndProc is called from WaitMessage. It fails, which I think shows
> > what I doubted is actually happening. Tested in the old 1.6.2 wine and
> also
> > in 1.7.50.
> >
> > Cheers!
> >
> > On Wed, Aug 26, 2015 at 11:29 AM, Sebastian Lackner <
> sebastian at fds-team.de>
> > wrote:
> >
> >> On 26.08.2015 16:04, Sebastian Lackner wrote:
> >>> If you are concerned that WaitMessage immediately dispatches the
> >> messages,
> >>> Wine doesn't do that. Processing of window messages is only done in the
> >>> context of GetMessage and PeekMessage, no matter if its a "queued" or
> >>> "non-queued" message. In fact Wine doesn't really make a difference
> >> between
> >>> the two, it just assigns specific internal message numbers for
> non-queued
> >>> messages. To identify those the the highest bit (0x80000000) is set.
> >>
> >> After reading the last part again I noticed that I wasn't really very
> >> precise,
> >> because I somehow already assumed that you are talking about non-queued
> >> messages
> >> caused by SetWindowPos and things like that. Those are implemented using
> >> internal
> >> messages in Wine, and might be affected by the "bugs" mentioned in the
> >> last mail.
> >>
> >> Besides that its of course also possible to send other non-queued
> messages
> >> directly with SendMessage and similar functions. But in this case the
> >> answer would
> >> be the same: WaitMessage does not dispatch them immediately, they are
> >> processed
> >> during a call to PeekMessage or GetMessage.
> >>
> >> Regards,
> >> Sebastian
> >>
> >>
> >
> >
> >
> >
> >
>
>


-- 
Javier Pimás
Ciudad de Buenos Aires
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20150831/ffd653af/attachment.html>