LPEX
3.6.8

com.ibm.lpex.alef
Class LpexSourceViewer.RulerLayout

java.lang.Object
  extended by Layout
      extended by com.ibm.lpex.alef.LpexSourceViewer.RulerLayout
Enclosing class:
LpexSourceViewer

protected class LpexSourceViewer.RulerLayout
extends Layout

Layout of this source viewer. The vertical ruler, the LPEX text widget, and an overview ruler are shown side by side. The LPEX text widget window sits on top of a prompt window.


Field Summary
protected  int fGap
          The gap between the text viewer and the vertical ruler.
 
Constructor Summary
LpexSourceViewer.RulerLayout(int gap)
          Creates a new ruler layout with the given gap between text viewer and vertical ruler.
 
Method Summary
protected  Point computeSize(Composite composite, int wHint, int hHint, boolean flushCache)
           
protected  void layout(Composite composite, boolean flushCache)
           
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

fGap

protected int fGap
The gap between the text viewer and the vertical ruler.

Constructor Detail

LpexSourceViewer.RulerLayout

public LpexSourceViewer.RulerLayout(int gap)
Creates a new ruler layout with the given gap between text viewer and vertical ruler.

Parameters:
gap - the gap between text viewer and vertical ruler
Method Detail

computeSize

protected Point computeSize(Composite composite,
                            int wHint,
                            int hHint,
                            boolean flushCache)

layout

protected void layout(Composite composite,
                      boolean flushCache)

LPEX
3.6.8

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