FWD » Core Development » User Interface

Looking at some issues with screen-value when the widget is using a custom format and the display statement is used I've stumbled on FrameElement/Element and thought my issue at hand would be solved if the Element will use the widget's format as default if not set. Problem is if format is being defined the value is an FormattedValue instance and none of the widgets there seems to be able to use such a 'beast' :(

A simple test (testcases/ui/screen_value/display_format.p) shows that the conversion is simply ignoring the format option used in display statement and generated code always use the Element ctor with only two parameters so the format is always ignored.

Is that only a draft or the use of FrameElement is not meant to solve this case? My issue come from GenericFrame's copyToScreenBuffer where the FormattedValue looks like it might come into play but actually this doesn't seem to be the case.

Question - do we need to handle the case when the value passed to setScreenValue might be FormatedValue (by looking at the code one might think so)?

Question - do we need to handle the case when the value passed to setScreenValue might be FormatedValue (by looking at the code one might think so)?

I don't think so. Please see my notes in #6038-55.