Frame Modes
OpenROAD provides the following frame modes:
FM_UPDATE
Specifies that default biases for entry fields allow reading and updating. All other fields can be selected (clicked). All menu items are enabled.
FM_QUERY
Specifies that default biases for entry fields allow reading and updating. All other fields can be selected (clicked). All menu items are enabled.
FM_READ
Specifies that default biases for entry fields allow reading but not updating. All other fields can be selected (clicked). All menu items are enabled.
FM_USER1
Specifies a name that lets you create your own mode (default biases allow reading and updating)
FM_USER2
Specifies a name that lets you create your own mode (default biases allow reading and updating)
FM_USER3
Specifies a name that lets you create your own mode (default biases allow reading and updating)
Although OpenROAD provides a set of default biases for each of the modes, the most useful modes are the default Update and Read modes. Switching between Update and Read modes is effective when you want to change a frame from an interactive to a passive state. For example, the video_detail frame script sets the frame mode to Read to provide a view-only version of the video details.
Because the Query, User1, User2, and User3 modes have the same defaults as Update mode, these modes are useful only when you want to create your own customized mode by explicitly setting the biases of the individual fields and menu items in that mode. You can do this from OpenROAD Workbench using the Frame Editor's Bias menu or from your 4GL code with the mode-bias attributes.
When you create a frame with Workbench, OpenROAD uses Update mode as the default mode. You can change this initial frame mode on the frame's Property Inspector. To change the frame mode at runtime, use the CurMode attribute of the frame's FrameExec object.