Applies To: |
|
Summary: |
When Citect Explorer is started, some or all of the windows no longer appear, although the application appears on the taskbar. This problem can also manifest itself as a window that is sized incorrectly so that only part of the window is visible on the desktop, and items such as the status bar at the bottom of the Graphics Builder are no longer visible. |
Solution: |
This will most often occur after a user
has changed the default screen resolution used on the computer to a
smaller size. The CitectSCADA Window sizes and positions are saved
each time CitectSCADA is closed, so that when CitectSCADA is
restarted, the windows appear in the same place, with the same size
windows. Unfortunately, if you shutdown CitectSCADA and then switch
to a lower screen resolution before restarting (or copy in a
Citect.INI file from a computer that uses a high resolution) it is
possible that CitectSCADA will place the three application windows
off the screen or and/or make them too big to fit on the desktop.
This can be resolved by clearing the saved window sizes and positions from the INI file and letting CitectSCADA create windows in new default positions. The following INI parameters should be commented out or deleted in order to restore the corresponding windows sizes/positions to the default values: (The values next to the parameters below are taken from the author's computer, and may not necessarily match those in your own INI file) Citect Explorer: [CTEXPLORE] Project Editor: [CTEDIT] Graphics Builder: [CTDRAW.windowplacement] Cicode Editor: [CtCicode] (You may not have all of these parameters under the CtCicode section in your INI file, if you haven't used these debug windows previously). Kernel: [Kernel] (There may be more or less of the Win(x) parameters under the Kernel section in your INI file, depending on how many kernel windows you had open when you last closed down Citect Runtime). The parameters can be commented out by simply placing an exclamation mark in front of the parameter (i.e.. "!"). For further information on what each parameter value means, please refer to KB article Q3766. |
Keywords: |
Related Links
Attachments