Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.ui
Interface EditmaskViewInterface

All Superinterfaces:
ViewFactory
All Known Implementing Classes:
EditmaskViewBasicTextFieldUI, EditmaskViewMetalTextFieldUI, EditmaskViewWindowsTextFieldUI

public interface EditmaskViewInterface
extends ViewFactory

Normally, it is only the classes that extend TextFieldUI and create EditmaskPlainView classes that need to implement this interface.

See Also:
EditmaskAttributes, EditmaskPlainView, EditmaskViewBasicTextFieldUI, EditmaskViewMetalTextFieldUI

Field Summary
static String copyright
           
 
Method Summary
 EditmaskAttributes getEditmaskAttributes()
          Return EditmaskAttributes.
 EditmaskPlainView getEditmaskPlainView()
          Return EditmaskPlainView.
 String getFormattedText()
          Return user input text with the editmask format.
 void setEditmaskAttributes(EditmaskAttributes attrib)
          Replace EditmaskAttributes
 
Methods inherited from interface javax.swing.text.ViewFactory
create
 

Field Detail

copyright

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

getEditmaskAttributes

EditmaskAttributes getEditmaskAttributes()
Return EditmaskAttributes.

Returns:
com.ibm.etools.iseries.ui.EditmaskAttributes

getEditmaskPlainView

EditmaskPlainView getEditmaskPlainView()
Return EditmaskPlainView.

Returns:
com.ibm.etools.iseries.ui.EditmaskPlainView

getFormattedText

String getFormattedText()
Return user input text with the editmask format.

Returns:
java.lang.String

setEditmaskAttributes

void setEditmaskAttributes(EditmaskAttributes attrib)
Replace EditmaskAttributes

Parameters:
attrib - com.ibm.etools.iseries.ui.EditmaskAttributes

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.