Home » openjdk-7 » javax » swing » text » [javadoc | source]
public class: AsyncBoxView.ChildState [javadoc | source]

All Implemented Interfaces:

A record representing the layout state of a child view. It is runnable as a task on another thread. All access to the child view that is based upon a read-lock on the model should synchronize on this object (i.e. The layout thread and the GUI thread can both have a read lock on the model at the same time and are not protected from each other). Access to a child view hierarchy is serialized via synchronization on the ChildState instance.
 public ChildState(View v) 
    Construct a child status. This needs to start out as fairly large so we don't falsely begin with the idea that all of the children are visible.
    since: 1.4 -
Method from javax.swing.text.AsyncBoxView$ChildState Summary:
getChildView,   getMajorOffset,   getMajorSpan,   getMinorOffset,   getMinorSpan,   isLayoutValid,   preferenceChanged,   run,   setMajorOffset,   updateChild
Methods from java.lang.Object:
clone,   equals,   finalize,   getClass,   hashCode,   notify,   notifyAll,   toString,   wait,   wait,   wait
Method from javax.swing.text.AsyncBoxView$ChildState Detail:
 public View getChildView() 
    Fetch the child view this record represents
 public float getMajorOffset() 
    Get the offset along the major axis
 public float getMajorSpan() 
    What is the span along the major axis.
 public float getMinorOffset() 
    What is the offset along the minor axis
 public float getMinorSpan() 
    What is the span along the minor axis.
 public boolean isLayoutValid() 
    Has the child view been laid out.
 public  void preferenceChanged(boolean width,
    boolean height) 
    Mark preferences changed for this child.
 public  void run() 
    Update the child state. This should be called by the thread that desires to spend time updating the child state (intended to be the layout thread).

    This aquires a read lock on the associated document for the duration of the update to ensure the model is not changed while it is operating. The first thing to do would be to see if any work actually needs to be done. The following could have conceivably happened while the state was waiting to be updated:

    1. The child may have been removed from the view hierarchy.
    2. The child may have been updated by a higher priority operation (i.e. the child may have become visible).
 public  void setMajorOffset(float offs) 
    This method should only be called by the ChildLocator, it is simply a convenient place to hold the cached location.
  void updateChild()