FWD » Core Development » User Interface

Attributes

• MENU:TOGGLE-BOX
• EDITOR:LARGE
• COMBO-BOX:AUTO-COMPLETION

Methods

• BROWSE:CREATE-RESULT-LIST-ENTRY
• COMBO-BOX:EDIT-UNDO

Conversion issues for AUTO-COMPLETION attribute and EDIT-UNDO method are solved in 3750a rev 11298.

Are all the other attributes/methods already supported at conversion time?

Greg Shah wrote:

Are all the other attributes/methods already supported at conversion time?

Yes, I've checked them.

• TOGGLE-BOX is fully supported - fixed gaps in 11299.
• EDITOR:LARGE - this is just to mark that an EDITOR can display a LONGCHAR value - FWD can handle this automatically, nothing specific is required. I think the gaps should be changed to rt_full.

FWD can handle this automatically, nothing specific is required. I think the gaps should be changed to rt_full.

Please go ahead with this. Also: the runtime code should have comments to mention that no actual backing runtime is needed because the feature is implicitly supported in FWD.

3750a rev 11300 fixes EDITOR:LARGE attribute runtime (get/set support) and gaps.

I'll be working on BROWSE:CREATE-RESULT-LIST-ENTRY while AWS is not accessible.

FYI, we miss implementation of QUERY:CREATE-RESULT-LIST-ENTRY, so it should be implemented for all types of queries in order to implement BROWSE:CREATE-RESULT-LIST-ENTRY.

Stanislav Lomany wrote:

FYI, we miss implementation of QUERY:CREATE-RESULT-LIST-ENTRY, so it should be implemented for all types of queries in order to implement BROWSE:CREATE-RESULT-LIST-ENTRY.

Agreed. These must be implemented at the same time.

I've been wondering if the core of the implementation is the idea that the query is closed and reopened such that there is a new result list.

I've been wondering if the core of the implementation is the idea that the query is closed and reopened such that there is a new result list.

Unfortunately it's not the case. The new entry contains ids of the current records contained in the query's backing buffers. It can be arbitrary records not matching the original query sorting. "No record" is also a valid entry.

Note that I'm not going to implement CREATE-RESULT-LIST-ENTRY for non-scrolling queries because it seems to be inpractical: what is the sense of adding an entry if you cannot get back to it? I guess that underlying implementations for scrolling and non-scrolling queries are similar in 4GL, while in FWD it may be completely different, so that will save a lot of time.

The work for CREATE-RESULT-LIST-ENTRY() is being moved to #3940, which will be worked in the main project.

Are there any runtime features in this task which were not finished?

Greg Shah wrote:

Are there any runtime features in this task which were not finished?

Does anyone know this answer?

Greg Shah wrote:

Are there any runtime features in this task which were not finished?

All runtime for MENU:TOGGLE-BOX and EDITOR:LARGE is there. COMBO-BOX:AUTO-COMPLETION and COMBO-BOX:EDIT-UNDO is not completed.

COMBO-BOX:AUTO-COMPLETION and COMBO-BOX:EDIT-UNDO is not completed.

Eugenie: Please add these to your work in #3811.