Messagepump incomplete?

BackupUser · Post by **BackupUser** » Wed Apr 23, 2003 10:23 am

Restored from previous forum. Originally posted by ebknoppert.

The WaitForWindowsEvent() doesn't seem to use IsDialogMessage()
This is not really handy since it will prevent some important messages to occure.

I write custom controls and they awaite the WM_GETDLGCODE message.
Without this IsDialog() API it will use WM_KEYDOWN instead.
This is not my goal to handle it this way.

I have never seen any problem using the IsDialog.. in SDK apps.
So...?

I wonder how PureBasic currently handles the WM_TABSTOP part.

??

http://www.hellobasic.com

BackupUser · Post by **BackupUser** » Wed Apr 23, 2003 9:19 pm

Restored from previous forum. Originally posted by PB.

> The WaitForWindowsEvent() doesn't seem to use IsDialogMessage()
> This is not really handy since it will prevent some important messages to occure.

From what I've read here in the past, the WaitWindowEvent() and WindowEvent()
commands are ONLY designed to check for the events listed here (even though it
will currently pick up other events, but there is no absolute guarantee):

http://www.purebasic.com/documentation/ ... event.html

All other events MUST be checked via a callback.

BackupUser · Post by **BackupUser** » Wed Apr 23, 2003 9:34 pm

Restored from previous forum. Originally posted by ebknoppert.

It's not what it returns, it's what it handles (executes internally)
Almost every messagepump i have seen add's this to have a 'proper' execution.
Not everything get's passed in the cb since the messagepump is not entirly as desired.

http://www.hellobasic.com

BackupUser · Post by **BackupUser** » Wed Apr 23, 2003 9:38 pm

Restored from previous forum. Originally posted by PB.

> It's not what it returns, it's what it handles (executes internally)

Oops, I misunderstood. Sorry!