# Default color for analyzer decoding

**URL:** <https://discuss.saleae.com/t/default-color-for-analyzer-decoding/703>\
**Category:** Logic 2 Software\
**Created:** [August 23, 2020, 9:38pm UTC](https://discuss.saleae.com/t/default-color-for-analyzer-decoding/703 "2020-08-23T21:38:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Adrian](https://avatars.discourse-cdn.com/v4/letter/a/82dd89/32.png) [@Adrian](https://discuss.saleae.com/u/Adrian)\
**Post date:** [August 23, 2020, 9:38pm UTC](https://discuss.saleae.com/t/default-color-for-analyzer-decoding/703/1 "2020-08-23T21:38:20Z")

</div>

First, congrats on making the analyzer outputs much easier to read when zoomed out. Major enhancement.

first a request: Could you avoid truncating the analyzer result with “…” unless it is too long to fit into the bar? I have a lot of packets that are long enough to get truncated but that would fit on the bar if not for the truncation

And an easy improvement:  
Could you make the default color of a new analyzer match the wire color?

---

<div class="post-metadata">

**Author:** ![P.Jaquiery](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/p.jaquiery/32/289_2.png) [@P.Jaquiery](https://discuss.saleae.com/u/P.Jaquiery)\
**Post date:** [August 24, 2020, 12:44am UTC](https://discuss.saleae.com/t/default-color-for-analyzer-decoding/703/2 "2020-08-24T00:44:50Z")

</div>

> [@Adrian](#):
>
> Could you avoid truncating the analyzer result with “…” unless it is too long to fit into the bar? I have a lot of packets that are long enough to get truncated but that would fit on the bar if not for the truncation

See [Declutter and fill analyzer output - Logic 2 - Ideas and Feature Requests - Saleae](https://ideas.saleae.com/b/feature-requests/declutter-and-fill-analyzer-output/).

I nag Saleae on this topic fairly regularly and they are about due another nag. It gives me pain every day I use the analyser!

---

<div class="post-metadata">

**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\
**Post date:** [August 24, 2020, 9:20pm UTC](https://discuss.saleae.com/t/default-color-for-analyzer-decoding/703/3 "2020-08-24T21:20:34Z")

</div>

Thanks for the reminder @P.Jaquiery! We’ll keep an eye on this feature request for now. Unfortunately, it’s not on the immediate roadmap to fix. I just pinged our team about this.

@Adrian Would you mind adding your vote, or any comments you have below? We would like to continue monitoring user need for this to help with prioritization. I agree this should be addressed eventually - just a matter of where this would fit into our roadmap.

> **[Declutter and fill analyzer output - Logic 2 - Ideas and Feature Requests -...](https://ideas.saleae.com/b/feature-requests/declutter-and-fill-analyzer-output/)**
>
> At present (2.2.8) analyzer output (Async serial at least) text in bubbles and the terminal quote spaces which clutters the output making it harder to read. In the terminal \\r\\n is shown as text instead of causing a line break. Combined these make...

As for your improvement idea:

> Could you make the default color of a new analyzer match the wire color?

Could you post that idea to the link below? In your idea post, let us know how you’d like us to handle colors for multi-channel analyzers as well. For example, when adding a SPI analyzer, would you prefer 4 separate colors for each data channel (MOSI, MISO, CLK, EN)? We opted to keep the colors consistent for all analyzer data channels, hence keeping it separate from the wire colors.  
[https://ideas.saleae.com/b/feature-requests/](https://ideas.saleae.com/b/feature-requests/)

---

<div class="post-metadata">

**Author:** ![P.Jaquiery](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/p.jaquiery/32/289_2.png) [@P.Jaquiery](https://discuss.saleae.com/u/P.Jaquiery)\
**Post date:** [August 24, 2020, 9:34pm UTC](https://discuss.saleae.com/t/default-color-for-analyzer-decoding/703/4 "2020-08-24T21:34:35Z")

</div>

Thanks @timreyes. The “nag” comment was somewhat tongue in cheek, but the “pain every day” comment is real. From the outside it seems like an easy fix and would make at least a couple of customers very happy. But I understand the need for focus and bang for buck.

It may be a bigger issue for me than many people because I run multiple async serial channels at 912600 Baud as diagnostic output. I also run a fairly chatty HLA looking at I2C transactions. Both generate bursts of several hundred characters and trying to read those through a 50 character window by scrolling the trace is a significant pain!