D
Denis Dmitriev
Hello,
I'm looking for a way to attach keyboard shortcuts to the CommandBar buttons
my COM add-in creates (the add-in is hosted in Word, but a solution that'd
also work in PowerPoint would be nice), preferrably without using any VBA
glue. Unfortunately, I don't have the luxury of picking my own shortcuts
right now, and the ones I have to use cannot be handled by adding a
strategically placed ampersand to the caption.
I tried playing around with KeyBindings, but this went nowhere, as the
callbacks into the add-in are neither commands nor macros (hence, for
example, binding a key to
`Application.COMAddIns.Item(...).Object.ButtonPress(1)` didn't work).
I'm trying to stay away from creating VBA macros at runtime as that'd
pollute user documents. Also, while VBA glue could be placed in a template,
installing it in all the right user accounts is a mess and a maintenance
issue. As for the COM add-in loading a global template at run-time---it
sounds exactly like something the system administrator may disallow.
So the question is, is there some way to create my own custom commands and
attach them to my buttons, so that wdKeyCategoryCommand may be used? Or is
there some other approach (not necessarily pretty or elegant---`working` is
the key) that could be used to attach keyboard shortcuts to my buttons while
staying away from VBA?
Thanks,
Denis.
I'm looking for a way to attach keyboard shortcuts to the CommandBar buttons
my COM add-in creates (the add-in is hosted in Word, but a solution that'd
also work in PowerPoint would be nice), preferrably without using any VBA
glue. Unfortunately, I don't have the luxury of picking my own shortcuts
right now, and the ones I have to use cannot be handled by adding a
strategically placed ampersand to the caption.
I tried playing around with KeyBindings, but this went nowhere, as the
callbacks into the add-in are neither commands nor macros (hence, for
example, binding a key to
`Application.COMAddIns.Item(...).Object.ButtonPress(1)` didn't work).
I'm trying to stay away from creating VBA macros at runtime as that'd
pollute user documents. Also, while VBA glue could be placed in a template,
installing it in all the right user accounts is a mess and a maintenance
issue. As for the COM add-in loading a global template at run-time---it
sounds exactly like something the system administrator may disallow.
So the question is, is there some way to create my own custom commands and
attach them to my buttons, so that wdKeyCategoryCommand may be used? Or is
there some other approach (not necessarily pretty or elegant---`working` is
the key) that could be used to attach keyboard shortcuts to my buttons while
staying away from VBA?
Thanks,
Denis.