![]() |
Short cut keys apply when an edit field has focus |
Post Reply ![]() |
Author | |
JamesH ![]() Senior Member ![]() Joined: 01 December 2004 Status: Offline Points: 149 |
![]() ![]() ![]() ![]() ![]() Posted: 16 June 2006 at 1:19pm |
I have mentioned this issue before when I first discovered it with the report control here.
However, I am now having the exact same issue but with a property grid.
If you have a short cut key assigned to a command bar item this key can not be used when editing a property grid or report control. This seems rediculous. Our application (as do many others, eg. visual stuido) has many short keys that are needed for entering information when a property grid or report control cell is in edit mode.
This seems like a major flaw and makes using command bar short cuts virtually usless.
![]() Does anyone have a suggestion for a work-around? Surely this must be an issue for other people.
|
|
![]() |
|
markh ![]() Groupie ![]() Joined: 12 November 2003 Location: United Kingdom Status: Offline Points: 49 |
![]() ![]() ![]() ![]() ![]() |
I agree this is a major problem with shortcut keys. Basically it seems that any child, of the frame window that contains the CommandBars object, doesn't receive any WM_KEYDOWN messages if the key happens to be used as a shortcut in CommandBars. This occurs irrespective of the focus and is impossible to override. I am having the same problem with a RichEdit control hosted in a DockingWindow. All of the shortcuts for the RichEdit such as Ctrl-C for copy are routed to CommandBars rather than being received by the control itself.
There definitely needs to be some mechanism of allowing the focus window to handle the message first before it is passed to CommandBars. I would have thought this could be done by first allowing the focus window to handle the keydown message and only passing it to CommandBars if it is not handled.
Without this mechanism the shortcut key system is useless for many apps and indeed I have stopped using it.
Any ideas of a way round this problem would be greatly appreciated.
|
|
![]() |
|
JamesH ![]() Senior Member ![]() Joined: 01 December 2004 Status: Offline Points: 149 |
![]() ![]() ![]() ![]() ![]() |
It's good to hear I'm not the only one with this problem, not so great to hear the only work-around suggested so far is not use accelleartor keys.
This is seems crazy. Is anyone using the accellerator keys?
|
|
![]() |
|
vb1to6 ![]() Newbie ![]() Joined: 23 November 2005 Location: United States Status: Offline Points: 11 |
![]() ![]() ![]() ![]() ![]() |
I use the WinHook control of the Desaware SpyWorks v7.1 to workaround the issue of turning off the Accelerator Keys of the CommandBar 9.81 and still getting the functionality I needed within complex VB 6.0 MDI applications. I capture the accelerator keys on the MDI form and post them for the toolbar in code. I'm not saying it is not a drag to get around the "undocumented feature" of the CommandBar, however it beats the hell out of re-coding the entire project. |
|
![]() |
|
Oleg ![]() Admin Group ![]() Joined: 21 May 2003 Location: United States Status: Offline Points: 11234 |
![]() ![]() ![]() ![]() ![]() |
Hi,
Actually... BeforeTranslate event of 10.3 release can help....
|
|
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS |
|
![]() |
Post Reply ![]() |
|
Tweet
|
Forum Jump | Forum Permissions ![]() You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |