Community
Participate
Working Groups
build 20021213 Running on Motif, over the javaeditor, the menu pop-up when mouse button is released. But on different views I have to hold the button down to get the menu. The right behavior on Motif is to hold the button down to pop-up the menu. For the javaeditor the SWT support (Control.setMenu) for popup menu is not been used properly. This will break: Motif (different platform behavior), GTK (menu don`t get input method menu items added), Mac (different platform behavior).
This appears to be a duplicate of 19804. Moving to SWT for assessment.
Sonia, 19804 is not a duplicate but could be related. Are they trying to share the same menu? I don't think so but UI needs to decide. BTW: This PR is at least a P2 as it violates the platform menu behavior. It would not be so bad if every menu in Eclipse violated the platform but the menus in the tree and table widgets work properly. This makes it a real pain because you need to know how the menu is popped up, depending on the widget.
*** This bug has been marked as a duplicate of 27232 ***
This is not a duplicate of 27232. This problem occurs regardless of whether gestures are being used. There are several implications of popping the context menu up yourself rather than using setMenu. 1) It does not appear and disapperar at the right time. The correct behaviour depends on the platform. e.g. Windows - should appear on mouse up Motif - should appear on mouse down and disappear on mouse up Mac - should appear on mouse down and stay on mouse up Photon, QT and GTK have other variations on this. 2) For DBCS support on GTK we have added an IM (input method) item at the end of all context menus. This will only happen if you call setMenu. The Java editors are not DBCS enabled because they do not have this item on GTK. 3) The user should be able to make a context menu pop up from the keyboard for accessibility purposes. On Windows this is done with SHIFT + F10 and other platforms there may be something else. This does not work on the java editor. If setMenu were used, this would work.
Hey! This is really important. I'm surprised that this was not fixed for M4. I'm adding Nick in hope that something will happen.
This was not fixed for M4, although it was supposed to have been removed. I don't see rebuilding M4 just for this unless a product requires it. We will remove it early in M5. Kevin, let me know if this is critical for M4.
*** Bug 27232 has been marked as a duplicate of this bug. ***
gestures commented out until proper solution for them can be found. the newsgroup comments suggests some possible solutions, mostly involving a preference page that could allow the user to require that a modifier key be pressed, or alternate mouse button to be used, on certain platforms. (the opera browser doesn't seem to care much about this problem, and mozilla allows the user to choose a modifier key)
