Use gray for inferred rundown timings
This commit is contained in:
parent
61c3cbe885
commit
588c2a8e71
|
|
@ -59,7 +59,7 @@ const PREVIEW_SUCCESS: Color32 = Color32::from_rgb(115, 205, 150);
|
|||
const PREVIEW_AMBER: Color32 = Color32::from_rgb(235, 190, 95);
|
||||
const PREVIEW_GAP: Color32 = Color32::from_rgb(110, 200, 215);
|
||||
const PREVIEW_RED: Color32 = Color32::from_rgb(245, 125, 120);
|
||||
const PREVIEW_INFERRED: Color32 = Color32::from_rgb(185, 160, 245);
|
||||
const PREVIEW_INFERRED: Color32 = Color32::from_rgb(165, 172, 184);
|
||||
const COLUMN_FOCUS_PULSE_SECONDS: f64 = 1.8;
|
||||
|
||||
fn needs_information(d: &Diagnostic) -> bool {
|
||||
|
|
|
|||
|
|
@ -75,9 +75,9 @@ visually distinct from labels and ordinary actions; the active tab uses the stro
|
|||
diagnostics from the last analysis and gaps for context. Ignored rows can be restored using All rows.
|
||||
Notes attached to another event keep their own source row and identify their
|
||||
parent timer instead of duplicating it. Amber means unresolved, red means an
|
||||
error, gray means ignored, teal marks gaps, and purple timing values were inferred
|
||||
rather than read directly from the rundown. Start, end and duration are colored
|
||||
independently, so a row can show exactly which values were calculated. An overlap marks both the later
|
||||
error, dim gray means ignored, teal marks gaps, and medium-gray timing values were
|
||||
inferred rather than read directly from the rundown. Start, end and duration are
|
||||
colored independently, so a row can show exactly which values were calculated. An overlap marks both the later
|
||||
cue and its predecessor in red because either timing may need correction; each
|
||||
row's hover leads with the warning or error severity, code, source location,
|
||||
full explanation and a concrete way to resolve it. Timing inference is conveyed
|
||||
|
|
|
|||
Loading…
Reference in New Issue