apollo.gui
Interface TierManagerI

All Superinterfaces:
ControlledObjectI, java.io.Serializable
All Known Subinterfaces:
DrawableTierManagerI, FeatureTierManagerI
All Known Implementing Classes:
DrawableTierManager, FeatureTierManager, SiteTierManager, TierManager

public interface TierManagerI
extends ControlledObjectI


Field Summary
static long Y_PIXELS_PER_FEATURE
          I believe COORDS_PER_PIXEL is only used in the vertical/y direction.
 
Method Summary
 void decrementTierHeight()
           
 void doLayoutTiers()
           
 void fireTierManagerEvent(int type)
           
 int getAggregateSizeChange()
           
 int getLowestVisible()
           
 long getMaxTierUserHeight()
           
 long getMaxUserCoord()
           
 int getMaxVisibleTierNumber()
           
 int getMinimumVisibleTransformCoord()
           
 int getNumTiers()
           
 int getNumVisible()
           
 Tier getTier(int tier_number)
           
 java.util.Vector getTiers()
           
 int getTotalHeight()
           
 ViewI getView()
           
 long getVisibleUserCoord()
           
 int[] getYRange()
           
 void incrementTierHeight()
           
 void setAggregateSizeChange(int change)
           
 void setCharHeight(int height)
           
 void setIgnoreScoreThresholds(boolean ignore)
           
 void setLowestVisible(int lowest)
           
 void setTierData(java.lang.Object data)
           
 void setView(ViewI view)
           
 void setViewHeight(int height)
           
 long toTier(long userCoord)
           
 int toUser(int tierNum)
           
 
Methods inherited from interface apollo.gui.ControlledObjectI
getController, getControllerWindow, needsAutoRemoval, setController
 

Field Detail

Y_PIXELS_PER_FEATURE

static final long Y_PIXELS_PER_FEATURE
I believe COORDS_PER_PIXEL is only used in the vertical/y direction. It can't be for the x direction as its dynamic with zooming. So I guess I'm wondering why bother having coords per pixel in the y direction. Why not just have pixels? There is no real y axis, its just a layout issue. I guess I'm missing what the coordinates are doing for us and why is it 10? Is this to leave open the possibility of zooming in the y direction in which case these parameter would be dynamic.

See Also:
Constant Field Values
Method Detail

setView

void setView(ViewI view)

getView

ViewI getView()

setViewHeight

void setViewHeight(int height)

setCharHeight

void setCharHeight(int height)

doLayoutTiers

void doLayoutTiers()

getYRange

int[] getYRange()

setTierData

void setTierData(java.lang.Object data)

incrementTierHeight

void incrementTierHeight()

decrementTierHeight

void decrementTierHeight()

getTotalHeight

int getTotalHeight()

getNumTiers

int getNumTiers()

getNumVisible

int getNumVisible()

getLowestVisible

int getLowestVisible()

setLowestVisible

void setLowestVisible(int lowest)

getMaxVisibleTierNumber

int getMaxVisibleTierNumber()

getMinimumVisibleTransformCoord

int getMinimumVisibleTransformCoord()

getVisibleUserCoord

long getVisibleUserCoord()

getMaxUserCoord

long getMaxUserCoord()

getMaxTierUserHeight

long getMaxTierUserHeight()

toTier

long toTier(long userCoord)

toUser

int toUser(int tierNum)

getTiers

java.util.Vector getTiers()

getTier

Tier getTier(int tier_number)

getAggregateSizeChange

int getAggregateSizeChange()

setAggregateSizeChange

void setAggregateSizeChange(int change)

setIgnoreScoreThresholds

void setIgnoreScoreThresholds(boolean ignore)

fireTierManagerEvent

void fireTierManagerEvent(int type)