Community
Participate
Working Groups
"Previous Search Results" drop down goes off-screen when window maximized in KDE. This happens in Search View.
Created attachment 5026 [details] In Search View, the drop down menu for "Previous Search" ends up off-screen (bottom right of picture)
The search view uses standard Platform UI code to show that menu.
Moving back to Platform UI. The positioning of the menu is done by JFace. I believe the code is in ActionContributionItem.handleWidgetSelection. This code just positions the menu under the toolitem. It does not consider whether the menu will be offscreen either to the right or below.: } else if ((style & SWT.DROP_DOWN) != 0) { if (e.detail == 4) { // on drop-down button if (action.getStyle() == IAction.AS_DROP_DOWN_MENU) { IMenuCreator mc = action.getMenuCreator(); ToolItem ti = (ToolItem) item; // we create the menu as a sub-menu of "dummy" so that we can use // it in a cascading menu too. // If created on a SWT control we would get an SWT error... //Menu dummy= new Menu(ti.getParent()); //Menu m= mc.getMenu(dummy); //dummy.dispose(); if (mc != null) { Menu m= mc.getMenu(ti.getParent()); if (m != null) { // position the menu below the drop down item Rectangle b = ti.getBounds(); Point p = ti.getParent().toDisplay(new Point(b.x, b.y+b.height)); m.setLocation(p.x, p.y); // waiting for SWT 0.42 m.setVisible(true); return; // we don't fire the action } } } } }
While this code has not changed, I do not see the visual effect described. Window is maximized, KDE 3.2, GTK 2.2.4, and Eclipse I20040219. Do you still see the problem in a recent Eclipse 3.0 integration build?
Hi Douglas! Unfortunately, I'm using M7's GTK (on KDE 3.0.5 though) and still have this problem.
What version of GTK+ are you using? I cannot reproduce this under GNOME 2.2 or KDE 3.1, using either GTK+ 2.2.1 or GTK+ 2.4.9. I wonder if this may have been a limitation in the GTK+ 2.0.x series?
No response, closing as WORKSFORME. Please re-open if you have more information.
Hello all, My apologies for the lack of response as I've been away from the office :) Billy & Douglas, thanks for doing the checks! This bug did happen a while ago so it could possibly have been a version limitation or fixed indirectly since. Thanks for closing the bug! :) Yours, C.
*** Bug 29227 has been marked as a duplicate of this bug. ***