Bug #4619
GUI fill-in widgets show in FWD, when 4GL shows nothing
0%
Related issues
History
#1 Updated by Roger Borrello about 4 years ago
- Related to Feature #4393: add TITLE-DCOLOR attribute support added
#2 Updated by Roger Borrello about 4 years ago
- File GUI_frame_title_color_default_values3.png added
A simple integer on a frame becomes a fill-in widget with the default value showing. In 4GL, this is not a fill-in and doesn't show anything by default.
Testcase: uast/frame_title_color_default_values.p
In the screen grab above, the frames behind the dialog box were fill-ins before focus was taken away.
#3 Updated by Greg Shah about 4 years ago
In 4GL, this is not a fill-in and
I think you mean that it is an editable fill-in in FWD and not in the 4GL?
We know that the widget being used is a fill-in. Whether it is editable or not is something that might be different between FWD and the 4GL.
In the screen capture, in the 4GL side you can see the outline of an editable fill-in in the dialog box and you can see an insertion cursor being drawn there too. It definitely seems editable in the 4GL.
doesn't show anything by default.
Well, I think this is actually the issue. The 4GL must be defaulting this to ? (unknown value) which does not display. FWD defaults to 0 which does display.
#4 Updated by Roger Borrello about 4 years ago
Would this be related to the variable factory itself, or the widgets? I had another testcase uast/io/basic_redirected_output.p which used message "Redirected?" set redir as logical. which ended up being pre-filled with "no" in FWD, and not pre-filled in 4GL.
#5 Updated by Greg Shah about 4 years ago
The message set case may not be related to this at all.