-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
-colorprop- crashes treemap if colorby is the second layer #13
Comments
Will check but use of such syntax where the lowest tier variable is determining the color is not advisable. All rows are unique in the If you switch the syntax to:
the output is more reasonable. |
I tried this and I am puzzled:
In my understanding of colorby() all three values of model_nr should have the same color across the brands. But they don't... |
and in my real world example it leads me to the question whether I could also be able to control for the first layer colors if I want the second layer categories across the first layer to have the same color... My example is that I have organizational units that contribute to different subjects and different units may contribute to one subject... like the example above would be:
|
will check tonight. |
Currently, the colors are inherited from the topmost layer. For color variations within layers such that 2nd or 3rd layer categories have the same color implies re-writing the base color functions. I can think about in future releases which might take a while. |
-colorprop- crashes treemap if colorby is defined as the second or third layer:
This code works:
This treemap-command crashes with an unintuitive error:
The text was updated successfully, but these errors were encountered: