Closed kirbyj closed 2 years ago
Hi @kirbyj - the var conColors is correctly updated for each trackName. The bug is a feel lines later in https://github.com/IPS-LMU/EMU-webApp/blob/e3758baa8ae4c329a0ab0f43552488de0dbfa992/src/app/components/ssff-canvas.component.ts#L200-L201
The fix is: this.ctx.strokeStyle = contColors.colors[contourNr]; this.ctx.fillStyle = contColors.colors[contourNr];
I integrated @samgregory's fix into master and will make a new release this week.
I just released this fix with v1.4.0. Please feel free to re-open the issue if it doesn’t work as intended.
Not sure if the fix for #287 caused this (though I can't see how) or if it is expected behavior.
Consider the following
signalCanvases
ordering:Is it possible to assign each of these F0 tracks an arbitrary color? The following does not work:
All three contours appear as
rgb(0,255,0)
, i.e. the first specification in thecontourColors
array.Assigning all contours to the same
signalCanvas
does not work either:which results in both
praatF0
andksvF0
being displayed in blue andeggF0
displayed in (default) red. Adding a specification foreggF0
results in it too being displayed in the whatever the first"colors"
specification in thecontourColors
array happens to be.Why isn't
var contColors
getting updated for eachtrackName
?