Skip to content

Logic channel color sequencing#119

Open
jgartrel wants to merge 3 commits into
sigrokproject:masterfrom
jgartrel:signal-color-sequence
Open

Logic channel color sequencing#119
jgartrel wants to merge 3 commits into
sigrokproject:masterfrom
jgartrel:signal-color-sequence

Conversation

@jgartrel
Copy link
Copy Markdown

I humbly beseech the maintainers that be, that they might accept this pull request. I know this might seem pedantic, however, most manufacturers of ribbon cable in the last 20 years start with brown, red ... with black next to white at the other side of the cable (for 10 wire, or 40 wire ribbon cable).

This pull request adds an option to the view settings to change the color offset for the logical channels. This allows a user to set the first color used for channels to be brown (or some other color) by default (instead of black)

Setting a value of "1" for the "Logic color offset" assigns brown as the color for channel 0, red as channel 1, etc... This has the following benefits:

  1. It better matches the most common manufacturing sequencing for colored ribbon cables.
  2. This works better with the cheapest available logic analyzers. These are very common and the GND signals are placed in positions 9 and 10. If position 10 was black that would equate to the GND return for most of these cheap analyzers.

The default for the color offset is: "0", allowing for the traditional look of pulseview to remain unchanged and work well with the Saleae logic analyzers that use black for channel 0.

I did my best with the translations for German, Spanish, Japanese, and Chinese. Those will certainly need a review.

@jgartrel jgartrel changed the title Signal color sequence Logical channel color sequencing Apr 26, 2026
@jgartrel jgartrel changed the title Logical channel color sequencing Logic channel color sequencing Apr 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant