xInactivity Class gives Clarion applications a structured way to respond when users become inactive or resume activity.
An application can define multiple events instead of relying on one fixed idle timeout, and those events can be added, removed, or changed while the program is running.
Flexible event handling
Activity and inactivity events can trigger whatever application behavior is appropriate: warnings, locking, cleanup, navigation, automatic actions, or other program logic.
Key features
- Multiple activity/inactivity events
- Activity events
- Inactivity events
- Add events at runtime
- Remove events at runtime
- Change event behavior at runtime
- Execute application-defined logic for each event
- ABC template chain