com.ibm.etools.iseries.edit.wizards
Class RPGDSpecKeywordBasePane
java.lang.Object
com.ibm.etools.iseries.edit.wizards.RPGDSpecKeywordBasePane
- Direct Known Subclasses:
- RPGDSpecArrayKeywordsPane, RPGDSpecOtherKeywordsPane, RPGDSpecSimpleSubfieldKeywordsPane
public class RPGDSpecKeywordBasePane
- extends Object
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
copyright
public static final String copyright
- See Also:
- Constant Field Values
selects
protected boolean[] selects
container
protected Object container
errorMessage
protected SystemMessage errorMessage
RPGDSpecKeywordBasePane
public RPGDSpecKeywordBasePane(Object container)
initValidators
protected void initValidators()
setErrorMessage
public void setErrorMessage(Object container,
SystemMessage errorMessage)
clearErrorMessage
protected void clearErrorMessage(Object container,
RPGDSpecKeywordBasePane keywordPane)
isPaneComplete
public boolean isPaneComplete()
isSelected
protected boolean isSelected(Button btn)
populateSFKeyword
public void populateSFKeyword(RPGDSpecSubfieldKeywords kwd)
setEnabled
protected void setEnabled(Button btn,
boolean enabled)
setFocus
protected void setFocus(RPGKeywordEntry entry)
initSelections
protected void initSelections()
getSelections
public boolean[] getSelections()
- Returns:
updateContainerKeywords
protected void updateContainerKeywords()
checkError
protected void checkError(RPGKeywordEntry skip,
boolean setFocus)
validatePane
public SystemMessage validatePane(RPGKeywordEntry skip,
boolean setFocus)
getContainer
public Object getContainer()
- Returns:
- the container this pane is on
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.