I was not aware of the multiple strings feature of .put for annotations.  
That's pretty handy.  I haven't seen that feature in other logic analyzers 
(closest was letting the user manually chose terse or verbose).  It provides a 
nice balance between novices for a particular protocol and advanced users.

Between Soeren and you, I think I'll tackle adding variable strings.  Please 
ignore my "Shorted the displayed decode text" submission.  I'll re-work it.

Is there deeper documentation for the various OUTPUT_ types (annotations, 
binary, meta, etc)?  I reviewed
http://sigrok.org/wiki/Protocol_decoder_API and 
http://sigrok.org/wiki/Protocol_decoder_output and found some info but didn't 
see the format for annotations defined (i.e. the list of strings wasn't 
mentioned).  Is the Wiki the full documentation but it is still a 
work-in-progress or is the Wiki a starter guide and there is more documentation 
elsewhere.  If all else fails, I can go read the C code directly.  :-)

-Chris

----------------------------------------
> Date: Wed, 24 Aug 2016 11:37:52 +0200
> From: [email protected]
> To: [email protected]
> CC: [email protected]
> Subject: Re: [sigrok-devel] Substantial improvement to decoding of MIDI 
> messages
>
> Hi,
>
> On Tue, Aug 23, 2016 at 10:20:56PM -0700, Chris Dreher wrote:
>> I was also thinking that the decoding text was getting too long, especially 
>> for users who use the GUI.  I'll shorten the text by using abbreviations, 
>> but only for common abbreviations that someone with only moderate experience 
>> with a logic analyzer or MIDI would likely know.  I reviewed some manuals 
>> for MIDI devices as a guideline.  Some examples:
>>
>> ch = Channels
>> SysEx = System Exclusive
>> RPN = Registered Parameter Number
>> NRPN = Non-Registered Parameter Number
>>
>> I will not use abbreviations for less common phrases.  For example, I've 
>> seen "CC" used for "Control Change" but only in audio chip datasheets.  CC 
>> seems too technical.
>
> Sounds good. Note that the PD should emit all annotations lengths/versions,
> frontends can use that to show different annotation strings at different
> zoom levels.
>
> Example:
>
> ['Registered Parameter Number', 'Reg Param Num', 'RPN', 'R']
>
> and such...
>
>
> Uwe.
> --
> http://hermann-uwe.de | http://randomprojects.org | http://sigrok.org
                                          
------------------------------------------------------------------------------
_______________________________________________
sigrok-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Reply via email to