Releases: bengeisler/TcLog
Releases Β· bengeisler/TcLog
v0.5.0: Changed library namespace to work with 4024.55
v0.4.0: Buffer messages until time information is valid
- Log messages get buffered until time information is available. This fixes #17. Filenames now include always the correct timestamp instead of point zero of unix time when logging in the first cpu cycles.
TcLogCore
exposes theTimeInfoReady
property to indicate when the time information is available. This can be used have only valid timestamps within in the log files. It is a choice, though: either log from the first cycle on, risking to have an invalid timestamp for the message, or throwing away the first cycles and have only valid timestamps.
v0.3.1: Bugfix
Fixes a bug (#14) where some data types were not correctly converted to STRING
with AppendVariable
or AppendAny
.
v0.3.0
- Updated to Zeugwerk naming conventions -> results in changed API namings
- Fixed a bug when no newline was added after messages with more than 254 chars that get logged to the file system
v0.2.2 : Performance upgrade
- New implementation of the file system persistence mechanism allows for much faster persistence. When logging less than 100 messages per cycle, the persistence mechanism takes
1 to 1.5 * # consecutive logging cycles
cylces to persist. Previously, it took# of logs per cycle * # of consecutive cycles * 4 + 4
. - Exposed the properties of TcLog and TcLogCore in debug view.
v0.2.1 : Bugfix
Fixes a bug that does not close files opened for writing when logging too many messages in too many consecutive cycles.