Mojo.Event

Generated before a scene is displayed. Allows widgets or scenes to delay the scene transition if needed.

Supported Widgets

• None.

An activate event is generated when a scene is loaded.

Supported Widgets

• None.

This event is sent through the active commander chain when a back gesture is recognized (or the back key is pressed on the desktop).

It's currently generated by the stage assistant, which also responds to it in handleCommand(). If no other clients handle the event, then the stage assistant will do so by closing the current dialog or popping the current scene.

Custom Event Fields

• originalEvent: The original click Event object which caused this event to be dispatched. Useful for disambiguating changes if the list items contain multiple input fields.

Supported Widgets

• None.

A command event is generated when a menu item is selected.

Supported Widgets

• None.

Menuitems that specify checkEnabled:true in the menu model cause the menu system to check their enable state before displaying them. This is useful for items in submenus and the appmenu, because they are not constantly displayed (like items in the command & view menus), meaning their enable state always appears correct when the menu is popped up.
The command-enabled event is generated as part of menu updating.
To check the enable state of a menuitem, a command-enable event is sent through the commander chain. This event does not go through the DOM.
If nothing in the commander chain calls preventDefault() on the event, the menuitem will be enabled.

Supported Widgets

• None.

An up action following a Mojo.Event.dragStart event generates a dragEnd event.

Supported Widgets

• None.

Movement following the Mojo.Event.dragStart event generates dragging events.

Supported Widgets

• None.

A down action followed by movement outsided of a system-defined radius generates a Mojo.Event.dragStart event. Usually, the Mojo.Event.dragStart event is handled by the scroller. However, any element that chooses to handle this event gets all subsequent drag events.

Supported Widgets

• None.

Entering data in the filterbox generates a filter event after a client of default specified delay.

Supported Widgets

• Mojo.Widget.FilterField

Entering data in the filterbox generates a filter event as soon as a key is typed.

Supported Widgets

• Mojo.Widget.FilterField

Movement greater than a system-defined rate, between down and up events, generates a flick event.

Supported Widgets

• None.

This event is sent through the active commander chain when a forward gesture is recognized

Supported Widgets

• None.

A down movement lasting greater than a system-defined time interval and with movement within a limited radius generates a hold event. The hold event is associated with the Mojo.Event.hold event.

Supported Widgets

• None.

An up movement following a hold event generates a Mojo.Event.holdEnd event.

Supported Widgets

• None.

imageViewChanged sent from an ImageView widget when the current center image has been changed via a gesture.

Supported Widgets

• Mojo.Widget.ImageView

Forwarded keydown event. Only supported on the currently active sceneElement or container.

Custom Event Fields

• originalEvent: keyboard event that triggered this event.

Supported Widgets

• None.

Forwarded keydown event. Only supported on the currently active sceneElement or container.

Custom Event Fields

• originalEvent: keyboard event that triggered this event.

Supported Widgets

• None.

Forwarded keyup event. Only supported on the currently active sceneElement or container.

Custom Event Fields

• originalEvent: keyboard event that triggered this event.

Supported Widgets

• None.

This event is dispatched to the widget element when there the special "Add" item at the end of the list is clicked. This item appears when the addItemLabel property is defined in the widget's attributes or model, and a custom event name is used to give applications an easy way to identify the expected behavior.

Custom Event Fields

• model: The model object used to render the List to which an item should be added.
• originalEvent: The original click Event object which caused this event to be dispatched. Useful for disambiguating changes if the list items contain multiple input fields.
• item: The item model to be added. Only defined for listAdd events resulting from a drag/drop from a different list.
• index: The index at which to add the new item. Only defined for listAdd events resulting from a drag/drop from a different list.

Supported Widgets

• Mojo.Widget.List

This event is dispatched to the widget element when a list item is clicked. As with Mojo.Event.listTap, the app handler is responsible for sorting out which part of the list item changed if there are multiple options, and event.originalEvent.target should be the input element which changed.

Custom Event Fields

• object: The object from the listItems array in the model associated with the changed list item.
• model: The model object used to render the List.
• originalEvent: The original change Event object which caused this event to be dispatched. Useful for disambiguating changes if the list items contain multiple input fields.

Supported Widgets

• Mojo.Widget.List

This event is dispatched to the widget element when an item is deleted from the list. SceneAssistants will often listen for this event on List widgets, and should respond by deleting the given item from the model (and database, if any). If preventDefault() is called on the listDelete event, then the default deletion behavior in the list widget will not occur.

Custom Event Fields

• model: The widget's model object.
• item: The model object for the list item being deleted.
• index: The index of the list item being deleted.

Supported Widgets

• Mojo.Widget.List

This event is dispatched to the widget element when an item is reordered. SceneAssistants will often listen for this event on List widgets, and should respond by reordering the given item model as indicated (and persist the changes to disk if appropriate).

Custom Event Fields

• model: The widget's model object.
• item: The model object for the list item being moved.
• fromIndex: The current index of the list item, which it should be moved from.
• toIndex: The new index of the list item, which it should be moved to.

Supported Widgets

• Mojo.Widget.List

This event is dispatched to the widget element when there is a mojo-tap event on a list item. The app handler is responsible for sorting out which part of the list item was clicked if necessary, since that depends entirely on the template provided. It's useful to look at event.originalEvent.target. This is the target of the original click or change event that caused the higher level mojo event to be dispatched. It will be an input element containing the new value for a change event, or the item's sub-element that was actually clicked for a click event. For example:

    listClickHandler: function(event) {
          // Only respond to clicks on the label element, not the editable text field.
          if(event.originalEvent.target.tagName == "LABEL")
            Mojo.Log.info(event.object.data +": "+event.object.definition);
        }

Custom Event Fields

• item: The object from the listItems array in the model associated with the clicked list item.
• model: The model object used to render the List.
• originalEvent: The original click Event object which caused this event to be dispatched. Useful for disambiguating clicks if the list items contain multiple clickable elements.

Supported Widgets

• Mojo.Widget.List

Sent by the scene controller on the scene element when the screen orientation changes. Contains an orientation property describing the orientation.

Sent when progress reaches 100%.

Supported Widgets

• Mojo.Widget.ProgressPill
• Mojo.Widget.ProgressBar

Sent when the icon on the ProgressPill is tapped by the user.

Custom Event Fields - model: model associated with this progress pill.

Supported Widgets

• Mojo.Widget.ProgressPill
• Mojo.Widget.ProgressBar

This event is dispatched to the widget element when property-editing widgets change values.

Custom Event Fields

• property: Name of the property that changed.
• value: New value of the property.
• model: The model object to which the property change applies. Sometimes available:
• oldValue: value of the widget before this change.
• originalEvent: event that triggered the propertyChange event to be sent.

Supported Widgets

• Mojo.Widget.ListSelector
• Mojo.Widget.PasswordField
• Mojo.Widget.RadioButton
• Mojo.Widget.Scroller
• Mojo.Widget.Slider
• Mojo.Widget.TextField
• Mojo.Widget.ToggleButton

When contained in a scroller, down action followed by movement generates a scroll-starting event.

Supported Widgets

• Mojo.Widget.Scroller

A native down-and-up movement within a limited time interval and within a limited radius generates a single tap event.

It's sent when Mojo.handleSingleTap is called and has the following properties: x, y, shiftKey, ctrlKey, altKey, metaKey, timestamp.

Supported Widgets

• None.

Sent when the draggable element on the Slider is dropped.

Supported Widgets

• Mojo.Widget.Slider
• Mojo.Widget.ProgressSlider

Sent when the draggable element on the Slider is picked up to be dragged.

Supported Widgets

• Mojo.Widget.Slider
• Mojo.Widget.ProgressSlider

A stageActivate event is generated when a stage becomes active and is potentially receiving the user's attention. For card stages, this is when the stage is maximized and fills the screen. The event is sent to the top scene, and bubbles up to the stage's document.

Supported Widgets

• None.

A stageDeactivate event is generated when a stage is no longer active and potentially receiving the user's attention. For card stages, this is when the stage is minimized.
The event is sent to the top scene, and bubbles up to the stage's document.

Supported Widgets

• None.

A down-and-up movement within a limited time interval and within a limited radius generates a tap event.

Supported Widgets

• None.

Sent in response to saving inline images.

Supported Widgets

• Mojo.Widget.WebView

A wrapper around addEventListener that adds some parameter checking.

This function can be used to listen for changes in the focused element inside the node.

A 'listener object' is returned which implements a stopListening() method. This can be called permanently cancel the listener, removing its event listeners.

This function can be used to listen for some kind of 'hold' event on a given node. This works by initiating a 'hold timer' when the appropriate 'down' event is received, and cancelling it if we see the 'up' event before it has expired. If the timer expires, then we call the given handler function with the initial 'down' event as the first argument.

A 'listener object' is returned which implements a stopListening() method. This can be called permanently cancel the listener, removing its event listeners. Alternatively, if the handler function returns true, then the listener will be automatically stopped.

The implementation is somewhat tailored for key events: * Successive 'down' events do not reset the hold timer. * After calling the handler once, it will not be called again until after an 'up' event is received.

Utility routine used to create custom mojo events.

In addition to creating an event with the given name, the event is also extended such that a isDefaultPrevented() method is available.

Like prototype's element.fire(), except that the event type is actually as specified (instead of always dataavailable), and the specified details are placed in the event object directly (instead of a memo subobject). If element is undefined, the new event will just be returned and not actually dispatched.

Function to create and send a key down and up event.

Function to create and send a key event.

A wrapper around removeEventListener that adds some parameter checking.