I guess this is related to NC messages
-
Hello to everyone, I have developed a SDI MFC application. So what I want is when my mouse is hovering over the application window (any window.. main window, title, views anything), it should work properly, As the mouse moves out of application or windows , it should give some dialog box message that you are out of application area. now if mouse goes out of scope then it should not give so many dialog box messages.. only one is enough so that I wont be wasting time destryoying those messageboxes and go straight to application area. How can this be made? row
-
Hello to everyone, I have developed a SDI MFC application. So what I want is when my mouse is hovering over the application window (any window.. main window, title, views anything), it should work properly, As the mouse moves out of application or windows , it should give some dialog box message that you are out of application area. now if mouse goes out of scope then it should not give so many dialog box messages.. only one is enough so that I wont be wasting time destryoying those messageboxes and go straight to application area. How can this be made? row
-
if ur tracking the mouse leaving by checking the NC messages u should have to keep the flags to prevent multiple message box beign displayed... Else use
TrackMouseEventAPI naveI think TrackMouseEvent will be tracking only client area of the window . (also which handler I would be keeping this function) What I want is if the mouse is moving or clicking or hovering on any portion of the window, its ok, but when it completely goes out of application windows then it should give some kind of notification. -- modified at 8:04 Monday 19th June, 2006
-
Hello to everyone, I have developed a SDI MFC application. So what I want is when my mouse is hovering over the application window (any window.. main window, title, views anything), it should work properly, As the mouse moves out of application or windows , it should give some dialog box message that you are out of application area. now if mouse goes out of scope then it should not give so many dialog box messages.. only one is enough so that I wont be wasting time destryoying those messageboxes and go straight to application area. How can this be made? row
Use global or class variables to determine if message is already on screen. I guess I solve your problem? :~
-
I think TrackMouseEvent will be tracking only client area of the window . (also which handler I would be keeping this function) What I want is if the mouse is moving or clicking or hovering on any portion of the window, its ok, but when it completely goes out of application windows then it should give some kind of notification. -- modified at 8:04 Monday 19th June, 2006
Along with what naveen said use
WM_MOUSELEAVE.
Nibu thomas A Developer Programming tips[^] My site[^]
-
Use global or class variables to determine if message is already on screen. I guess I solve your problem? :~
-
I think TrackMouseEvent will be tracking only client area of the window . (also which handler I would be keeping this function) What I want is if the mouse is moving or clicking or hovering on any portion of the window, its ok, but when it completely goes out of application windows then it should give some kind of notification. -- modified at 8:04 Monday 19th June, 2006
-
ROWALI wrote:
I think TrackMouseEvent will be tracking only client area of the window .
no. check the dwFlags of the TRACKMOUSEEVENT structure.There u can find TME_NONCLIENT nave