The app provide to us several events to be used. We can use this events (like any other app view event, app dialog event or app control event) to perform any task that we need. Below are referred all the available and ready to be use app events.
The app Mounted event is the first one which is fired then the app start. Only the "app" variable is available inside this event, of course with their app properties, app methods and the available app user functions. See also the available events variables.
The app DomReady event is fired when the main first app view DOM (Document Object Model) is ready to be used. For example, you can change the Text property of a Push button control in a secure way, that is, because the Push button control HTML markup is ready to be use and modified. See also the available events variables.
The app DeviceReady event is only fired if our app has been compiled with Apache Cordova, that is, is intended to run in platforms like Android, Apple iOS or Microsoft Windows. When the app DeviceReady event is fired we can access to the Apache Cordova stuff, as well the Apache Cordova plugins that we want to use. In fact, it's mandatory to wait for the app DeviceReady event in order to access to the referred stuff in a secure way, in other words, we can't access to the Apache Cordova stuff from the app Mounted event, just because that stuff has not been properly initialized yet. See also the available events variables.
The app SidebarItemClick event is fired when the user click on an item or subitem of the optional app sidebar. Here in this event you have at your disposition the Sidebar.Item, Sidebar.Item.Index and the Sidebar.Item.Subindex app properties.
The app SidebarHeaderClick event is fired when the user click on the header of the optional app sidebar. Take a look at the app sidebar options for more information.
The app JavascriptError event is fired when a JavaScript error occurs. If so, in this event the app Error property is filled with the below properties:
| Name | Type | Description |
|---|---|---|
| app.error.message | String | An error message that must describe the JavaScript error. |
| app.error.url | String | The URL of the script that causes the JavaScript error. |
| app.error.lineNumber | String | The line number of the script that causes the JavaScript error. |
The app VueJsError event is fired in case of VueJS uncaught errors during component render function and watchers. You know that one of the used libraries in DecSoft App Builder apps is the VueJS library. Here in this event you have at your disposition the app Error property with the below properties:
| Name | Type | Description |
|---|---|---|
| app.error.message | String | An error message that must describe the VueJS error. |
| app.error.vm | Object | The VueJS component instance wich causes the error. |
| app.error.info | String | Additional information about the VueJS error. |
The app Pause event is only fired if our app has been compiled with Apache Cordova, that is, is intended to run in platforms like Android, Apple iOS or Microsoft Windows. This event is fired when the app become to the platform "background mode" from the platform "foreground mode". In other words, this event is fired when the app user go to another possible device app or anyway put our app in the background.
We are talking here about the platforms app cycle. Once an app is launched by the user, that app become the foreground app. When the user go to another app or just put the foreground app into the background, the operating system is responsible to maintain this app running or to gracefully close it, to save precious device resources.
The app Pause event is the right place to, for example, save certain app states, for example in the app local storage, in order to recover that saved app state when the app starts again or when the app Resume event is fired. See also the available events variables.
The app Resume event is only fired if our app has been compiled with Apache Cordova, that is, is intended to run in platforms like Android, Apple iOS or Microsoft Windows. This event is fired when the app become to the platform "foreground mode" from the platform "background mode". In other words, this event is fired when the app user back to your app (which has been started before) from another possible device app or anyway put our app in the foreground.
Before the app Resume event is fired, the app Pause event has been already fired in the past. The app Resume event is the right place, for example, to recover a previously saved app state, when the Pause event was fired. See also the available events variables.
The app Resize event is fired when the screen has been resized, for example, because the user resizes the browser window. See also the available events variables.
The app Online event is fired when the app goes online, and the device becomes connected to the Internet. This app event requires the Apache Cordova Network information plugin was included in the app. See also the available events variables.
The app Offline event is fired when the app goes offline, and the device is not connected to the Internet. This app event requires the Apache Cordova Network information plugin was included in the app. See also the available events variables.
The app ViewChange event is fired when the app are going to change to another app view, because the user navigates to another app view URL, or because you go to another app view by using the showView() method, for example.
It's possible to prevent the app view change if you return "false" in this app event. You can know the app view that is going to be show by using the app.event.nextViewName property, and, you can know the app view which is going to be leaved by using the app.event.prevViewName property.
The app OrientationChange event is fired when the screen orientation changes. This app event requires the Apache Screen Orientation plugin was included in the app. See also the available events variables.
The app BackButton event is fired when the user presses the device's back button (Android and Windows only). See also the available events variables.
The app BatteryStatus event is fired when the battery charge percentage changes by at least 1 percent, or when the device is plugged in or unplugged. This event requires the Apache Cordova Battery Status to be included in the app. Inside this event you can use the referred plugin app.cordova.battery.level and app.cordova.battery.isPlugged variables.
The app BatteryLow event is fired when the battery charge percentage reaches the low charge threshold. This threshold value is device-specific. This event requires the Apache Cordova Battery Status to be included in the app. Inside this event you can use the referred plugin app.cordova.battery.level and app.cordova.battery.isPlugged variables.
The app BatteryCritical event is fired when the battery charge percentage reaches the critical charge threshold. This threshold value is device-specific. This event requires the Apache Cordova Battery Status to be included in the app. Inside this event you can use the referred plugin app.cordova.battery.level and app.cordova.battery.isPlugged variables.
The app VolumeUpButton event is fired when the user press the device's volume up button (Android only). See also the available events variables.
The app VolumeDownButton event is fired when the user press the device's volume down button (Android only). See also the available events variables.
The WebExtContent app event is fired only if the app is deployed as a Web Extension and after you call to the app webExtensionSendMessage() method. Take a look too at the app WebExtMessage event. This method provides the below variables, which can be accessed "as is", without any prefix.
| Name | Type | Description |
|---|---|---|
| message | Mixed | This is the message that you send using the app webExtensionSendMessage() method. |
The WebExtMessage app event is fired only if the app is deployed as a Web Extension and after you call to the "window.chrome.runtime.sendMessage(message)" JavaScript method. It's a way to communicate the Web Extension Content script (which run in the context of the current browser's page) with our app. Take a look too at the app WebExtContent event.
This event put at your disposition the below variables, which can be accessed "as is", without any prefix:
| Name | Type | Description |
|---|---|---|
| message | Mixed | This is the message that you send using the "window.chrome.runtime.sendMessage(message)" JavaScript method. |
The app KeyUp event is fired when the user release up a key in the keyboard while the app has the focus. You can find information about what key has been pressed, for example, using the Event variable which is available also in this control event. See also the available events variables.
The app KeyDown event is fired when the user press a key while the app has the focus. You can find information about what key has been pressed, for example, using the Event variable which is available also in this control event. See also the available events variables.
The Click event handler is fired when the user click or tap into the app. See also the available events variables.
The DblClick (Double Click) event handler is fired when the user double click or double tap into the app. See also the available events variables.
The SwipeUp event handler is fired when the user made the swipe up gesture with the mouse (browsers) or with the finger (devices). See also the available events variables.
The SwipeRight event handler is fired when the user made the swipe right gesture with the mouse (browsers) or with the finger (devices). See also the available events variables.
The SwipeDown event handler is fired when the user made the swipe down gesture with the mouse (browsers) or with the finger (devices). See also the available events variables.
The SwipeLeft event handler is fired when the user made the swipe left gesture with the mouse (browsers) or with the finger (devices). See also the available events variables.
The MouseUp event handler is fired when the user up the mouse into the app. See also the available events variables.
The MouseDown event handler is fired when the user down the mouse into the app. See also the available events variables.
The MouseMove event handler is fired when the user move the mouse into the app. See also the available events variables.
The ContextMenu event handler is fired when the browser must shown the context menu of the the app, which occur when the user click with the right mouse button into the app. See also the available events variables.
The below JavaScript variables are available in all the referred App events handlers:
| Name | Type | Description |
|---|---|---|
| event | Mixed | This variable is received in almost all app events. You can use this variable to stop the propagation of the event, to access the HTML element who fire the event and more. |
| self | Object | Stores the app object. This is a shortcut to the "app" variable, and it's available since we are talking about specific app events. |
| view | Object |
Stores the current app view or dialog. This variable allow us to access to that view or dialog properties and methods and also their controls properties and methods. For example, you can access to a control properties using the variable "view.yourControlName", suposing the control is named "yourControlName". |
| views | Object | Stores all the loaded app views. Note that loaded views mean that the app views has been previously show to the user. It's possible to access to the app view controls properties like "views.view1.yourControlName", suposing the view is named "view1" and the control is named "yourControlName". In the same way we can access to other controls of the view and to other loaded views and their controls. |
| frames | Object | Stores all the app frames. You can use this variable to access to all the app frames and their controls. |
| dialogs | Object | Stores all the app dialogs. You can use this variable to access to all the app dialogs and their controls. |
| app | Object | Stores all the app properties and methods. You can use this variable to access to all the app properties and app methods. |