If you are interested, the framework that I use for all my App development (and many PB customers do as well) - it is free and open sourced under an Apache 2.0 licensing model since 1995 (and written in 1992 before the PFC). It also tracks how many times any given window is activated / deactivated, number of key stokes it receives, O/S messages and the state of the Window and its controls on disposition. The Window Manager service also keeps track of all MS-Window resources that the Open Window class consumes including memory and GDI resources for all of its controls. It is called when any window activity is performed and also handles the Close All Windows functionality. This service (which is completely transparent to any PB App) handles the tracking of opening and closing windows. I solved these challenges a few decades ago in my STD Framework by creating a Window Manager service. Another reason for closing window classes in the exact reverse order. Apps also need to handle Window closes in a nice logical way too for the CloseQuery events so that business end-of-transaction states are upheld. I found out a long ago that closing them in a random order can lead to App crashes. closing the windows in the exact reverse order that they were opened. Also, not all Apps are MDI and even if they are - there could also be both Child and Pop-up windows open to consider as well. This seems like an easy thing to do when you first think about it but it is actually a very complex issue behind the scenes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |