since we have the new HTML widget and for those writing XML files straight from uniface code, there is a natural conflict between the precompiler constants and the tags wjhich should end up in the string.

One option would be to disable constant replacements for a given area
#noprecompilerconstants
…… your code here
#endnoprecompilerconstants

another one would be a new character which will be replaced at the very end of the precompilin process. just like the \\\”french quotation\\\” marks or enhancements of the GOLD set

or do not convert precompiler constants in blockdata (where normal uniface processing like \\\”%%myfield%%%\\\” conversions are disabled

For a lot of navigations in the IDF there is no keyboard alternative.

An an example take the proc code editors: I have not found a way to select a trigger without the mouse.

And because the code editor \\\\\\\\\\\\\\\”eats\\\\\\\\\\\\\\\” the TAB, there is no way to activate another widget by keyboard (just to select another item of the tree).

Perhaps a menu option (not pop-up) to select triggers (by name=triggerabbr, not by changing position) would be helpful.

relationship constraints should be checkend and processes regardles if the related entity is painted in a specific form or not.

as in unifields, $curline and $curword needs to be supported for all other kinds of (C/S) widgets

\\\”provide a correct handling of uniface-internal handles ($occhandle, $entityhandle, …) in associated lists. Requires an \\\”\\\”internal format\\\”\\\” for these handles.\\\”