GUI ScreenIO for Windows |
This would be a good time to review the GUI ScreenIO programming rules.
You (and your users) can verify the installed version of the GUI ScreenIO runtime in use by the key combination Ctrl+Alt+Shift+V. This will display the version that you're running, like this:
It's not uncommon to mistakenly install more than one version of the runtime on a system; this can lead to confusion when features in the latest version aren't appearing when your application is being run.
You may note that this also displays the name and type of the panel that is being displayed. This could be useful to you when you're debugging your own applications.
Problems generally fall into one of these categories:
These tend to be one-time issues with setting up your compiler, figuring how to LINK your application, and related issues. Once you get everything set up properly, you won't encounter them again.
The Getting Started Problems page covers these topics.
Programming error of one kind or another; but the common ones are:
Programming, installation, or LINKing error. The usual suspects are:
We have not seen a memory leak or memory violation caused by GUI ScreenIO for several years.
Your program can cause memory leaks, though, if you fail to close your main panel before you STOP RUN. You need to close your main in order for GUI ScreenIO to release the memory and other objects that it allocated in order to run your application.
You can cause memory violations in your application in a number of ways; the most common ones are:
The best way to track down these errors is by using your interactive debugger.
Most of these are covered in the section dealing with individual controls:
© 2000-2019 Norcom, all rights reserved |