Dangerous Prototypes

The OLS client supports the annotating of data to present additional information along with the signal data. For example, many of the decoding tools use annotations to represent the decoded data. For the new signal display component, I'd like to implement a new style of annotation rendering that is both useable regarding its presentation of data, as well looks good.

I'd like to invite as many people as possible to cast their vote on which annotation style rendering they prefer. Screenshots are added below to give you an idea on how the current styles look.

[attachment=1]
[attachment=0]

If you've got new ideas on how to represent annotations, please post them in this topic! All ideas are welcome!

---

I vote for 'Style 2' - it is more eye clear what is the scope of the anotation, and actual signal in background

I prefer style 2 as well, but perhaps the signal could be just slightly more visible in the background..

Hi I would prefer Style 2 with a ToggleButton in the toolbar that switches the layers painted on top.
The default should be as shown in style 2, but when you click the button, the signal is painted in front with the dimmed Annotation in shown in the back.

Eberhard

The poll is at the top of the post; the images are just to clarify each of the styles...

I prefer style 2, thanks

i like style 2, the color of the lines in between the markers could be a little brighter, maybe a different color

I like both. But I reckon style 1 communicates more clearly because it shows the highs and lows bright and clear while it displays the annotation without being too disturbing! :) I like it Jan! :) Thanks.M

[quote author="jone"]I prefer style 2 as well, but perhaps the signal could be just slightly more visible in the background..[/quote]
I'd second that.

Style 2, but make the signal more visible, maybe if the mouse hovers over it or something.

Style 2 absolutely. It is instantly recognizable and saves brain power for doing the payload thinking. The less cognitive stressors the better.

Anyway, this project looks pretty good and I will be trying it out shortly.

How about a combination of #1 and #2? Keep the lines from the measuring points of #2 but with the bright tops and bottoms of the signal of #1? The best of both worlds.

Seems I am late to this, but can we control the width of the line? Style 2(guided) seems to show 2 much thicker lines than the rest of the sample, which I presume is a quicker logic change than the resolution of the image. If we can control the width of the line then such situations would be more rare. But I am not familiar with how difficult such an option would be, so I don't have much of a understanding if such an option were possible. :P

Awesome nonetheless! Thank you a bunch Jawi for continuing to develop GUI's! :D

[quote author="hak8or"]Seems I am late to this, but can we control the width of the line? Style 2(guided) seems to show 2 much thicker lines than the rest of the sample, which I presume is a quicker logic change than the resolution of the image. If we can control the width of the line then such situations would be more rare. But I am not familiar with how difficult such an option would be, so I don't have much of a understanding if such an option were possible. :P[/quote]

Sorry, I'm having hard times to understand your post. Control the width of which lines? The sample data, or the annotation guides?

Since it's software, why not implementing both (or even more) method and leave the decision to the user by offering a preference menu? Add vars for colour, transparency, line width and text size and everyone can set it up in a way it work best for a particular task.

Sorry for the confusion, the thickness of the line representing sample data.