locked
WM_ ????? 0x00AE RRS feed

  • Question

  • Please

    If you know what windows message is the message 0x00AE  let me know

    I just spend 3 hours searching for that

    Tuesday, November 16, 2010 10:47 PM

Answers

  • Apparently, 0x00AE and 0x00AF are undocumented windows messages related to themes:

    WM_NCUAHDRAWCAPTION = 0x00AE

    WM_NCUAHDRAWFRAME = 0x00AF

     


    Tom Shelton
    • Marked as answer by Crazypennie Wednesday, November 17, 2010 3:05 AM
    Wednesday, November 17, 2010 1:43 AM

All replies

  • It's a failure to obtain a new (or modify an existing) filesystem lock.

    EDIT: I copy/pasted the wrong link address previously - this one is to MSDN, last was to some 3rd party troubleshooting site that wants you to download antispyware junk.

    What context are you seeing it in?


    It never hurts to try. In a worst case scenario, you'll learn from it.
    • Edited by Andrew B. Painter Tuesday, November 16, 2010 11:48 PM
    • Marked as answer by Crazypennie Wednesday, November 17, 2010 12:19 AM
    • Unmarked as answer by Crazypennie Wednesday, November 17, 2010 12:37 AM
    Tuesday, November 16, 2010 11:35 PM
  • I am bypassing the WDM and doing my own glass effect in the NC area of a form.

    Getting nicer and less boring effect. But this message pops time to time and is causing some problems

    Tuesday, November 16, 2010 11:48 PM
  • Sounds like you need to check the locking status of an object before exercising a direct API call?

    It never hurts to try. In a worst case scenario, you'll learn from it.
    Tuesday, November 16, 2010 11:50 PM
  • this glass is kind of complicated thing to do, have to handle all the messages to the non client area and the documentation about defWinproc is very limitated. however, I got 95% under control now

    -I can set the NC area the size I want

    -Min Max and close button are implemented

    -the system drop down menu is done

    -All the events fire

    -the NCPAINT is almost ok

    -WM_MINMAXINFO works

    _WM_NCHITTEST, WM_NCSYSCOMMAND works

    Now, i am working on the form shadow

    Wednesday, November 17, 2010 12:19 AM
  • ANDEW, I cannot connect this message to the link on your post ... Are you sure that this is the meaning of this message
    Wednesday, November 17, 2010 12:39 AM
  • ANDEW, I cannot connect this message to the link on your post ... Are you sure that this is the meaning of this message


    I'm absolutely positive that 0xAE is 174 and I'm absolutely positive that Error 174 correlates to the entry on that MSDN Page.

    The only thing I'm not absolutely positive of is that the actual error you're actually receiving is 0xAE.

    You should bear in mind that sometimes when working with the Windows API, Err.Number and Err.LastDLLError (in VB) and the Windows API function GetLastError in kernel32.DLL will all return different values (sometimes one or two are the same and the other is off).  Sometimes a Try-Catch works with API errors in VB and sometimes it doesn't.

    Where did you get the value 0xAE?


    It never hurts to try. In a worst case scenario, you'll learn from it.
    Wednesday, November 17, 2010 12:50 AM
  • This is a click on the Non Client area :

    0x84 WM_NCHITTEST  WParam = 0  LParam = 3F019C
    0x84 WM_NCHITTEST  WParam = 0  LParam = 3F019C
    0x20 WM_SETCURSOR  WParam = 5104FE  LParam = 2000002
    0xA0 WM_NCMOUSEMOVE  WParam = 2  LParam = 3F019C
    0x84 WM_NCHITTEST  WParam = 0  LParam = 3F019C
    0x84 WM_NCHITTEST  WParam = 0  LParam = 3F019C
    0x20 WM_SETCURSOR  WParam = 5104FE  LParam = 2010002
    0xA1 WM_NCLBUTTONDOWN  WParam = 2  LParam = 3F019C
    0xAE WM_?????  WParam = 1001  LParam = 0
    0x112 WM_SYSCOMMAND  WParam = F012  LParam = 3F019C
    0x215 WM_CAPTURECHANGE  WParam = 0  LParam = 0
    0x46 WM_WINDOWPOSCHANGING  WParam = 0  LParam = 1D04BDD0
    0x2A2 WM_NCMOUSELEAVE  WParam = 0  LParam = 0
    0x84 WM_NCHITTEST  WParam = 0  LParam = 3F019C
    0x84 WM_NCHITTEST  WParam = 0  LParam = 3F019C
    0x20 WM_SETCURSOR  WParam = 5104FE  LParam = 2000002
    0xA0 WM_NCMOUSEMOVE  WParam = 2  LParam = 3F019C

     

    I receive the window message 0x00AE ... But it does not appears to be an error notification message

    if it is an error notification the error number should be 0x1001 from the WParam value

    • Edited by Crazypennie Wednesday, November 17, 2010 1:07 AM
    Wednesday, November 17, 2010 12:57 AM
  • Wow... I don't have the faintest idea what that output is from.  Stack Trace on an app crash?  Your own log output?

    What API function are you actually passing WParam and LParam to - and what exactly is the nature of WParam and LParam?


    It never hurts to try. In a worst case scenario, you'll learn from it.
    Wednesday, November 17, 2010 1:02 AM
  • This a window message log of the messages dispatched from the message loop to the form handle

    This log is the messages sent by the operating system to the Form for a click on the non client area

    The MouseMove & CaptureChange comes from the fact that the mouse is captured to give the possibility to move the form from this click

    Wednesday, November 17, 2010 1:15 AM
  • OK, that changes the ballpark quite a lot.  Sorry.

    Are you sure 0x00AE isn't some custom value you're pushing through the API on some DotNET Event yourself?


    It never hurts to try. In a worst case scenario, you'll learn from it.
    Wednesday, November 17, 2010 1:24 AM
  • I am not using any API here, this is what the operating system tells the form when you click the window title bar
    Wednesday, November 17, 2010 1:28 AM
  • Found the following in WinUser.h (under C:\Program Files\Microsoft SDKs\Windows\v6.0A\Include\WinUser.h) - I'm running Windows 7 x64 and Visual Studio 2008 Pro.  I don't know if this SDK actually came with VS or Windows or if it's one (of several) I might have installed at one time or another.

     

    #define WM_NCMOUSEMOVE     0x00A0
    #define WM_NCLBUTTONDOWN    0x00A1
    #define WM_NCLBUTTONUP     0x00A2
    #define WM_NCLBUTTONDBLCLK    0x00A3
    #define WM_NCRBUTTONDOWN    0x00A4
    #define WM_NCRBUTTONUP     0x00A5
    #define WM_NCRBUTTONDBLCLK    0x00A6
    #define WM_NCMBUTTONDOWN    0x00A7
    #define WM_NCMBUTTONUP     0x00A8
    #define WM_NCMBUTTONDBLCLK    0x00A9
    
    
    
    #if
    
    (_WIN32_WINNT >= 0x0500)
    #define WM_NCXBUTTONDOWN    0x00AB
    #define WM_NCXBUTTONUP     0x00AC
    #define WM_NCXBUTTONDBLCLK    0x00AD
    #endif /* _WIN32_WINNT >= 0x0500 */
    
    
    
    There is absolutely NO 0x00AE - it goes from 0x00AD straight on to 0x00FE.

     

    Maybe a funky monitor or device driver kicking gibberish back from kernel mode, or some message being sent by AntiVirus or other 3rd Party system software on your machine?

     

    Any way you can get a lock on the sender of an individual message?


    It never hurts to try. In a worst case scenario, you'll learn from it.
    Wednesday, November 17, 2010 1:32 AM
  • You can considere this as the operating system events for a click ... I can implement the code for those or ask DefWinProc to do it for me.

    However, for what I am doing I have to do the implementation.

    The problem, is the operating system is expecting also a return value .. These event are not Void, they are function ...

    And I cant handle the 0x00AE since I dont know what it is. If I ignore it or have  DefWinProc to handle it, most of the time it makes no problem, but sometime, it bugs

    Wednesday, November 17, 2010 1:38 AM
  • Only other possibility is:

    #define VK_VOLUME_DOWN 0xAE

    Also from WinUser.h ... I guess if the message queue expects everything to be WM_ and it hits a VK_ it could explain what's happening there with the WM_???? output, but I'd say that's a pretty long long-shot.

    Either way, I've got pork chops waiting on me. Going to have to pick this up tomorrow if somebody else doesn't help you resolve it tonight.


    It never hurts to try. In a worst case scenario, you'll learn from it.
    Wednesday, November 17, 2010 1:41 AM
  • Apparently, 0x00AE and 0x00AF are undocumented windows messages related to themes:

    WM_NCUAHDRAWCAPTION = 0x00AE

    WM_NCUAHDRAWFRAME = 0x00AF

     


    Tom Shelton
    • Marked as answer by Crazypennie Wednesday, November 17, 2010 3:05 AM
    Wednesday, November 17, 2010 1:43 AM
  • Where'd you find that, Tom?
    It never hurts to try. In a worst case scenario, you'll learn from it.
    Wednesday, November 17, 2010 1:48 AM
  • Thanks Tom,

      This is giving me ta least  a start to search

    Wednesday, November 17, 2010 1:50 AM
  • Googled 0x00AE.

    Tom Shelton
    Wednesday, November 17, 2010 1:57 AM
  • Nice Google-fu.  I kept trying to tack wm_ onto the front of the hex and decimal search term and I kept getting hits on this thread and then a lot of hits on WINE.

     


    It never hurts to try. In a worst case scenario, you'll learn from it.
    Wednesday, November 17, 2010 2:06 AM
  • Thanks again Tom

    I found the info I needed from what you gave me in your post

    Luc

    Wednesday, November 17, 2010 3:05 AM