okteta
utf32stringdata.cpp
Go to the documentation of this file.
could it be useful to hide the data access behind an iterator? * class KDataBufferIterator { public: ...
Definition: abstractbytearraymodel.h:79
Definition: stringdata.h:36
TopLevelDataInformation * topLevelDataInformation() const
Definition: datainformation.cpp:240
void _childCountAboutToChange(DataInformation *sender, uint oldCount, uint newCount)
Definition: topleveldatainformation.h:184
void _childCountChanged(DataInformation *sender, uint oldCount, uint newCount)
Definition: topleveldatainformation.h:192
Definition: stringdata.h:45
Definition: stringdata.h:43
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...
union StringData::@5 mLength
virtual qint64 read(Okteta::AbstractByteArrayModel *input, Okteta::Address address, BitCount64 bitsRemaining)
Definition: utf32stringdata.cpp:108
virtual QString stringValue(int row) const
Definition: utf32stringdata.cpp:59
virtual QString completeString(bool skipInvalid=false) const
Definition: utf32stringdata.cpp:80
Definition: stringdata.h:42
Utf32StringData(StringDataInformation *parent)
Definition: utf32stringdata.cpp:35
Definition: stringdata.h:44
Definition: stringdatainformation.h:39
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.