skip to main content

Integrated Development Environment (IDE) : Working with Screen Programs and File Layouts : Drawing the Screen

Drawing the Screen
To draw a control on the screen:
1.
2.
3.
4.
By drawing the control you automatically set LINE, COL, LINES and SIZE properties. All other properties are set to a default value that can be configured by clicking on the Window menu, choosing Preferences and then selecting isCOBOL / Screen Designer / Default from the tree.
The control is automatically named with the following pattern: <screen_name>-<two-digits-control-type>-<progressive-number>. For example, when you draw the first entry-field on screen-1, it will be named "screen-1-ef-1". If you wish to assign a different prefix than the screen name to the control name, you can right click on the Screen Designer area and choose "Change Screen Prefix". When you change the prefix, all existing controls in the screen are automatically renamed, unless you check the option "Change screen’s prefix only", in this case only the new controls will use the new prefix. You can always rename a single control by editing its "(name)" property.
To change the property values for one or more controls drawn on the screen:
1.
o
o
2.
Change the properties values in the Properties view. The full documentation of graphical control properties can be found at the Graphical User Interface Reference section of the isCOBOL Documentation.
Note: When you set the font property of a control to a native font (e.g. large-font) the IDE shows a preview of the control depending on the iscobol.font setting (e.g. iscobol.font.large) found in the configuration. Therefore, in order to obtain a preview that is consistent with the run time, ensure that the same font settings are used both for the IDE configuration and the Framework configuration. Changing these settings after the Screen Program has been created doesn’t produce any effect since these settings are read only when the program is created.
To easily change LINE, COL, LINES and SIZE
1.
2.
o
o
o

Copyright (c) 2017 Veryant
Contact us
Please share your comments on this manual or on any
Veryant product documentation with the email button at the top left