-
-
Notifications
You must be signed in to change notification settings - Fork 877
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[BUG] Polyline with border ignores color in V4 #1510
Comments
Thanks for reporting. It's reproducible. Will investigate a fix. |
Hmm, maybe I messed up back tracing through commits then. |
I haven't got a lot of time to dig into it just atm, but I suspect it may be related to batching code, eg around c4b6680 and if I revert to a previous commit to that it all works. Maybe it's trying to batch forgetting about the separate layers when having a border or something. |
I think the main problem is possibly the ordering of the paints is wrong. We want to draw the main path/paint after the borders, so I think that may be an easy fix if it comes to it..There's something a little different with the filterPaint/path I'm confused about, but I'm not entirely sure how that works... Maybe we need to clarify the logic and reasons...we have
Whats 3 for, is it for opacity on lines that have a border color or something ? If someone needs a super quick fix, you could try swapping the order of the paints in polylinelayer.dart, but it would be nice before we do a change to know that its either a) the same as previous, or b) its different because of a fix (so need to double check lines with opacity and things like that). |
What is the bug?
When setting a border color on a polyline the color property gets ignored and the polyline is drawn with a black color.
How can we reproduce it?
Set the color property and the border color property on a polyline.
Do you have a potential solution?
I may be wrong but it looks like the wrong color value is set in filterPaint in the polyline_layer class.
Platforms
All flutter platforms
Severity
Minimum: Allows normal functioning
The text was updated successfully, but these errors were encountered: