The Deferred Section is used to allow lazy loading, which can contribute to efficiency in a Coaches operation since images outside of viewport are not loaded until the user scrolls to them.
Like almost all SPARK controls, you can trigger events that are fired when the user interacts with the control (see the Event and Methods sections below and the Event Handling article for more information).
This section is most commonly used when wanting to improve the efficiency of Coaches.
Configuration
Lazy-load automatically When selected; specifies that the control should be lazy-loaded
Delay for auto-loading Specified in milliseconds (e.g. 1000 for 1 second)
Example
These are the configuration option settings...
The image will load after 5 seconds...
Event
With the Deferred Section, there is 1 type of event handler:
- On lazy-loaded event When there is lazy loading
You can use JavaScript logic to affect the effects of the control, depending on the event. More information on using these controls can be found in the Event Handling article.
Methods
For detailed information on the available methods for this control, access the JS Doc file.
Best Practices
Best to use when you have a fairly heavy/intensive section, and need to delay the loading of said section. Useful to defer logic until after a section is done loading (through the on lazy-loaded event).
Known Issues
If you have a Deferred Section inside a coach view there are potential addressing issues. To avoid these issues you should add a load Event Handler containing the following code:
- bpmext.ui.loadView(this)
- add an unload Event Handler containing
- bpmext.ui.unloadView(this)
- This will workaround the addressing issue.
- Author: Courtney Silva
- Date Created: June 29, 2015
- Date Modified: December 9, 2015
Comments