Ektron® eWebEditPro Developer's Reference Guide

}
JavaScript Objects
eWebEditPro.instances[sEditorName].editor.ExecCommand("cmdselstyle", ".highlight", 0);
Note that each array entry defines a handler for one command. If more than one
command uses the same function, set each array entry to the same function (for
example, setStyleSheet). The syntax is:
eWebEditProExecCommandHandlers[command_name] = your_handler_function
The handler must be a function with the same parameters as
eWebEditProExecCommand, namely,
function(sEditorName, strCmdName, strTextData, lData)
ExecCommandHandlersArray Parameters
Parameter Type Description
sEditorName String The name of the occurrence of eWebEditPro. To access the
eWebEditPro methods, use
eWebEditPro.instances[sEditorName].editor.
See Also: “Appendix A: Naming the eWebEditPro Editor” on
page 576
Note: If your Web server is running ASP.NET, use this syntax:
eWebEditPro.instances[sEditorName].editor
strCmdName String The name of the JavaScript command that was just executed (if a
standard command) or to be executed (if a custom command).
Standard commands begin with cmd; custom commands begin with
js.
An example of a JavaScript function that executes after a standard
command executes is checking spelling within all instances of the
editor on a page. If the user presses the spellcheck button in one
editor, he is prompted to continue to the next editor. If confirmed, the
command is sent to the next editor on the page and will loop back to
the first editor on the page.
strTextData String A string that may contain text data related to the command. Typically
not used.
lData Long A long integer value that may contain numeric data related to the
command. Typically not used.
Parameter Requirements for Commands
Most commands do not require parameters. For example, cmdbold bolds (or
unbolds) selected text, ignoring the strTextData and lData parameters.
Ektron® eWebEditPro Developer’s Reference Guide, Release 5.1, Revision 1 238