FreeEMS Issues - OLV
View Issue Details
0000298OLVGeneral Featurespublic2011-10-17 08:422011-12-02 12:39
Fred 
BenFenner 
normalminorN/A
assignedopen 
AllAllAll
0.0.1-SNAPSHOT 
0.0.7 
0000298: Add Support For Arbitrary Marks With Meta Data
Add front end support for things like log marking (hitting space bar in tuning app while logging), reset occurrences as detected by discontinuity of continuously incremented unsigned vars, freeems async error packets, stray other log packets and return packets due to interruptions by other software, programmable feature detection (occurrence of excess delta from one record to the next on a particular field value) etc etc etc.

Each thing should get a unique colour (use the same mechanism as the traces) and some mouse and/or keyboard action should expose what they mean somewhere. Perhaps just display in a console style area below and highlight (double or triple width/2 or 3 pixels instead of 1) the line in the graphing area.

We need to have a chat about this to hash out the mechanics of it and how to propogate the data through to the UI from the source, whatever the source is. Perhaps something like each record holder having a slot for a list of meta data objects at that point (just in case more than one is on the same one at the same time...) and read the presence of them when going through the data to display it.

Required for 0000348 to be properly displayed.
No tags attached.
related to 0000348closed Fred Add Reset Detection To FreeEMS Bin 

Notes
(0000491)
Fred   
2011-10-27 13:49   
Note, these should almost certainly display as a solid line from top to bottom of graph area crossing all divisions.
(0000832)
Fred   
2011-12-02 12:37   
I like the way the 1/2 markers in saleae look, with the dashed line and the flag at the top. This could work well for us, or something similar. Just noting it down while it's on my mind :-)
(0000833)
Fred   
2011-12-02 12:39   
Dashed is necessary in an LA app, not so much in ours. But perhaps we could have solid and dashed with different dash lengths, colours and thicknesses configured for each type, such that serious things get a big fat red line and informational stuff gets a faint or even semi transparent dashed line of a single pixel. ETC! :-)