Difference between revisions of "Screensaver"
| (6 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
The user interface supports a screensaver mode that can be activated automatically after a preset amount of time of user inactivity. | The user interface supports a screensaver mode that can be activated automatically after a preset amount of time of user inactivity. | ||
| − | When the screensaver is activated, the display is | + | When the screensaver is activated, the display is greyed out with a partially opaque mask, and a user event is sent to the HSYCO Server, triggering the USER event in events and the userCommand() callback in JavaScript and Java. The name parameter is set to the project's name, and the param parameter to "screensaver". |
When the screensaver is active, a click or touch will de-activate the screensaver, returning to normal operations. A USER event and userCommand() callback will be triggered, with the name parameter set to the project's name, and the param parameter to "screensaver/close". | When the screensaver is active, a click or touch will de-activate the screensaver, returning to normal operations. A USER event and userCommand() callback will be triggered, with the name parameter set to the project's name, and the param parameter to "screensaver/close". | ||
| − | To enable the screensaver, you can either add the screensaver=N option to the | + | To enable the screensaver, you can either add the screensaver=N option to the '''[[URL_Keywords| URL's query string]]''', where N is the number of seconds of inactivity, or dynamically with the UISET command, setting the screensaver '''[[Project#Project_attributes| project's attribute]]''' to N, or 0 to disable the screensaver. |
Latest revision as of 17:01, 27 September 2017
The user interface supports a screensaver mode that can be activated automatically after a preset amount of time of user inactivity.
When the screensaver is activated, the display is greyed out with a partially opaque mask, and a user event is sent to the HSYCO Server, triggering the USER event in events and the userCommand() callback in JavaScript and Java. The name parameter is set to the project's name, and the param parameter to "screensaver".
When the screensaver is active, a click or touch will de-activate the screensaver, returning to normal operations. A USER event and userCommand() callback will be triggered, with the name parameter set to the project's name, and the param parameter to "screensaver/close".
To enable the screensaver, you can either add the screensaver=N option to the URL's query string, where N is the number of seconds of inactivity, or dynamically with the UISET command, setting the screensaver project's attribute to N, or 0 to disable the screensaver.
