Kbase 16517: Difference Between Disabled Native and Non-Native Fill-ins
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
28/10/2008 |
|
Status: Verified
GOAL:
Difference between disabled Native 4GL fill-ins and non-Native fill-ins.
FACT(s) (Environment):
Progress 8.x
Progress 9.x
FIX:
When a Native fill-in is disabled, the border remains, the text of the fill-in is grayed-out, and the background of the fill-in is grayed-out.
Other widgets (such as the editor, radio-set and toggle box widgets) also behave this way. (Refer to Progress Solution 13767, "Data Disappears from Native Fill-in Widgets When Disabled".)
When a non-native fill-in is disabled, the fill-in border disappears and the text remains the same color. Non-native fill-in's behave this way so that they work as expected in down frames with the CHOOSE statement and UPDATE TEXT.
Consider the following code samples:
/* example 1 - non-native */
REPEAT:
UPDATE a AS CHARACTER.
END.
/* example 2 - native */
REPEAT:
UPDATE a AS CHARACTER VIEW-AS FILL-IN NATIVE.
END.
Example 1 appears as a down frame because you update the variable. Example 2 keeps the borders around each field and does not look like a down frame.
You can get non-native fill-in's with the Progress 3D effect to keep their borders when they are disabled by setting Keep3DFillinBorder to true in the [Startup] section of the Progress.ini file. The text still is not grayed-out however:
/* non-native fill-in with 3D */
REPEAT:
UPDATE a AS CHARACTER WITH THREE-D.
END.