A
Andrey Starodoubtsev
Hi, all!..
There is some Outlook add-in, which creates its command bar. After this
command bar creation its .Protection will be set in msoBarNoCustomize +
msoBarNoVerticalDock + msoBarNoChangeDock - perfectly, in CommandBar
menu->Add or remove buttons this command bar name is grayed and we can't to
turn on/off button visibility on it. But we can change buttons order by
dragging them, can assign pictures to any button on this command bar, can
even remove button from command bar by dragging it out etc. - all of these
actions we'd like to prohibit.
This can be done - at the same Outlook version XTNDConnect and Nod32 are
installed, and all context menu items for this buttons are disabled.
Difference of these buttons from ours - they have .ID==32768 and
..FaceID=32768, but i can't to set this properties from add-in code, and i'm
afraid that this is indirect consequence of smth other mechanism of customize
prohibition.
Did you met similar problem?
There is some Outlook add-in, which creates its command bar. After this
command bar creation its .Protection will be set in msoBarNoCustomize +
msoBarNoVerticalDock + msoBarNoChangeDock - perfectly, in CommandBar
menu->Add or remove buttons this command bar name is grayed and we can't to
turn on/off button visibility on it. But we can change buttons order by
dragging them, can assign pictures to any button on this command bar, can
even remove button from command bar by dragging it out etc. - all of these
actions we'd like to prohibit.
This can be done - at the same Outlook version XTNDConnect and Nod32 are
installed, and all context menu items for this buttons are disabled.
Difference of these buttons from ours - they have .ID==32768 and
..FaceID=32768, but i can't to set this properties from add-in code, and i'm
afraid that this is indirect consequence of smth other mechanism of customize
prohibition.
Did you met similar problem?