Page 1 of 1

Cell-value colors when increasing/decreasing Ign advance

Posted: Sat Apr 15, 2017 2:14 pm
by BigBlockMopar
In an Ignition timing table, when a cell's advance number is increased, the number turns Blue.
With a lower (safer) advance number, it turns Red.
Thinking; Red usually means Warning/Danger, I would expect entering a higher (more) advance (which could lead to detonation) should be shown as Red, not Blue (safe).

Probably nitpicking but it bothered me that it would go against what one might expect.

Re: Cell-value colors when increasing/decreasing Ign advance

Posted: Sun Apr 16, 2017 1:09 pm
by samh
The red number in the green background means the new value in lower than the original number.
The blue number in the green back ground means the new value is larger than the original number.
The background will change color as the number gets larger or smaller.
When the gets large enough the background will change to red
When the number is small enough the background will change to blue
The background color shades range from blue - green - yellow - red.

Re: Cell-value colors when increasing/decreasing Ign advance

Posted: Sun Apr 16, 2017 1:58 pm
by BigBlockMopar
I understand the principle, and as for the background colors, they are fine as they are... as in MORE advance, the redder they become.
I know the number's color not really ment as a 'warning' color, but it kinda struck me as odd that when adding MORE advance to the current value in a cell, the number turns blue. It goes against what the background colors do.

Re: Cell-value colors when increasing/decreasing Ign advance

Posted: Mon Apr 17, 2017 7:58 am
by LT401Vette
To TunerStudio a table is a table, it doesn't know an ignition table from a fuel table. So all have blue more, red less.
To change that we would need to add an optional ini extension to tell TS whether up or down is more likely a warning condition.

Re: Cell-value colors when increasing/decreasing Ign advance

Posted: Mon Apr 17, 2017 11:54 am
by BigBlockMopar
I imagined something like this that TS uses 1 way of dealing with tables and its content.

Would be great if it was an 'easy fix' (if plenty more users agreed), but no need to spend much resources on.
I'm probably one of the few who noticed this (and felt it could use mentioning.) 8)