okteta
template_bytearraychecksumalgorithm.cpp
Go to the documentation of this file.
29 AbstractByteArrayChecksumParameterSet* Template_ByteArrayChecksumAlgorithm::parameterSet() { return &mParameterSet; }
could it be useful to hide the data access behind an iterator? * class KDataBufferIterator { public: ...
Definition: abstractbytearraymodel.h:79
static const int CalculatedByteCountSignalLimit
Definition: abstractbytearraychecksumalgorithm.h:43
Template_ByteArrayChecksumParameterSet mParameterSet
Definition: template_bytearraychecksumalgorithm.h:44
virtual ~Template_ByteArrayChecksumAlgorithm()
Definition: template_bytearraychecksumalgorithm.cpp:61
virtual bool calculateChecksum(QString *result, const Okteta::AbstractByteArrayModel *model, const Okteta::AddressRange &range) const
Definition: template_bytearraychecksumalgorithm.cpp:31
virtual Byte byte(Address offset) const =0
locates working range The idea behind is to tell buffer which range will be requested in the followin...
virtual AbstractByteArrayChecksumParameterSet * parameterSet()
used by the editor to get write access to the parameters
Definition: template_bytearraychecksumalgorithm.cpp:29
int bitNumber() const
Definition: template_bytearraychecksumparameterset.cpp:38
Template_ByteArrayChecksumAlgorithm()
Definition: template_bytearraychecksumalgorithm.cpp:21
void calculatedBytes(int bytes) const
This file is part of the KDE documentation.
Documentation copyright © 1996-2014 The KDE developers.
Generated on Tue Oct 14 2014 23:04:09 by doxygen 1.8.7 written by Dimitri van Heesch, © 1997-2006
Documentation copyright © 1996-2014 The KDE developers.
Generated on Tue Oct 14 2014 23:04:09 by doxygen 1.8.7 written by Dimitri van Heesch, © 1997-2006
KDE's Doxygen guidelines are available online.