Generic names that consist of the Listener interface and the method name of the event are used for all other events: An event registered as XListener::method is exported as
SDEvent-XListener-method = "/* event-code */"
Note that the XListener- and method components of this option are case sensitive.
The HTML filter now uses precisely these listener interfaces and method names so that it can import and export events as desired. You can register a focus event through
<INPUT TYPE=text ONFOCUS="/* code */"
Cut Through Black
<INPUT TYPE=text SDEvent-XFocusListener-focusGained="/* code */"
register. Events can therefore be registered as desired, including those not offered in the list boxes. To define the script language of events, you can write the following line in the document header:
<META HTTP-EQUIV="content-script-type" CONTENT="...">
During exporting, the default script language will be defined based on the first module found in macro management. For events, only one language can be used per document.