FWD » Core Development » User Interface

1. In swing, when an item is selected, but has no mouse over it, the text is not properly highlighted (so the item has black text on the dark blue background). Also, there may be an issue with swing when the first item of a sub-menu is selected by default while it shouldn't (customer's server is down, so I cannot check if it is an actual issue).
2. When an item in sub-menu is clicked, parent menu is not closed.

Testcase:

def var mnu as handle.
def var item1 as handle.
def var item2 as handle.
def var sm as handle.

CREATE MENU mnu
      ASSIGN
        POPUP-ONLY = TRUE
        TITLE      = 'Browser Menu'.

CREATE MENU-ITEM item1
        ASSIGN
          PARENT = mnu
          LABEL  = "item1" 
          NAME   = "item1".      

CREATE sub-menu sm
        ASSIGN
          PARENT = mnu
          LABEL  = "submenu" 
          NAME   = "submenu".       

CREATE MENU-ITEM item2
        ASSIGN
          PARENT = sm
          LABEL  = "item2" 
          NAME   = "item2".       

def var s as char.
form s with frame f1.
s:popup-menu = mnu.
update s with frame f1.

Created task branch 3487a.

Checked in revision 11247 to 3487a.

• popup menu not shown after popup overlay window lost focus
• popup menu was not properly processing key events after opened (focus issues)
• highlight state was not reset between popup invocations
• multiple abends and unexpected exceptions
• prevented abend caused by Fill-in widget selection logic
• prevented abend during menu setup when static sub-menu didn't have a parent menu

The code changes still require code cleanup and extensive regression testing, so far I ran only some limited number of trivial test cases.

3487a rebased against trunk 11248.

3487a rebased against trunk 11249.

3487a revision 11256 fixes this issue plus #3462, #3508, #3532.

Regression testing is in progress. Please review.

Code Review Task Branch 3487a Revision 11256

These changes are really good. I see no functional issues.

One minor code standard thing, protected Menu<O> showPopupMenu(MouseEvent e) should be moved below the public methods in AbstractWidget.

3487a revision 11258 resolves the points from the last review. It passed GUI regression tests (a large customer's GUI app, Hotel GUI, some of the menu test cases in uast, in both Swing and Web GUI). ChUI regression testing is in progress.

I found two more minor issues (both exist in trunk):
(1) Sometime when menu bar is navigated by mouse, an empty submenu body is displayed.
(2) In the large customer's GUI app one of the popup menu shows empty selectable menu item instead of a menu separator.

While regression testing 3487a I see client abends which prevent me to run all the required cases. These errors already exist in trunk. Greg, should I resolve these issues in a separate task branch?

The existing revision of 3487a is a significant improvement over trunk, right? Unless there are regressions, I would prefer to put it into trunk and work the remaining issues in another branch.

Code Review Task branch 3487a Revision 11258

I'm good with the changes.

ChUI regression test harness finished with some failures which are most likely negative failures. I restarted the tests.

Greg Shah wrote:

The existing revision of 3487a is a significant improvement over trunk, right?

Yes, it fixes some serious issues.

When it passes testing, merge to trunk.

3487a passed ChUI test harness. I am merging to trunk.

3487a rebased and merged to trunk as revision 11251. The branch was archived.

The ChUI menu regressions are more serious than I thought. I created new issue #3553 and checked in my WIP changes there.

Also I checked in a simple NPE fix to 3487b. Please review this change. No regression testing for the branch is needed. There are no more changes expected for this issue.

Code Review Task Branch 3487b Revision 11252

I'm fine with the change.

Are you proposing to merge this to trunk now? Or do you plan to include the changes for #3538?

Greg Shah wrote:

Are you proposing to merge this to trunk now? Or do you plan to include the changes for #3538?

Yes, it can be included with the changes for #3538.

Merged the only change in 3487b to 3553a.

Correction, merged the change in 3487b to 3538a.

3487b dead-archived.

The issue was resolved in 3538c, which was merged to trunk as revision 11255.