Denotes a component is created when rendering a ZUML page. Refer to the Component Lifecycle chapter.
Denotes the close button is pressed by a user, and the component shall detach itself.
Denotes another component is dropped to the component that receives this event. Refer to the Drag and Drop section.
Denotes the state of a component has been changed by the user.
Denotes a component has been moved by the user.
Denotes a component has been resized by the user.
Denotes the z-index of a component has been changed by the user.
Denotes the timer you specified has triggered an event. To know which timer, invoke the
Denotes a application-dependent event. Its meaning depends on applications. Currently, no component will send this event.
Notifies a root component about the client's information, such as time zone and resolutions.
Notifies a root component that the client has sent a request to the server. It is usually used to piggyback non-emergent UI updates to the client.
Notifies that the user pressed BACK, FORWARD or others that causes the bookmark changed.
|onColSize||columns listhead treecols||Event: ColSizeEvent
Notifies the parent of a group of headers that the widths of its children are changed by the user.
Notifies one of the pages of a multi-page component is selected by the user.
Notifies that file(s) is uploaded, and the application can retrieve the uploaded files(s) by use of the
Notifies that the fulfill condition has been applied to the target component. It is posted after all descendant components have been created.
Echo event allows you to provide more richer message before doing long operation.
<window id="w" width="200px" title="Test echoEvent" border="normal"> <attribute name="onLater"> Thread.sleep(5000); Clients.showBusy(null, false); new Label("Done.").setParent(w); </attribute> <button label="Echo Event"> <attribute name="onClick"> Clients.showBusy("Execute... (about 5 sec.)", true); Events.echoEvent("onLater", w, null); </attribute> </button> </window>
For more information, please refer to this small talk.
The Event Flow of radio and radiogroup
For developer's convenience, the
onCheck event is sent to
raido first and then to
radiogroup. Thus, you could add listener either to the radio group or to each radio button.
<radiogroup onCheck="fruit.value = self.selectedItem.label"> <radio label="Apple"/> <radio label="Orange"/> </radiogroup>
You have selected :
The above sample has the same effect as follows.
<radiogroup> <radio label="Apple" onCheck="fruit.value = self.label"/> <radio label="Orange" onCheck="fruit.value = self.label"/> </radiogroup>
You have selected :
- The internal implementation is done by adding a listener when a
radiois added to a