| Class | Description |
|---|---|
| BinaryDataSource |
Not just a source, but also a sink for binary data from the
binary store.
|
| BinaryFooter | |
| BinaryHeader | |
| BinaryHeaderAndFooter | |
| BinaryInputStream |
Used to read data back from a binary data file and either send
it off to the associated PamDataBlock or hand it back to the
BinaryStore controller, e.g.
|
| BinaryMapMakeProgress | |
| BinaryMapMakingDialog |
Not really a dialog, but displayed by BinaryStore while its making maps
of stored data during Viewer operation.
|
| BinaryObjectData |
Class to temporarily hold an objected data that has just been read from
a binary file.
|
| BinaryOfflineDataMap |
A binary offline data map is a datamap for a single data stream (i.e.
|
| BinaryOfflineDataMapPoint | |
| BinaryOutputStream |
Handles writing of an actual binary data file.
|
| BinarySettingsStorage |
Manage storage and retrieval of PAMGUARD serialised settings storage in
binary files.
|
| BinaryStorageDialog | |
| BinaryStorageDialogPanel | |
| BinaryStore |
The binary store will work very much like the database in that it
monitors the output of data streams and when data is added to them
it writes it to the binary store.
|
| BinaryStoreProcess | |
| BinaryStoreSettings | |
| BinaryTypes | |
| DataMapSerialiser | |
| DataUnitFileInformation |
Little bit of data to add to all PamDataUnits
when they are read back from a file which will
be used to say which file they were from, whether they
need updating, etc.
|
| DateRoundingTest | |
| ModuleFooter |
Class to contain module specific information
which will be stored at the end of a binary
data file, just before the BinaryFooter.
|
| ModuleHeader |
Class to contain module specific information
which will be stored at the end of a binary
data file, just before the BinaryFooter.
|
| ModuleNameObject |
Object which holds the type and name of a PAMGUARD module
and can read and or write it from file.
|
| ModuleSettingsObject | |
| PackedBinaryObject |