Modules/ColorTableMod/ColorTable64Mod.cpp

Go to the documentation of this file.

/** 
* @file ColorTable64Mod.cpp
* Implementation of class ColorTable64Mod.
*
* @author <A href=mailto:walter.nistico@uni-dortmund.de>Walter Nistico</A>
*/

#include "ColorTable64Mod.h"
#include "Tools/Location.h"

/* 
I don't like this.
Directly copying an object to a memory buffer is a C-style low level way of instantiating it, 
beside, the initialization of the memory buffer looks quite ugly because of the test operators
to determine the size of the biggest colortable object, and it gets worser and worser as new
colortables are implemented.
I have a more elegant solution which gives access to colortables to the image processors 
through a colortable pointer: it works, but it needed a thorough rewriting of the image processor
interface, and it has a potential for problems with image processors designed to use a 
single color table (ColorTable64) such as GridImageProcessor2.
If you want to support this second approach, please write me an e-mail.
*/
void ColorTable64Mod::setup()
{
  ColorTable64* colorTable64 = new ColorTable64();
  InBinaryFile stream(getLocation().getModelFilename("coltable.c64"));
  colorTable64->setFormat(ColorTable64::CT64);
  if (stream.exists())
  {
    stream >> *colorTable64;
  }else{
    OUTPUT(idText, text, "load coltable.c64 FAILT");
  }
  memcpy(colorTable, colorTable64, sizeof(ColorTable64));
  delete colorTable64;
}

void ColorTable64Mod::execute()
{
  //dont work hier why
  INFO(sendColorTable64, idText, text, "send Colortable");
  INFO(sendColorTable64, idColorTable64, bin, *(const ColorTable64*)&colorTable);
}

---