[Bug 40244] New: PostThreadMessage with WM_NOTIFY message should succeed

https://bugs.winehq.org/show_bug.cgi?id=40244

Bug ID: 40244
           Summary: PostThreadMessage with WM_NOTIFY message should
                    succeed
           Product: Wine
           Version: 1.9.4
          Hardware: x86
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: user32
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

The issue was encountered by a user in the #winehq channel while testing a
company-internal application in Wine. Based on the provided log file I've
tracked it down to the following few lines:

--- snip ---
0009:Call user32.PostThreadMessageA(00000028,0000004e,00000001,00000466)
ret=0051258b
0009:Call winex11.drv.GetKeyboardLayout(00000000) ret=7e9a8476
0009:Ret  winex11.drv.GetKeyboardLayout() retval=04090409 ret=7e9a8476
0009:Ret  user32.PostThreadMessageA() retval=00000000 ret=0051258b
0009:Call user32.LoadStringA(00400000,0000ffc9,0033e820,00001000) ret=004071c7
0009:Ret  user32.LoadStringA() retval=00000010 ret=004071c7
0009:Call KERNEL32.RaiseException(0eedfade,00000001,00000007,0033f880)
ret=005125c6
0009:trace:seh:raise_exception code=eedfade flags=1 addr=0x7b83b77c ip=7b83b77c
tid=0009
[...]
--- snip ---

The application is not really happy about the result of PostThreadMessageA. A
quick test confirms that sending WM_NOTIFY should succeed, which means Wines
is_pointer_message() function is a bit too strict here.

I'll prepare some more tests and a patch to fix it, this bug is just to keep
track of the issue.