#include <RestorePoints.h>
List of restore points.
- Note
- This class is based on observations, as there is no public documentation available. There are undocumented API functions for RestorePoint handling. And this seems like it.
◆ calculateObjectSize()
uint32_t Vector::BLF::RestorePoints::calculateObjectSize |
( |
| ) |
const |
|
virtual |
Calculates the objectSize
- Returns
- object size
◆ read()
Read the data of this object
- Parameters
-
◆ write()
Write the data of this object
- Parameters
-
◆ objectInterval
uint32_t Vector::BLF::RestorePoints::objectInterval {1000} |
object interval
This is the interval between RestorePoints. Actually, due to a bug in the implementation, the interval is actually objectInterval + 1; Default is 1000, so it's storing a list, which point to each 1001stth object.
◆ objectSize
uint32_t Vector::BLF::RestorePoints::objectSize {0x00180008} |
- Todo
- Is this the maximum byte size of the restorePoints vector?
Not sure with this.
objectSize is usually 0x00180008=1572872. Reduced by sizeof(objectSize) + sizeof(objectInterval) lefts 1572864 bytes for restorePoints. Each RestorePoint has 24 bytes, which would result in 65536 elements. Seems like a potential maximum for the RestorePoints. But why does this need to be stored in the file?
Actually restorePointData.size() in this example, was just 20936, based on available data, which is 502464 bytes. So I would have expected to see objectSize=502472.
◆ restorePoints
std::vector<RestorePoint> Vector::BLF::RestorePoints::restorePoints {} |
The documentation for this struct was generated from the following files: