okteta
crc32bytearraychecksumalgorithm.cpp
Go to the documentation of this file.
86 AbstractByteArrayChecksumParameterSet* Crc32ByteArrayChecksumAlgorithm::parameterSet() { return &mParameterSet; }
could it be useful to hide the data access behind an iterator? * class KDataBufferIterator { public: ...
Definition: abstractbytearraymodel.h:79
NoByteArrayChecksumParameterSet mParameterSet
Definition: crc32bytearraychecksumalgorithm.h:43
static const int CalculatedByteCountSignalLimit
Definition: abstractbytearraychecksumalgorithm.h:43
virtual ~Crc32ByteArrayChecksumAlgorithm()
Definition: crc32bytearraychecksumalgorithm.cpp:113
virtual bool calculateChecksum(QString *result, const Okteta::AbstractByteArrayModel *model, const Okteta::AddressRange &range) const
Definition: crc32bytearraychecksumalgorithm.cpp:88
virtual AbstractByteArrayChecksumParameterSet * parameterSet()
used by the editor to get write access to the parameters
Definition: crc32bytearraychecksumalgorithm.cpp:86
Crc32ByteArrayChecksumAlgorithm()
Definition: crc32bytearraychecksumalgorithm.cpp:81
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...
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:07 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:07 by doxygen 1.8.7 written by Dimitri van Heesch, © 1997-2006
KDE's Doxygen guidelines are available online.