BUG: DXCluster timestamp sorting 0000Z
Posted: 29 Nov 2020, 00:24
Hello,
Log4om Version 2.10.0.0
Found a bug wen sorting of DXCluster messages originated before and after 0000Z
LOG4OM simply sorts numbers from small to large, but 0001Z is later thus larger then 2359Z, maybe also consider the (system) date when sorting ?
Log4om Version 2.10.0.0
Found a bug wen sorting of DXCluster messages originated before and after 0000Z
LOG4OM simply sorts numbers from small to large, but 0001Z is later thus larger then 2359Z, maybe also consider the (system) date when sorting ?
- cluster-time-sorting.png (11.97 KiB) Viewed 2044 times