civquest.swing.quadmap.fieldview
Class QuadIsoLayeredFieldView

java.lang.Object
  civquest.swing.fieldview.CompositeFieldView
      civquest.swing.fieldview.LayeredFieldView
          civquest.swing.quadmap.fieldview.QuadIsoLayeredFieldView

All Implemented Interfaces:

FieldView, FieldViewManager, QuadFieldView, QuadIsoFieldView

public class QuadIsoLayeredFieldView

extends LayeredFieldView

implements QuadIsoFieldView

A LayeredFieldView that paints on quad iso maps.

Field Summary

Fields inherited from class civquest.swing.fieldview.LayeredFieldView

terrainView

Fields inherited from class civquest.swing.fieldview.CompositeFieldView

field, parent

Constructor Summary

QuadIsoLayeredFieldView(Field field, FieldViewManager parent, Registry registry)

Method Summary

void	updateImage() If this FieldView stores some images (and doesn't just load and calculate the needed images inside the paint-method), this method recalculates that images.

Methods inherited from class civquest.swing.fieldview.LayeredFieldView

getListenerSectionsForParent, getPaintSize, paint

Methods inherited from class civquest.swing.fieldview.CompositeFieldView

getField, repaintChildFieldView

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Methods inherited from interface civquest.swing.fieldview.FieldView

getField, getListenerSectionsForParent, getPaintSize, paint

Constructor Detail

QuadIsoLayeredFieldView

public QuadIsoLayeredFieldView(Field field,
                               FieldViewManager parent,
                               Registry registry)

Method Detail

updateImage

public void updateImage()

Description copied from interface: FieldView

If this FieldView stores some images (and doesn't just load and calculate the needed images inside the paint-method), this method recalculates that images.

So this method should be called whenever some data the FieldView displays changes.

Note: Subinterfaces / implementing classes may specify that they listen to all required GameChanges directly. Then, calling this method from the XXXChanged-methods inside the FieldView suffices. (This behaviour can't be standard since some thousand Fields listening to a GameChange affecting just one or two Fields would be pretty inefficient).

Specified by:

updateImage in interface FieldView