Support of #WM_KEYDOWN + EventwParam()?

Everything else that doesn't fall into one of the other PB categories.
Marco2007
Enthusiast
Enthusiast
Posts: 648
Joined: Tue Jun 12, 2007 10:30 am
Location: not there...

Support of #WM_KEYDOWN + EventwParam()?

Post by Marco2007 »

Hi,

according to this:
Srod wrote:Yes PB will be swallowing the timer events now.
Srod and TS-Soft wrote:use a callback
Will that also happen for e.g.:

Code: Select all

#WM_KEYDOWN + EventwParam() 

Code: Select all

#WM_SIZE

I´m always avoiding callbacks, when there`s a "standard-way" (you know, what I mean)...

br and thx
Marco
PureBasic for Windows
User avatar
netmaestro
PureBasic Bullfrog
PureBasic Bullfrog
Posts: 8453
Joined: Wed Jul 06, 2005 5:42 am
Location: Fort Nelson, BC, Canada

Re: Support of #WM_KEYDOWN + EventwParam()?

Post by netmaestro »

I´m always avoiding callbacks, when there`s a "standard-way"
When you're handling Windows messages with no PureBasic native counterpart, the callback is the standard way. Using EventwParam() or EventlParam() on a #WM_<whatever> message is about the most non-standard approach there is. This is why these two commands are unsupported.
BERESHEIT
Marco2007
Enthusiast
Enthusiast
Posts: 648
Joined: Tue Jun 12, 2007 10:30 am
Location: not there...

Re: Support of #WM_KEYDOWN + EventwParam()?

Post by Marco2007 »

Best thank for this answer...a very important info!
Ok, so maybe I should change my mind about using callbacks.

thx!
PureBasic for Windows
Post Reply