-
Notifications
You must be signed in to change notification settings - Fork 2
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
Deal with transparency #32
Comments
Thanks for opening this issue! When we discussed that point with @Azamung the idea was to convert this pixel into a totally transparent one. |
Oh, that would work. But this means we modify the chipset before saving it? (It is not a problem, I just want to be sure I understood correctly) |
Yes! That's idea. We were thinking of either detecting that automatically or provide a pen that would allow to select the color. |
Probably we can imagine the following:
This is three steps we can do one by one. What do you think? |
I like this incremental approach. I think we should implement it that way.
|
In a chipset, one color is often used as the “transparency color” that is it is not supposed to be displayed in the map.
One way to improve the chipset upload and management is to deal with this transparency color. I suspect it is not an easy change as it also impacts the renderer.
The text was updated successfully, but these errors were encountered: