The Menu Commands Api - MACROMEDIA DREAMWEAVER 8-EXTENDING DREAMWEAVER Manual

If the user pressed the shortcut keys (F12 or Ctrl+F12) and no primary or secondary browser
has been specified, a dialog box appears to inform the user. If the user clicks OK, the function
calls the function
dw.showPreferencesDialog()
user specify a browser at that point.

The Menu Commands API

The custom functions in the Menu Commands API are not required.
canAcceptCommand()
Description
Determines whether the menu item is active or dimmed.
Arguments
{arg1}, {arg2},...{argN}}
If it is a dynamic menu item, the unique ID that the
specifies is the only argument. Otherwise, if the
tag, the value of that attribute passes to the
menuitem
(and to the
isCommandChecked()
functions) as one or more arguments. The
between two menu items that call the same menu command.
The arguments attribute is ignored for dynamic menu items.
Returns
Dreamweaver expects a Boolean value:
commandButtons()
Description
Defines the buttons that appear on the right side of the Options dialog box and their behavior
when they are clicked. If this function is not defined, no buttons appear, and the
of the Menu Commands file expands to fill the entire dialog box.
Arguments
None.
with the
getDynamicContents()
arguments
canAcceptCommand()
,
receiveArguments()
attribute is useful for distinguishing
arguments
if the item should be enabled;
true
argument to let the
browsers
attribute is defined for a
, and
setMenuText()
false
BODY
The Menu Commands API
function
function
otherwise.
section
209