[Bug AWT/16758] AWT menu system should use new GtkAction API

["djee at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>]

------- Additional Comments From djee at redhat dot com  2004-07-30 14:28 -------
After some thought and discussion, it seems that it is not necessary to migrate
to the GtkAction/GtkUIManager API.  First off, the new GtkAction/GtkUIManager
API doesn't replace the old Menu, MenuShell, MenuBar, etc.  The new API simply
makes it easier for application developers to organize their menu hierarchy
using XML, and allows them to reuse stock "actions" in multiple instances (eg
having "Open" in both the main menu and the popup toolbar).  Once you register
all your actions with the UIManager, the UIManager will create the menu for you,
using the old widgets.  It's nice for app developers, but we don't really have
anything to gain from using this API.  In fact, the XML interface makes things a
bit hairy, especially when we want to reference menu elements by index.

Secondly, the main reason why we wanted to migrate to the new API is that we
thought it might allow us to implement menu accelerators.  But it turns out that
the code necessary to implement accelerators are already in place on the Java
side.  In fact, registering menu accelerators on the native side doesn't seem
necessary at all, because we're intercepting the GTK key events, and we're
processing them on the Java side.  Then if necessary, we activate MenuShortcuts.
 I committed a small patch that fixes some bugs regarding this, but other than
that, menu shortcuts are in good working shape, I think.

I'm marking this as WONTFIX.  Is that the appropriate tag in this case?

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WONTFIX


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16758