New Environment Variables
Several environment variables are added to this release of OpenROAD—three for general use, and three for memory management. For more information, see
Environment Variables in the
Workbench User Guide.
General Environment Variables
The following general environment variables are added:
• II_W4GL_DETAILS_ON_MOUSEWHEELCLICK
• II_W4GL_DISABLE_WINDOWS_GHOSTING
• II_W4GL_DPI_AWARENESS
II_W4GL_DETAILS_ON_MOUSEWHEELCLICK
Specifies whether to activate the On Details and On ChildDetails events by clicking the mouse wheel.
II_W4GL_DISABLE_WINDOWS_GHOSTING
Specifies whether the Windows ghosting feature for OpenROAD applications will be disabled (if set to TRUE).
“Windows ghosting” means that the Windows OS will put a ghost window in place of the application window when it considers an application as “not responding.” The ghost window looks like the application window with its title having a “(Not responding)” text appended.
For OpenROAD frames, the Windows ghosting could cause problems during processing of events, for example:
• Status bar is not updated
• Moving of ghost window of frame is possible, but OpenROAD application does not get the information of the new position
• Input buffering when using CurFrame.BlocksFrames=FALSE does not work
Default: FALSE
II_W4GL_DPI_AWARENESS
OpenROAD is DPI aware, which may make some fields smaller so the parent background becomes visible, resulting in the image of some fields with a bitmap background appearing more than once. To correct this, a new environment variable is added.
You may set this variable to these values:
DPI_UNAWARE (-1, the behavior before DPI awareness was implemented)
DPI_SYSTEM_AWARE (-2, the default)
DPI_PER_MONITOR_AWARE (-3)
DPI_PER_MONITOR_AWARE_V2 (-4)
DPI_UNAWARE_GDISCALED (-5)
Environment Variable for WebGen
The following environment variable is added:
II_W4GL_RS_ROUTES
Lets you set the path of a JSON-format file containing alternate routing information for applications running within an OpenROAD application server. It serves to convert existing applications using RemoteServer.Call4GL() statements with 'http' routing into JSON RPC requests using 'http-jsonrpc' routing. This eliminates any 4GL changes needing to be made.
Environment Variables for Memory Management
The OpenROAD memory management system is now configurable, and by default, issues fewer system memory calls, which can improve performance.
OpenROAD maintains a list of segments to store different type of buffers. When some memory is needed, OpenROAD checks its pool of segments for an available buffer. If none is available, then OpenROAD requests more memory from the operating system. When some memory is released, OpenROAD checks whether the buffer belonged to a segment that now contains only freed buffers. If this the case the, segment is returned to the OS.
These buffers and segments had static sizes that can be not big enough when running some applications on some system, hence the need to be able to modify these static values dynamically.
The following general environment variables are added:
• II_W4GL_SEGMENT_SIZES
• II_W4GL_SEGMENT_TOT_SIZE
• II_W4GL_TRACE_MEMORY
II_W4GL_SEGMENT_SIZES
Specifies a list of seven numbers, separated by commas, that define the size, in bytes, of the seven types of fixed buffers.
Default: 32, 128, 256, 512, 1024, 2048, 4096
II_W4GL_SEGMENT_TOT_SIZE
Specifies the size, in bytes, of buffer segments that OpenROAD allocates.
Default: 524160
II_W4GL_TRACE_MEMORY
Specifies whether to include the number of buffers OpenROAD has allocated and freed when printing output to the trace window. Analyzing the trace may help you decide which value to use:
TRUE
Specifies that the number of buffers should be written to the trace
FALSE
(Default) Specifies that the number of buffers not be written to the trace
Last modified date: 12/20/2023