Overview  Package   Class  Tree  Serialized  Deprecated  Index  Help 
Rational Developer for Power Systems Software
V7.6
 PREV CLASS   NEXT CLASS FRAMES    NO FRAMES    
SUMMARY: NESTED | FIELD | CONSTR | METHOD DETAIL: FIELD | CONSTR | METHOD

com.ibm.etools.iseries.rse.ui.actions
Class QSYSCascadingTableViewAction

java.lang.Object
  extended by SystemBaseSubMenuAction
      extended by com.ibm.etools.iseries.rse.ui.actions.QSYSCascadingTableViewAction

public class QSYSCascadingTableViewAction
extends SystemBaseSubMenuAction

A cascading menu action for "Show in table->"

Field Summary
static String Copyright
           
 
Constructor Summary
QSYSCascadingTableViewAction(Shell shell, IAction[] actions)
          Constructor
 
Method Summary
 void menuAboutToShow(IMenuManager ourSubMenu)
          Called when submenu is about to show
 IMenuManager populateSubMenu(IMenuManager menu)
           
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

Copyright

public static final String Copyright
See Also:
Constant Field Values
Constructor Detail

QSYSCascadingTableViewAction

public QSYSCascadingTableViewAction(Shell shell,
                                    IAction[] actions)
Constructor

Method Detail

populateSubMenu

public IMenuManager populateSubMenu(IMenuManager menu)
See Also:
SystemBaseSubMenuAction#createSubMenu(ResourceBundle, String)

menuAboutToShow

public void menuAboutToShow(IMenuManager ourSubMenu)
Called when submenu is about to show

Overview  Package   Class  Tree  Serialized  Deprecated  Index  Help 
Rational Developer for Power Systems Software
V7.6
 PREV CLASS   NEXT CLASS FRAMES    NO FRAMES    
SUMMARY: NESTED | FIELD | CONSTR | METHOD DETAIL: FIELD | CONSTR | METHOD
Copyright © 2011 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.