D
Dale Fye
Ref the thread labeled "Custom commandbar (1 works, 1 doesn't)" has a
discussion of a problem I have encountered with a custom commandbar.
I've created my own File menu options, one of which is Print, which has
additional options under it. When I try to enable/disable controls on the
Print sub-menu the statement:
Application.CommandBars.FindControl(Tag:="ControlTag").Enabled = True
Has no effect on the button.
Additionally, when I try to use the msoButtonUp and msoButtonDown values to
change the state of a button control on that Print sub-menu, it changes the
state, but the new state value is not reflected by addition or removal of the
checkbox preceeding the button.
Both of the techniques mentioned above work properly on 1st level menus
(msoBarPopup), but not on second level menus (msoControlPopup). Is this a
design feature, or a bug?
Dale
discussion of a problem I have encountered with a custom commandbar.
I've created my own File menu options, one of which is Print, which has
additional options under it. When I try to enable/disable controls on the
Print sub-menu the statement:
Application.CommandBars.FindControl(Tag:="ControlTag").Enabled = True
Has no effect on the button.
Additionally, when I try to use the msoButtonUp and msoButtonDown values to
change the state of a button control on that Print sub-menu, it changes the
state, but the new state value is not reflected by addition or removal of the
checkbox preceeding the button.
Both of the techniques mentioned above work properly on 1st level menus
(msoBarPopup), but not on second level menus (msoControlPopup). Is this a
design feature, or a bug?
Dale