Community
Participate
Working Groups
If you have a look at the AbstractAction (scout model) hierarchy: ---AbstractAction +---AbstractToolButton | \---AbstractMenu +---AbstractKeyStroke +---AbstractToolButton | \---AbstractFromToolButton<FORM> \---AbstractViewButton \---AbstractOutlineViewButton This hierarchy isn’t reflected in the Swt renderer plugin, leading to incomplete behavior. For example the AbstractSwtAction (corresponding to the Scout AbstractAction), does’nt react on AbstractAction#setEnabled(). The hierarchy in the SWT Part should be fixed.
Minimal change (common code between SwtScoutAction and AbstractSwtMenuAction): https://git.eclipse.org/r/20169 The problem is that there is still some duplicate code between SwtScoutComposite and AbstractSwtScoutAction. I will try to come with a v2 of the change.
The second version is pushed to Gerrit: https://git.eclipse.org/r/#/c/20169/2 Common code between AbstractSwtScoutAction and SwtScoutComposite is now in SwtScoutListener.
Pushed with commit b870ee6c71fb7647ae3663b236c7b9fd9d1a0ccc on develop: http://git.eclipse.org/c/scout/org.eclipse.scout.rt.git/commit/?id=b870ee6c71fb7647ae3663b236c7b9fd9d1a0ccc @Matthias.Nick: Can you verify please?
Change looks good to me. Verified with org.eclipse.scout.rt.ui.swt 3.10.0.20140205-1810
Shipped with Eclipse Luna Release