|
|
You're in the
dotnet compact framework
group:How to invoke menu item with SendMessage?
dotnet compact framework:
I thought it would be a simple matter to SendMessage(hWnd, WM_COMMAND,
commandId, lParam), where hWnd is the form window handle and lParam is 0. (Surprise... it doesn't work on a WM5 PPC.) Using CESpy, I can see that for real menu clicks, lParam is set to the handle of a window with a class name of "MS_SOFTKEY_CE_1.0". Sure enough, if I manually set lParam to this value in the debugger, SendMessage works as expected. So now the question is: How do I _reliably_ get the handle to this MS_SOFTKEY_CE_1.0 window? There can be any number of them at a given time. I need to know which one to use for the active form. Thanks!
Hi Peter,
Thanks for the response. Your blog has been helpful to me on more than one occasion. I'm able to find the softkey bar window (class "menu_worker") using SHFindMenuBar without any trouble. Its parent is the form hWnd, and it has no child windows, so that seems to be a dead end as far as finding the related MS_SOFTKEY_CE_1.0 window goes. I'm also able to find my form menu handle using the TB_GETBUTTONINFO message. GetMenu (SHCMBM_GETMENU) only works on the Smartphone platform, not on the PocketPC. But I still don't see any way to get the correct lParam value to use to send a WM_COMMAND message that will invoke a .NET CF menu command. -David [quoted text, click to view] "Peter Foot [MVP]" wrote:
> There is a softkey bar for each application potentially. I can't remember > but possibly the GetMenu API call will work - pass in the handle to your > main form and see what handle is returned. > > Regards, > > Peter > > -- > Peter Foot > Microsoft Device Application Development MVP > www.peterfoot.net | www.inthehand.com > In The Hand Ltd - .NET Solutions for Mobility > > "_dtaylorus" <dtaylorus@discussions.microsoft.com> wrote in message > news:F308EF11-E3B7-4189-9B17-50D5DC4B3CF3@microsoft.com... > >I thought it would be a simple matter to SendMessage(hWnd, WM_COMMAND, > > commandId, lParam), where hWnd is the form window handle and lParam is 0. > > (Surprise... it doesn't work on a WM5 PPC.) > > > > Using CESpy, I can see that for real menu clicks, lParam is set to the > > handle of a window with a class name of "MS_SOFTKEY_CE_1.0". > > > > Sure enough, if I manually set lParam to this value in the debugger, > > SendMessage works as expected. > > > > So now the question is: How do I _reliably_ get the handle to this > > MS_SOFTKEY_CE_1.0 window? There can be any number of them at a given > > time. > > I need to know which one to use for the active form. > > > > Thanks! > > -David
Problem solved. It turns out that the handle returned by SHFindMenuBar works
fine as the lParam for WM_COMMAND, even though CESpy shows a different lParam value if the menu is invoked normally by tapping on it. Thanks! [quoted text, click to view] "_dtaylorus" wrote:
> Hi Peter, > > Thanks for the response. Your blog has been helpful to me on more than one > occasion. > > I'm able to find the softkey bar window (class "menu_worker") using > SHFindMenuBar without any trouble. Its parent is the form hWnd, and it has > no child windows, so that seems to be a dead end as far as finding the > related MS_SOFTKEY_CE_1.0 window goes. > > I'm also able to find my form menu handle using the TB_GETBUTTONINFO > message. GetMenu (SHCMBM_GETMENU) only works on the Smartphone platform, not > on the PocketPC. > > But I still don't see any way to get the correct lParam value to use to send > a WM_COMMAND message that will invoke a .NET CF menu command. > > -David > > > > > > > > > > "Peter Foot [MVP]" wrote: > > > There is a softkey bar for each application potentially. I can't remember > > but possibly the GetMenu API call will work - pass in the handle to your > > main form and see what handle is returned. > > > > Regards, > > > > Peter > > > > -- > > Peter Foot > > Microsoft Device Application Development MVP > > www.peterfoot.net | www.inthehand.com > > In The Hand Ltd - .NET Solutions for Mobility > > > > "_dtaylorus" <dtaylorus@discussions.microsoft.com> wrote in message > > news:F308EF11-E3B7-4189-9B17-50D5DC4B3CF3@microsoft.com... > > >I thought it would be a simple matter to SendMessage(hWnd, WM_COMMAND, > > > commandId, lParam), where hWnd is the form window handle and lParam is 0. > > > (Surprise... it doesn't work on a WM5 PPC.) > > > > > > Using CESpy, I can see that for real menu clicks, lParam is set to the > > > handle of a window with a class name of "MS_SOFTKEY_CE_1.0". > > > > > > Sure enough, if I manually set lParam to this value in the debugger, > > > SendMessage works as expected. > > > > > > So now the question is: How do I _reliably_ get the handle to this > > > MS_SOFTKEY_CE_1.0 window? There can be any number of them at a given > > > time. > > > I need to know which one to use for the active form. > > > > > > Thanks! > > > -David
There is a softkey bar for each application potentially. I can't remember
but possibly the GetMenu API call will work - pass in the handle to your main form and see what handle is returned. Regards, Peter -- Peter Foot Microsoft Device Application Development MVP www.peterfoot.net | www.inthehand.com In The Hand Ltd - .NET Solutions for Mobility [quoted text, click to view] "_dtaylorus" <dtaylorus@discussions.microsoft.com> wrote in message
news:F308EF11-E3B7-4189-9B17-50D5DC4B3CF3@microsoft.com... >I thought it would be a simple matter to SendMessage(hWnd, WM_COMMAND, > commandId, lParam), where hWnd is the form window handle and lParam is 0. > (Surprise... it doesn't work on a WM5 PPC.) > > Using CESpy, I can see that for real menu clicks, lParam is set to the > handle of a window with a class name of "MS_SOFTKEY_CE_1.0". > > Sure enough, if I manually set lParam to this value in the debugger, > SendMessage works as expected. > > So now the question is: How do I _reliably_ get the handle to this > MS_SOFTKEY_CE_1.0 window? There can be any number of them at a given > time. > I need to know which one to use for the active form. > > Thanks! > -David
Great! Glad that resolved it. The differences between Menu architecture in
Pocket PC and Smartphone can be confusing (since they now are designed to look and behave more or less the same). Peter -- Peter Foot Microsoft Device Application Development MVP www.peterfoot.net | www.inthehand.com In The Hand Ltd - .NET Solutions for Mobility [quoted text, click to view] "_dtaylorus" <dtaylorus@discussions.microsoft.com> wrote in message
news:228CC2CA-F1A8-4602-9B5B-D14ACF7CDC61@microsoft.com... > Problem solved. It turns out that the handle returned by SHFindMenuBar > works > fine as the lParam for WM_COMMAND, even though CESpy shows a different > lParam > value if the menu is invoked normally by tapping on it. > > Thanks! > > "_dtaylorus" wrote: > >> Hi Peter, >> >> Thanks for the response. Your blog has been helpful to me on more than >> one >> occasion. >> >> I'm able to find the softkey bar window (class "menu_worker") using >> SHFindMenuBar without any trouble. Its parent is the form hWnd, and it >> has >> no child windows, so that seems to be a dead end as far as finding the >> related MS_SOFTKEY_CE_1.0 window goes. >> >> I'm also able to find my form menu handle using the TB_GETBUTTONINFO >> message. GetMenu (SHCMBM_GETMENU) only works on the Smartphone platform, >> not >> on the PocketPC. >> >> But I still don't see any way to get the correct lParam value to use to >> send >> a WM_COMMAND message that will invoke a .NET CF menu command. >> >> -David >> >> >> >> >> >> >> >> >> >> "Peter Foot [MVP]" wrote: >> >> > There is a softkey bar for each application potentially. I can't >> > remember >> > but possibly the GetMenu API call will work - pass in the handle to >> > your >> > main form and see what handle is returned. >> > >> > Regards, >> > >> > Peter >> > >> > -- >> > Peter Foot >> > Microsoft Device Application Development MVP >> > www.peterfoot.net | www.inthehand.com >> > In The Hand Ltd - .NET Solutions for Mobility >> > >> > "_dtaylorus" <dtaylorus@discussions.microsoft.com> wrote in message >> > news:F308EF11-E3B7-4189-9B17-50D5DC4B3CF3@microsoft.com... >> > >I thought it would be a simple matter to SendMessage(hWnd, WM_COMMAND, >> > > commandId, lParam), where hWnd is the form window handle and lParam >> > > is 0. >> > > (Surprise... it doesn't work on a WM5 PPC.) >> > > >> > > Using CESpy, I can see that for real menu clicks, lParam is set to >> > > the >> > > handle of a window with a class name of "MS_SOFTKEY_CE_1.0". >> > > >> > > Sure enough, if I manually set lParam to this value in the debugger, >> > > SendMessage works as expected. >> > > >> > > So now the question is: How do I _reliably_ get the handle to this >> > > MS_SOFTKEY_CE_1.0 window? There can be any number of them at a given >> > > time. >> > > I need to know which one to use for the active form. >> > > >> > > Thanks! >> > > -David >> >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |