--Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andrew de Quincey
Sent: Friday, 5 December 2003 8:45 AM
To: wine-patches
Subject: menu: nasty bug in menu tracking
In IDA, the menus don't work correctly... as you move down a menu, the
wrong
item is highl
Andrew de Quincey <[EMAIL PROTECTED]> writes:
> IDA *is* changing what has been captured. If I add a
> MENU_SetCapture(hwndOwner); just after the WM_INITMENUPOPUP is sent, this
> fixes the problem. Is this an acceptable solution?
That depends on what Windows does. This will probably require wri
On Friday 05 December 2003 00:16, Mike Jackson wrote:
> Actually I think the code would work better like this:-
>
> if ((msg.message >= WM_MOUSEFIRST) && (msg.message <= WM_MOUSELAST))
> {
> mt.pt.x = (short)LOWORD(msg.lParam);
> mt.pt.y = (short)HIWORD(msg.lParam);
>
On Thursday 04 December 2003 23:34, Alexandre Julliard wrote:
> Andrew de Quincey <[EMAIL PROTECTED]> writes:
> > OK, I'll keep looking. I've printed out the coordinates I get in the
> > tracking loop. As soon as the popup menu is displayed, they are
> > immediately "off" by the position of the men
Andrew de Quincey <[EMAIL PROTECTED]> writes:
> OK, I'll keep looking. I've printed out the coordinates I get in the tracking
> loop. As soon as the popup menu is displayed, they are immediately "off" by
> the position of the menu on the top of the screen. Its fine on menus without
> popups.
P
On Thursday 04 December 2003 22:59, Alexandre Julliard wrote:
> Andrew de Quincey <[EMAIL PROTECTED]> writes:
> > The problem is that MSG.lParam is NOT necessarily in screen coordinates
> > (even though the comment I have removed says they are). As I can't trust
> > the MSG.pt either, this means us
Andrew de Quincey <[EMAIL PROTECTED]> writes:
> The problem is that MSG.lParam is NOT necessarily in screen coordinates (even
> though the comment I have removed says they are). As I can't trust the MSG.pt
> either, this means using GetCursorPos() to determine the mouse position in
> screen coo
