[Bug 38759] New: WM_USER (and +1, +2) are being sent to application windows
https://bugs.winehq.org/show_bug.cgi?id=38759 Bug ID: 38759 Summary: WM_USER (and +1, +2) are being sent to application windows Product: Wine Version: 1.7.38 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jasonwinter(a)hotmail.com Distribution: --- My programs use WM_USER, WM_USER+1 and WM_USER+2 for various functions, but they seem to be sent these messages by WINE when the mouse moves around the window involved, possibly during repainting. This doesn't happen in Windows. I've changed my offsets of 0x0400 to add 0x0280 (I now start acting on messages at 0x0680 instead) and it's fixed - but it's clearly a bug in WINE. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38759 --- Comment #1 from Nikolay Sivov <bunglehead(a)gmail.com> --- Hi, Jason. Could you share a minimal test case application source that shows this problem? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38759 --- Comment #2 from Jason <jasonwinter(a)hotmail.com> --- Hi Nikolay, I'm glad you asked, as I realised I'm running Win-MONO on WINE for this software, so I should test that on Windows with MONO instead of making assumptions about WINE... It also fails there too, so it's a MONO bug, not a WINE bug. Anyway, this is a standard C# winforms project that shows the issue when the mouse passes over the window. using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Linq; using System.Text; using System.Windows.Forms; namespace TestWine { public partial class Form1 : Form { public Form1() { InitializeComponent(); } public const int WM_USER = 0x0400; protected override void WndProc(ref Message m) { switch (m.Msg) { case WM_USER: case WM_USER + 1: case WM_USER + 2: MessageBox.Show("Ouch! Msg=" + m.Msg); break; default: break; } base.WndProc(ref m); } } } Sorry for the bogus bug report, Jason. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38759 Jason <jasonwinter(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #3 from Jason <jasonwinter(a)hotmail.com> --- Resolving issue. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38759 Nikolay Sivov <bunglehead(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #4 from Nikolay Sivov <bunglehead(a)gmail.com> --- I see, so it's something it mono probably that makes use of WM_USER messages. Thanks for testing. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs@winehq.org