MACROMEDIA DREAMWEAVER MX 2004-EXTENDING DREAMWEAVER Specifikace Strana 209

  • Stažení
  • Přidat do mých příruček
  • Tisk
  • Strana
    / 504
  • Tabulka s obsahem
  • KNIHY
  • Hodnocené. / 5. Na základě hodnocení zákazníků
Zobrazit stránku 208
The Menu Commands API 209
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() with the browsers argument to let the
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 getDynamicContents() function
specifies is the only argument. Otherwise, if the
arguments attribute is defined for a
menuitem tag, the value of that attribute passes to the canAcceptCommand() function
(and to the
isCommandChecked(), receiveArguments(), and setMenuText()
functions) as one or more arguments. The
arguments attribute is useful for distinguishing
between two menu items that call the same menu command.
Returns
Dreamweaver expects a Boolean value: true if the item should be enabled; false otherwise.
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
BODY section
of the Menu Commands file expands to fill the entire dialog box.
Arguments
None.
NOTE
The arguments attribute is ignored for dynamic menu items.
Zobrazit stránku 208
1 2 ... 204 205 206 207 208 209 210 211 212 213 214 ... 503 504

Komentáře k této Příručce

Žádné komentáře