FWD » Core Development » User Interface

Then a window receives focus, and no field-level was in focus before in this window (for example, when a window is just opening), OE searches the window tab ring for a suitable field-level to set focus on.
For all suitable field-levels in the tab ring, OE sends ENTRY events, and selects the first field-level, for which the trigger code does not return NO-APPLY.

This seems to work the same in OE and FWD.

But for some reason, OE sends also an additional ENTRY event to the frame of the first tested field-level after the selection is done, and the focus is set to the suitable field. This trigger return is ignored.

No such event is sent in FWD.

The attached 8770.p example demonstrates this difference: in OE 3 ENTRY events are reported, while in FWD only 2 events are reported.

Fixed in 8809a rev. 15240.

The following code in TC.waitForWorker was probably intended to send ENTRY to the frame in question, but, at least in the case of focus was set with focusUndefImplicit, does this incorrectly:

      // or else generate frame ENTRY event, only if previous focus is not
      // part of this frame
      else
      {
         Frame frame = UiUtils.locateFrame(UiUtils.getCurrentFocus());
         if (saveFocus == null || frame != UiUtils.locateFrame(saveFocus))
         {
            if (frame != null)
               sendEntry(frame);

After the patch, the ENTRY event sent by the code must not be sent anymore.

Since this code works for all cases, not only for focusUndefImplicit, an additional investigation is required, to get the right way to fix this.