-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
Bar chart with time delay displayed with the same color #26041
Comments
When you say "before 3.0.1" do you mean 3.0.0 did not have this problem? What's the latest official release you've found that has the prior, desired behavior? |
we were using the 2.1.0 version, and now we have upgraded to 3.0.1 @sfirke |
This was a side-effect of another fix. They should have the same color but we need to add a differentiator between normal and offset bars similar to what the line chart does by using dashed lines. I can take a look at this problem. |
I also have the same question. For line charts, using dashed lines to differentiate offset lines for the same indicator is possible. But for bar charts, I think maintaining the previous logic might seem more reasonable. I prefer to have them display different colors, especially when we are only drawing a single indicator and want to compare the data from a week ago. Showing different colors would be very convenient for observation. But when we are drawing multiple indicators and want to compare the data from a week ago for all of them, using the same color but different styles should be more convenient for observation. |
In line charts, it makes the time-delay lines dotted instead of solid but in the same color. This is pretty nice, however, if you have multiple time-delay lines, they will all look identical. |
Thank you all for the discussion.
My concerns here would be:
You're correct. We would be need have a number of patterns (dashed, solid, dotted, etc) equal to the number of supported offsets to differentiate the metrics. Tagging @kasiazjc to bring the designer's perspective to the discussion. |
Any update on this? We recently switched over to Superset for analytics and I've been getting some complaints about this exact issue. |
Hi @eschutho with our use-case it doesn't seem to change anything (Superset 3.0.3) : |
Same for me. We are on 3.0.1 |
Same for me. Version 3.1.3. Any update on whether the issue will be fixed? |
We're currently looking into some improvements here. Perhaps by the 4.2 release. |
Hello, I'm checking in.When is the release of version 4.2 scheduled? |
It's not clear if there will be a 4.2... though there may well be. We're beginning to focus on 5.0, so 4.x.x releases will be as-needed for patches, or as-wanted by a volunteer release manager (e.g. @sadpandajoe). You can join us on slack in the various release channels if you want to keep an ear out or get involved in the process. |
Before the 3.0.1 :
After the 3.0.1 :
How to reproduce the bug
Environment
3.0.1
The text was updated successfully, but these errors were encountered: