Class VolatileByteType

java.lang.Object
net.imglib2.Volatile<ByteType>
net.imglib2.type.volatiles.AbstractVolatileRealType<ByteType, VolatileByteType>
net.imglib2.type.volatiles.AbstractVolatileNativeRealType<ByteType, VolatileByteType>
net.imglib2.type.volatiles.VolatileByteType
All Implemented Interfaces:
Comparable<VolatileByteType>, NativeType<VolatileByteType>, ComplexType<VolatileByteType>, NumericType<VolatileByteType>, RealType<VolatileByteType>, Add<VolatileByteType>, Div<VolatileByteType>, Mul<VolatileByteType>, MulFloatingPoint, Pow<VolatileByteType>, PowFloatingPoint, SetOne, SetZero, Sub<VolatileByteType>, ValueEquals<VolatileByteType>, Type<VolatileByteType>
public class VolatileByteType extends AbstractVolatileNativeRealType<ByteType, VolatileByteType>
A Volatile variant of ByteType. It uses an underlying ByteType that maps into a VolatileByteAccess.

  • Field Details

  • Constructor Details

    • VolatileByteType

      public VolatileByteType(NativeImg<?, ? extends VolatileByteAccess> img)

    • VolatileByteType

      public VolatileByteType(VolatileByteAccess access)

    • VolatileByteType

      public VolatileByteType(byte value)

    • VolatileByteType

      public VolatileByteType()

  • Method Details

    • set

      public void set(byte value)

    • updateContainer

      public void updateContainer(Object c)
      Description copied from interface: NativeType
      This method is used by an accessor (e.g., a Cursor) to request an update of the current data array.

      As an example consider a CellCursor moving on a CellImg. The cursor maintains a NativeType which provides access to the image data. When the cursor moves from one cell to the next, the underlying data array of the NativeType must be switched to the data array of the new cell.

      To achieve this, the CellCursor calls updateContainer() with itself as the argument. updateContainer() in turn will call NativeImg.update(Object) on it's container, passing along the reference to the cursor. In this example, the container would be a CellImg. While the NativeType does not know about the type of the cursor, the container does. CellImg knows that it is passed a CellCursor instance, which can be used to figure out the current cell and the underlying data array, which is then returned to the NativeType.

      The idea behind this concept is maybe not obvious. The NativeType knows which basic type is used (float, int, byte, ...). However, it does not know how the data is stored (ArrayImg, CellImg, ...). This prevents the need for multiple implementations of NativeType .

      Parameters:
      c - reference to an accessor which can be passed on to the container (which will know what to do with it).

    • duplicateTypeOnSameNativeImg

      public VolatileByteType duplicateTypeOnSameNativeImg()
      Description copied from interface: NativeType
      Creates a new NativeType which stores in the same physical array. This is only used internally.
      Returns:
      a new NativeType instance working on the same NativeImg

    • createVariable

      public VolatileByteType createVariable()
      Description copied from interface: Type
      Creates a new Type variable which can only store one value.
      Returns:
      a new Type variable

    • copy

      public VolatileByteType copy()
      Description copied from interface: Type
      Creates a new Type variable that has the value of this Type
      Returns:
      a new Type variable

    • getNativeTypeFactory

      public NativeTypeFactory<VolatileByteType, ?> getNativeTypeFactory()