|
Hi, does someone know how can i detect the directional button presses in a Visual C++ Application. Thanks
|
|
|
|
|
The direction keys work like the standard keyboard keys VK_UP and the others...
|
|
|
|
|
ok, thanks 
|
|
|
|
|
Well, if you have a CListCtrl, you can use that function:
void CList::OnKeydownList(NMHDR* pNMHDR, LRESULT* pResult)
{
LV_KEYDOWN* pLVKeyDow = (LV_KEYDOWN*)pNMHDR;
// TODO: Add your control notification handler code here
if(GetAsyncKeyState(VK_UP))
{
......
}
Hope that helps 
Frank
_____ easySMS for pocket PC _____
www.Siedler-Net.de/WinCE/easySMS/
|
|
|
|
|
Has anyone got any experience of programming for the Symbian OS? If so what tools do you use, and can you recommend any books on the matter, in particular the Sony/Ericsson P800?
Andy
|
|
|
|
|
Download latest SDK (C++/Java/OPL/VB) from Symbian developer website. You will find many sample programs that can get you started quickly. I have used C++ SDK. It is highly object oriented and expected development style took sometime initially.
HTH,
Junkie
"* Code till death *"
http://www.askarya.com
|
|
|
|
|
Hi,
Is it possible to start a user mode process from a kernel mode driver?
Thanks in advance.
Shivpal
|
|
|
|
|
I want to disable all of the items in commandbar, but it doesn't seem to be working. Here's what I'm doing:
if (m_menuBarPtr)
{
m_menuBarPtr = GetMenu();
}
if (m_menuBarPtr)
{
MessageBeep(0);
UINT menuStyle = MF_BYPOSITION | ((m_currentBar == 0) ? MF_ENABLED : MF_GRAYED);
m_menuBarPtr->EnableMenuItem(0, menuStyle);
m_menuBarPtr->EnableMenuItem(1, menuStyle);
m_menuBarPtr->EnableMenuItem(2, menuStyle);
m_menuBarPtr->EnableMenuItem(3, menuStyle);
}
I've also tried setting ther m_menuBarPtr by using the return value of the CCeCommandBar::InsertMenu() function.
If you'll notice the
MessageBeep(0); call, I hear that beep when this code is encountered, indicating that I do indeed have a valid CMenu*, but the menu items are still active. According to the CE help, MF_DISABLED is not supported by CE (what an arbitrarily stupid f***ing decision on Microsoft's part), so I can't use it (although I did try it just to make sure, and of course, my app wouldn't compile with it included in the code).
Why does the interface stuff in CE suck so bad? Why is the documentation a complete waste of a CD? Why hasn't there been a decent book written for PPC2K2 development?
BTW, I also added this line in the constructor to CMainFrame
m_bAutoMenuEnable = FALSE;
------- signature starts
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
Please review the Legal Disclaimer in my bio.
------- signature ends
|
|
|
|
|
John Simmons / outlaw programmer wrote:
Why does the interface stuff in CE suck so bad?
Well, it really is not what you think. The menu visual element is not a menu, but instead a toolbar button. If you want to disable them, you have to know their IDs, which start at 0xF000 (yes, I had to go to MFC's source again).
So, to do what you want, here's a suggestion:
m_wndCommandBar.SendMessage(TB_ENABLEBUTTON, 0xf000, MAKELONG(FALSE,0));
m_wndCommandBar.SendMessage(TB_ENABLEBUTTON, 0xf001, MAKELONG(FALSE,0));
Intuitive, right?
|
|
|
|
|
Oh yeah "intuitive" is always a word I've associated with PocketPC coding.
Here's a new one for you though (or maybe not).
Taking your "they're just buttons" thing one step further, I decided to try also disabling the buttons on the commandbar with the same code. Since the buttons have their own ID's, I decided to try using those ID's in the command instead of the "0xf000" thing.
Well, they were disabled until the new toolbar was displayed, and then they re-enabled themselves. Hmmmm... I tried putting the enable/diable code into the OnUpdate... functions for those buttons, but that effectively made the buttons blink.
I also tried using 0xf004, 0xf005, and 0xf005 (three buttons), but they didn't get disabled at all that way.
Lastly, I tried just using indexes of 0, 1, and 2 - of course, that didn't work any better than the 0xf00n attempt.
As an aside, after the menu items are disabled, the last menu item is graphically truncated - instead of reading "Config", it reads "Con" and you can see one pixel's worth of the "F" in "Config".
Have I mentioned yet that I hate PPC2K2 UI development?
------- signature starts
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
Please review the Legal Disclaimer in my bio.
------- signature ends
|
|
|
|
|
John Simmons / outlaw programmer wrote:
Oh yeah "intuitive" is always a word I've associated with PocketPC coding.
That was an obvious joke (forgot the smiley, though). As a matter of fact, if you want to do anything serious about UI development for the PPC 2002, you gotta read the MFC source. And for two reasons: 1) the eVC help sucks and 2) it is incomplete, at best.
John Simmons / outlaw programmer wrote:
"they're just buttons"
I only figured that out some 10 minutes before posting the message. And being toolbar buttons may explain some of the bizarre functionality you are experimenting.
As for regular buttons, I think you need to access the underlying CToolBarCtrl object through GetToolBarCtrl(), just like I did in my last article on multiple toolbars. When you have a reference to that object, call EnableButton(nID, bEnable) where nID is the button ID and bEnable is the enabling / disabling BOOL.
John Simmons / outlaw programmer wrote:
Have I mentioned yet that I hate PPC2K2 UI development?
Not explicitly, but I did figure it out from your previous posts...
|
|
|
|
|
João Paulo Figueira wrote:
That was an obvious joke (forgot the smiley, though). As a matter of fact, if you want to do anything serious about UI development for the PPC 2002, you gotta read the MFC source. And for two reasons: 1) the eVC help sucks and 2) it is incomplete, at best.
Yeah I know.
João Paulo Figueira wrote:
As for regular buttons, I think you need to access the underlying CToolBarCtrl object through GetToolBarCtrl(), just like I did in my last article on multiple toolbars. When you have a reference to that object, call EnableButton(nID, bEnable) where nID is the button ID and bEnable is the enabling / disabling BOOL.
I already tried that, and I get the same behaviour as before (they disable for a split second, and then get re-enabled somehow.
I guess I'll keep pounding on it, but if you happen to run across anything, don't be shy about sharing it.
------- signature starts
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
Please review the Legal Disclaimer in my bio.
------- signature ends
|
|
|
|
|
John Simmons / outlaw programmer wrote:
I already tried that, and I get the same behaviour as before (they disable for a split second, and then get re-enabled somehow.
Are you using this technique with OnUpdate... handlers? They should be mutually exclusive.
John Simmons / outlaw programmer wrote:
I guess I'll keep pounding on it, but if you happen to run across anything, don't be shy about sharing it.
You bet!
|
|
|
|
|
If I put that code into OnUpdate, the buttons appear to blink.
------- signature starts
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
Please review the Legal Disclaimer in my bio.
------- signature ends
|
|
|
|
|
I'm actually suggesting not using OnUpdate. Try updating the buttons without these handlers.
|
|
|
|
|
I only tried OnUpdate after nothing else worked.
------- signature starts
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
Please review the Legal Disclaimer in my bio.
------- signature ends
|
|
|
|
|
I'm starting a new replay layer for this topic.
------- signature starts
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
Please review the Legal Disclaimer in my bio.
------- signature ends
|
|
|
|
|
Hi,
In my app, I do not face any such problem. I have followed this thread, and am still not getting it. I'm compiling on evc3.0 PPC2000,but I think this should work with PPC2002 too. here's what I do to enable/disable menuitems and buttons on commandbars(new toolband). FOr every new item, I map UPDATE_COMMAND_UI(), where based on a variable I toggle Enable flag like:
void CMainFrame::OnUpdateAddfiles(CCmdUI* pCmdUI)
{
// TODO: Add your command update UI handler code here
if(m_bAddFiles)
{
pCmdUI->Enable(TRUE);
// EnableMenuItem(TEXT("Archive"),TEXT("Add Files"),TRUE);
}
else
{
pCmdUI->Enable(FALSE);
// EnableMenuItem(TEXT("Archive"),TEXT("Add Files"),FALSE);
}
}
BOOL CMainFrame::EnableMenuItem(LPCTSTR szParent,LPCTSTR szChild,BOOL bEnable)
{
CMenu *pMenu = GetMenu();
int pos = FindMenuItem(pMenu, szParent);
if (pos == -1)
return FALSE;
CMenu* submenu = pMenu->GetSubMenu(pos);
int nPos = FindMenuItem(submenu,szChild);
if(nPos == -1)
return FALSE;
if(!bEnable)
submenu->EnableMenuItem(nPos,MF_BYPOSITION|MF_GRAYED);
else
submenu->EnableMenuItem(nPos,MF_BYPOSITION|MF_ENABLED);
return TRUE;
}
BOOL CMainFrame::EnableCommandBarItem(UINT nID, BOOL bEnable)
{
CToolBarCtrl& pCtrl = m_wndCommandBar.GetToolBarCtrl();
pCtrl.EnableButton(nID,bEnable);
return TRUE;
}
BOOL CMainFrame::EnableToolbarItem(UINT nID, BOOL bEnable)
{
CToolBarCtrl& pCtrl = m_wndToolBar.GetToolBarCtrl();
pCtrl.EnableButton(nID,bEnable);
return TRUE;
}
finally, whenever I set m_bAddFiles to TRUE, toolbar button gets enabled and viceversa. EnableCOmmandBarItem() and EnableToolbarItem() is what I tried too, but without ON_UPDATE_UI handlers, things don't happen.
What do you think?
Hush,hush...
thought I heard you call my name now.
Kula Shaker.
Amit Dey
Latest articles at CP -
PocketPC New menu
Office addin
|
|
|
|
|
Amit Dey wrote:
I think this should work with PPC2002 too
This might be the problem, Amit. Both me and John experienced the same problem on the PPC 2002, and this led me to write an article on the subject. Have a look at it here: Disabling top-level popup menus in the PocketPC 2002
[^]
|
|
|
|
|
Alrightie... More information:
I decided to see what would happen if I removed the toolbar from the commandbar, leaving just the menu. When I disabled all of the menu items, the "Config" menu item (the last one in the menu) was no longer truncated when it was disabled.
This leads me to believe there's a bug somewhere in the MFC CCeCommandBar code.
For what it's worth, I still haven't figured out why the buttons in the toolbar don't stay disabled, but I think it might be because I'm not telling the commandbar they're disabled, so it might be re-enabling them on it's own.
------- signature starts
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
Please review the Legal Disclaimer in my bio.
------- signature ends
|
|
|
|
|
John Simmons / outlaw programmer wrote:
This leads me to believe there's a bug somewhere in the MFC CCeCommandBar code.
You mean: just one bug? Oh, dear...
John Simmons / outlaw programmer wrote:
For what it's worth, I still haven't figured out why the buttons in the toolbar don't stay disabled, but I think it might be because I'm not telling the commandbar they're disabled, so it might be re-enabling them on it's own.
Is it possible that I take a look at you code? We could try to solve this in parallel...
|
|
|
|
|
CCeCommandBar m_wndCommandBar;
CToolBar m_barProcess;
CToolBar m_barAnnotate;
CToolBar m_barZoom;
CToolBar m_barVideo;
CToolBar m_barAVI;
UINT m_currentBar;
int CMainFrame::OnCreate(LPCREATESTRUCT lpCreateStruct)
{
m_menuBarPtr = NULL;
m_currentBar = 0;
if (CFrameWnd::OnCreate(lpCreateStruct) == -1)
{
return -1;
}
m_wndCommandBar.m_bShowSharedNewButton = FALSE;
m_ToolTipsTable[0] = MakeString(IDS_NEW);
m_ToolTipsTable[1] = MakeString(IDS_FILE);
m_ToolTipsTable[2] = MakeString(IDS_MHELP);
m_ToolTipsTable[3] = MakeString(IDS_CUT);
m_ToolTipsTable[4] = MakeString(IDS_COPY);
m_ToolTipsTable[5] = MakeString(IDS_PASTE);
m_ToolTipsTable[6] = MakeString(IDS_ABOUT);
if (!m_wndCommandBar.Create(this))
{
TRACE(_T("Failed to create CommandBar\n"));
return -1;
}
m_menuBarPtr = m_wndCommandBar.InsertMenuBar(IDR_MAINFRAME);
if (!m_menuBarPtr ||
!m_wndCommandBar.InsertSeparator() ||
!m_wndCommandBar.AddAdornments() ||
!m_wndCommandBar.LoadToolBar(IDR_MAINFRAME) ||
!m_wndCommandBar.SendMessage(TB_SETTOOLTIPS, (WPARAM)(7), (LPARAM)(m_ToolTipsTable)))
{
TRACE(_T("Failed to create CommandBar\n"));
return -1;
}
m_wndCommandBar.SetBarStyle(m_wndCommandBar.GetBarStyle() | CBRS_TOOLTIPS | CBRS_FLYBY | CBRS_SIZE_FIXED);
if (!CreateOtherCommandBars())
{
TRACE(_T("Failed to create one or more supplementary CommandBars\n"));
return -1;
}
return 0;
}
BOOL CMainFrame::CreateOtherCommandBars()
{
m_currentBar = IDR_MAINFRAME;
UINT barStyle = WS_CHILD | CBRS_BOTTOM | CBRS_BORDER_TOP;
CRect rcBorder(0, 1, 0, 0);
if (!m_barProcess.CreateEx(this, TBSTYLE_FLAT, barStyle, rcBorder, AFX_IDW_TOOLBAR+1) ||
!m_barProcess.LoadToolBar(IDR_PROCESSBAR))
{
TRACE(_T("Failed to create process toolbar\n"));
return FALSE;
}
if (!m_barAnnotate.CreateEx(this, TBSTYLE_FLAT, barStyle, rcBorder, AFX_IDW_TOOLBAR+2) ||
!m_barAnnotate.LoadToolBar(IDR_ANNOTATEBAR))
{
TRACE(_T("Failed to create annotate toolbar\n"));
return FALSE;
}
if (!m_barZoom.CreateEx(this, TBSTYLE_FLAT, barStyle, rcBorder, AFX_IDW_TOOLBAR+3) ||
!m_barZoom.LoadToolBar(IDR_ZOOMBAR))
{
TRACE(_T("Failed to create zoom toolbar\n"));
return FALSE;
}
if (!m_barVideo.CreateEx(this, TBSTYLE_FLAT, barStyle, rcBorder, AFX_IDW_TOOLBAR+4) ||
!m_barVideo.LoadToolBar(IDR_VIDEOBAR))
{
TRACE(_T("Failed to create live video toolbar\n"));
return FALSE;
}
if (!m_barAVI.CreateEx(this, TBSTYLE_FLAT, barStyle, rcBorder, AFX_IDW_TOOLBAR+5) ||
!m_barAVI.LoadToolBar(IDR_AVIBAR))
{
TRACE(_T("Failed to create avi toolbar\n"));
return FALSE;
}
return TRUE;
}
void CMainFrame::ShowThisBar(UINT newBar)
{
switch (m_currentBar)
{
case IDR_PROCESSBAR : m_barProcess.ShowWindow(SW_HIDE); break;
case IDR_ANNOTATEBAR : m_barAnnotate.ShowWindow(SW_HIDE); break;
case IDR_ZOOMBAR : m_barZoom.ShowWindow(SW_HIDE); break;
case IDR_VIDEOBAR : m_barVideo.ShowWindow(SW_HIDE); break;
case IDR_AVIBAR : m_barAVI.ShowWindow(SW_HIDE); break;
default : break;
}
switch (newBar)
{
case IDR_PROCESSBAR : m_barProcess.ShowWindow(SW_SHOW); break;
case IDR_ANNOTATEBAR : m_barAnnotate.ShowWindow(SW_SHOW); break;
case IDR_ZOOMBAR : m_barZoom.ShowWindow(SW_SHOW); break;
case IDR_VIDEOBAR : m_barVideo.ShowWindow(SW_SHOW); break;
case IDR_AVIBAR : m_barAVI.ShowWindow(SW_SHOW); break;
default : break;
}
m_currentBar = newBar;
BOOL bEnable = (m_currentBar == 0);
m_wndCommandBar.GetToolBarCtrl().EnableButton(ID_NEXT_IMAGE, bEnable);
m_wndCommandBar.GetToolBarCtrl().EnableButton(ID_PREV_IMAGE, bEnable);
m_wndCommandBar.GetToolBarCtrl().EnableButton(ID_REMOVE_IMAGE, bEnable);
m_wndCommandBar.SendMessage(TB_ENABLEBUTTON, 0xf000, MAKELONG(bEnable,0));
m_wndCommandBar.SendMessage(TB_ENABLEBUTTON, 0xf001, MAKELONG(bEnable,0));
m_wndCommandBar.SendMessage(TB_ENABLEBUTTON, 0xf002, MAKELONG(bEnable,0));
m_wndCommandBar.SendMessage(TB_ENABLEBUTTON, 0xf003, MAKELONG(bEnable,0));
RecalcLayout(TRUE);
}
------- signature starts
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
Please review the Legal Disclaimer in my bio.
------- signature ends
|
|
|
|
|
Unless I'm really missing something here, the code should work. You have removed the OnUpdate handlers, right? 
|
|
|
|
|
Right.
------- signature starts
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
Please review the Legal Disclaimer in my bio.
------- signature ends
|
|
|
|
|
I'm experiencing the same problem with my code. Apparently, there is some bug int the CCeCommandBar code because when I disable the menu "buttons", I also get the same "clipping" problem. I'll check it out and get back to you.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
