*If* it is a valid handle ... that is the point. If you do the test and come out with "None", then you have a positive indication that the test worked properly and you have a clear answer. If you get a ?, then you have to determine whether or not that is a valid result. This is not a position I take specific to this test, but a general principle that it is better to get a clear, definitive response indicating state. ? should mean, state is unknown. In this case, the state is clearly defined and entirely different from GUI or TTY.
Consulting in Model-Based Development, Transformation, and Object-Oriented Best Practice http://www.cintegrity.com
After looking at the other properties of the RCODE-INFO (or FILE-INFO) handle, I'd rather use the empty string for display type agnostic.
The unknown valud typically indicates the I passed a wrong value to the FILE-NAME at the first place.
"PORTABLE" would be my choice
If you don't have a valid handle, calling the property on it will fail.
Like an UI for portable devices?
I'd rather use a clearer term...
RCODE-INFO handle invalid?
Call me naive - but it's still an 4GL where a static system widget is always accessible.
I appreciate you calling yourself naïve rather than me wrong (which is, of course, more accurate).
Since the RCODE-INFO handle is a system handle and so always valid, Thomas's approach is the correct one. ? is returned when the RCODE-INFO handle doesn't actually point at any rcode.
"NONE" might be more accurate since it refers to no UI-specific code.
Would there be value in separating ABL GUI from .NET GUI in the response?
Since both GUI's use the same runtime and both GUI's could be used in the same R-Code.
Isn't the point that this piece of R-code has no UI rather than that it can be used in either?
None or NoUI seems more to the point.
Sr. Development Manager
Thank you Evan!