FWD » Core Development » User Interface

Example

define frame f1 with side-labels.
message can-query(frame f1:handle, "side-label":U).
message frame f1:handle:side-label.

4GL:

yes
yes

FWD:

no
yes

Greg Shah wrote:

Let's just clear this now.

OK.

But what does SIDE-LABEL mean for frame widget? The same as SIDE-LABELS? I do not see the SIDE-LABEL attribute in OE Reference book.

Made some research and found the SIDE-LABEL is just an abbreviation for SIDE-LABELS. In 4GL it is possible to use any abbreviated keyword from SIDE-LAB to SIDE-LABELS. And for conversion we actually do this properly.

But at runtime the call can-query(frame f1:handle, "side-label":U) attempts to use exactly SIDE-LABEL. And it fails because our reflection usage has registered annotation for SIDE-LABELS only. Moreover we can have only one runtime annotation, for exactly full attribute name.

The solution is to convert abbreviated keyword on the fly to the full one. The fix is pretty simple(HandleOps.canQuery() method):

...
+import com.goldencode.p2j.uast.*;
...
   public static logical canQuery(final handle h, final String attributeOrMethodName)
   {
      if (h == null || h.isUnknown())
      {
         return logical.UNKNOWN;
      }

      final Object res = h.get();
      if (res == null)
      {
         return logical.FALSE;
      }

-      final String upcased = attributeOrMethodName.toUpperCase();
+      final String upcased = ProgressAst._keyword(attributeOrMethodName).toUpperCase();

      if (isHandleAttribute(upcased))
      {
         return logical.TRUE;
      }

      if (res instanceof HandleChain && invalidChainAttribute((HandleChain) res, upcased, true))
      {
         return logical.FALSE;
      }

      // check getters first
...

Are you OK with this fix?

I could even to include this fix in 9787a branch to speed the process.

The fix committed to 9787a revision 15781. Waiting for review and merge notification.