The CANTK window (uiwindow/uiscene) has a complete life cycle like the Android activity and other components, assuming my web app has two windows: Firstwindow,secondwindow, The entire app's life should look like this:
Created with Rapha?l 2.1.2 Firstwindow Firstwindow Secondwindow Secondwindow 1, Firstwindow ' s onsysteminit called 2, Secondwindow ' s onsysteminit called 3, Firstwindow ' s onLoad called 4, Secondwindow ' s onLoad called 5, Firstwindow ' s onbeforeopen called 6, Firstwindow ' s onOpen called Switch to Secondwindow 7, Secondwindow ' s onbeforeopen called 8, Firstwindow ' s onswitchtoback called 9, Secondwindow ' s onOpen called switch back to Firstwindow 10, Firstwindow ' s onswitchtofront called 11, Secondwindow ' s onClose called 12, Firstwindow ' s onClose called 13, Firstwindow ' s onUnload called 14, Secondwindow ' s onUnload called
Connection for process-related events:
- Onsysteminit
- OnLoad
- Onbeforeopen
- OnOpen
- Onswitchtoback
- Onswitchtofront
- OnClose
- OnUnload
Online demo of life cycle:
Gamebuilder Development Game Application Series of CANTK window life cycle