Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.rse.ui.widgets
Interface IQSYSObjectPromptListener

All Superinterfaces:
IQSYSLibraryPromptListener
All Known Subinterfaces:
IQSYSMemberPromptListener, IQSYSModulePromptListener
All Known Implementing Classes:
AbstractNewQSYSObjectWizardMainPage, CommandExecutionPropertyPage, NewQSYSDataAreaWizardMainPage, NewQSYSDataQWizardMainPage, NewQSYSLibraryWizardMainPage, NewQSYSMemberWizardMainPage, NewQSYSMsgFileWizardMainPage, NewQSYSSourceFileWizardMainPage, QSYSFilterStringEditPaneMembers, QSYSFilterStringEditPaneObjects, QSYSOpenMemberDialog, SaveFileTransferAndRestoreDialog

public interface IQSYSObjectPromptListener
extends IQSYSLibraryPromptListener

Interface for users of ISeriesObjectPrompt widgets to be informed of error checking as user enters text or selects item in the library (see inherited methods) or object combo field.

This is a callback interface so that the caller can update the UI to reflect the error message and enable/disable OK/Final buttons


Field Summary
static String copyright
           
 
Method Summary
 void objectNameChanged(SystemMessage errorMessage)
          The user has entered or selected text in the object entry field and it has been validated by the ISeriesObjectPrompt.
 
Methods inherited from interface com.ibm.etools.iseries.rse.ui.widgets.IQSYSLibraryPromptListener
libraryNameChanged
 

Field Detail

copyright

static final String copyright
See Also:
Constant Field Values
Method Detail

objectNameChanged

void objectNameChanged(SystemMessage errorMessage)
The user has entered or selected text in the object entry field and it has been validated by the ISeriesObjectPrompt.

Parameters:
errorMessage - Will be null if the input is valid, or a translated msg if not

Rational Developer for Power Systems Software
V7.6

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.