iSeries Remote Systems
v6.0.0

com.ibm.etools.iseries.core.util.clprompter
Class ClScrollBarListener

java.lang.Object
  extended byorg.eclipse.swt.events.KeyAdapter
      extended bycom.ibm.etools.iseries.core.util.clprompter.ClScrollBarListener
All Implemented Interfaces:
EventListener, FocusListener, KeyListener, SWTEventListener

public class ClScrollBarListener
extends KeyAdapter
implements FocusListener

This class is used to ensure that when focus is placed on a field (by tabbing or clicking on it, the field is displayed. If the field is not, the the composite is scrolled so that the widget appears. It also handles scrolling when the page up and down keys are pressed.

Since:
5.1.2

Constructor Summary
ClScrollBarListener(Object control)
           
 
Method Summary
 void focusGained(FocusEvent e)
           
 void focusLost(FocusEvent e)
           
 void keyPressed(KeyEvent e)
          Handles page up and down keys
 
Methods inherited from class org.eclipse.swt.events.KeyAdapter
keyReleased
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

ClScrollBarListener

public ClScrollBarListener(Object control)
Method Detail

focusGained

public void focusGained(FocusEvent e)
Specified by:
focusGained in interface FocusListener

focusLost

public void focusLost(FocusEvent e)
Specified by:
focusLost in interface FocusListener

keyPressed

public void keyPressed(KeyEvent e)
Handles page up and down keys

Specified by:
keyPressed in interface KeyListener
Since:
6.0
See Also:
KeyListener.keyPressed(org.eclipse.swt.events.KeyEvent)

iSeries Remote Systems
v6.0.0

Copyright © 2005 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.