Then the resulting map will not open correctly in the viewer, with console errors "Uncaught TypeError: contColorMap.getColor(...) is null" from SummaryHeatMapDisplay.js and DetailHeatMapDisplay.js
Since standard color names work fine for chmNewColorMap(), users might reasonably expect them to work for cuts_color. So this seems like a bug. At the very least we should give the user an error so they can use the hexadecimal code.
I'm not sure if this issue is caused by the viewer project's javascript code, java code, or somewhere in the R package.
When using the
cuts_color
option tochmNewDataLayer()
, if a standard color name is used, as in:Then the resulting map will not open correctly in the viewer, with console errors "Uncaught TypeError: contColorMap.getColor(...) is null" from SummaryHeatMapDisplay.js and DetailHeatMapDisplay.js
However using the hexidecimal code works fine:
Since standard color names work fine for
chmNewColorMap()
, users might reasonably expect them to work forcuts_color
. So this seems like a bug. At the very least we should give the user an error so they can use the hexadecimal code.I'm not sure if this issue is caused by the viewer project's javascript code, java code, or somewhere in the R package.