Re: Most significant bit in WM_COMMAND wparam
From: jeff (msnews.x.jsd_at_xoxy.net)
Date: 02/07/05
- Next message: Grei: "ListView scrollbar ?!"
- Previous message: LP: "Delegates vs. Events vs. AsyncCallback"
- In reply to: Just Me: "Most significant bit in WM_COMMAND wparam"
- Next in thread: Just Me: "Re: Most significant bit in WM_COMMAND wparam"
- Reply: Just Me: "Re: Most significant bit in WM_COMMAND wparam"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 7 Feb 2005 11:21:58 -0800
I'd guess that the purpose is to avoid sign extension that would result in the
division operation.
" Just Me" <groups@a-znet.com> wrote in message news:OYg%23tmHDFHA.628@TK2MSFTNGP15.phx.gbl...
> I've seen this in examples:
>
> Case User.WM_COMMAND
>
> Select Case (m.WParam.ToInt32 And &H7FFF0000) \ &H10000
>
>
>
> My question is why is the most significant bit ignored?
>
> Does it have some significance or maybe not allowed
- Next message: Grei: "ListView scrollbar ?!"
- Previous message: LP: "Delegates vs. Events vs. AsyncCallback"
- In reply to: Just Me: "Most significant bit in WM_COMMAND wparam"
- Next in thread: Just Me: "Re: Most significant bit in WM_COMMAND wparam"
- Reply: Just Me: "Re: Most significant bit in WM_COMMAND wparam"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
