16 bit comm issue

[Mike McCormack]

Hi,

There's a problem with the current 16bit comm architecture which i'm
not sure how to solve correctly.

If a 16bit Windows programs uses EnableCommNotification to receive
WM_COMMNOTIFY messages then sits in a message loop waiting for them,
it will never receive them because there is no chance for APC that
sends the message (COMM16_ReadComplete) to run.

I have a patch for this problem which puts an alertable wait in
GetMessage(16), which i posted in October.

What is the problem with this method, and is there a better solution
to the problem?

Mike

------------------------------------------
mailto:[e-mail]
ph [phone]

__________________________________________________________________
Get your free Australian email account at http://www.Looksmart.com.au

[Alexandre Julliard]

Mike McCormack   writes:
> I have a patch for this problem which puts an alertable wait in
> GetMessage(16), which i posted in October.
>
> What is the problem with this method, and is there a better solution
> to the problem?

Sorry, must have missed this patch. The method seems reasonable; you
probably want to do the same thing at least in PeekMessage16, and
maybe add some global flag to only do it when comm functions are
actually in use, so that other apps don't have to do an extra server
call on each message.