jACOB 2.7 API Documentation.

de.tif.jacob.screen
Interface IToolbar

All Superinterfaces:
IGuiElement

public interface IToolbar
extends IGuiElement


Nested Class Summary
 
Nested classes/interfaces inherited from interface de.tif.jacob.screen.IGuiElement
IGuiElement.GroupState
 
Field Summary
static java.lang.String RCS_ID
           
static java.lang.String RCS_REV
           
 
Fields inherited from interface de.tif.jacob.screen.IGuiElement
NEW, SEARCH, SELECTED, UNDEFINED, UPDATE
 
Method Summary
 IToolbarButton getButton(ActionType type)
          The buttons of the handsover action or null of the toolbar doesn't contain this type of button.
 java.util.List getButtons()
           
 
Methods inherited from interface de.tif.jacob.screen.IGuiElement
findByName, getApplicationDefinition, getChildren, getDataStatus, getGroupTableAlias, getI18NLabel, getLabel, getName, getParent, getPathName, hasChild, isEnabled, isVisible, setBackgroundColor, setColor, setEnable, setLabel, setVisible
 

Field Detail

RCS_ID

static final java.lang.String RCS_ID
See Also:
Constant Field Values

RCS_REV

static final java.lang.String RCS_REV
See Also:
Constant Field Values
Method Detail

getButtons

java.util.List getButtons()
Returns:
List[IToolbarButton] the children

getButton

IToolbarButton getButton(ActionType type)
The buttons of the handsover action or null of the toolbar doesn't contain this type of button.
It is not required, that the button is visible in the toolbar. It must only a member of the toolbar.
TODO Wie soll man besser einen Button identifiezieren?! Soll man wirklich die "Action"an den AppProgrammierer weiter reichen?

Parameters:
type -
Returns:
The buttons of the handsover action or null of the toolbar doesn't contain this type of button.

jACOB 2.7 API Documentation.