Rational Developer for Power Systems Software

Class ISeriesDataTableViewPositionToAction

  extended by SystemBaseDialogAction
      extended by com.ibm.etools.iseries.rse.ui.actions.QSYSSystemBaseDialogAction
          extended by com.ibm.etools.iseries.rse.ui.actions.datatableview.ISeriesDataTableViewPositionToAction

public class ISeriesDataTableViewPositionToAction
extends QSYSSystemBaseDialogAction

This action displays the Position To dialog and tells the view to do the positioning

Field Summary
static String copyright
Constructor Summary
ISeriesDataTableViewPositionToAction(Shell parent, ISeriesDataTableView target)
          Constructor for ISeriesObjTableViewPositionToAction
Method Summary
protected  Dialog createDialog(Shell parent)
          Create the dialog.
protected  Object getDialogValue(Dialog dlg)
          Get the dialog value.
 void primeWith(char c)
Methods inherited from class com.ibm.etools.iseries.rse.ui.actions.QSYSSystemBaseDialogAction
getIBMiConnection, updateSelection
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail


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


public ISeriesDataTableViewPositionToAction(Shell parent,
                                            ISeriesDataTableView target)
Constructor for ISeriesObjTableViewPositionToAction

Method Detail


protected Dialog createDialog(Shell parent)
Create the dialog. Required by parent.


protected Object getDialogValue(Dialog dlg)
Get the dialog value. Required by parent.


public void primeWith(char c)

Rational Developer for Power Systems Software

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.