How to capture ON_WM_DEVICECHANGE using Toolkit Pr

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I think that the CXTPTopLevelWndMsgNotifier installs itself as the top-most window in a XTPToolKitPro derived application. As a result, it becomes the receipent of the "WM_DEVICECHANGE" message. My question is if there is a method by which to easily capture/forward this to a more useful window (for my application).

I'm trying to detect when USB devices connect/disconnect to gracefully handle it in my application logic.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
djesling Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 08 September 2003 Status: Offline Points: 3	Post Options Post Reply Quote djesling Report Post Thanks(0) Quote Reply Topic: How to capture ON_WM_DEVICECHANGE using Toolkit Pr Posted: 25 February 2009 at 2:00pm
	I think that the CXTPTopLevelWndMsgNotifier installs itself as the top-most window in a XTPToolKitPro derived application. As a result, it becomes the receipent of the "WM_DEVICECHANGE" message. My question is if there is a method by which to easily capture/forward this to a more useful window (for my application). I'm trying to detect when USB devices connect/disconnect to gracefully handle it in my application logic.

Oleg Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 21 May 2003 Location: United States Status: Offline Points: 11234	Post Options Post Reply Quote Oleg Report Post Thanks(0) Quote Reply Posted: 26 February 2009 at 3:47am
	Why you can't catch it in CMainFrame ?
	Oleg, Support Team CODEJOCK SOFTWARE SOLUTIONS

djesling Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 08 September 2003 Status: Offline Points: 3	Post Options Post Reply Quote djesling Report Post Thanks(0) Quote Reply Posted: 19 March 2009 at 12:50pm
	Turns out I can capture it in all windows, my suspicion was incorrect and misdirected by MSDN. After figuring out how to read I added it and it works wonderfully. Thanks