Skip to content
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

Open
lthms opened this issue Sep 6, 2016 · 5 comments
Open

Deal with transparency #32

lthms opened this issue Sep 6, 2016 · 5 comments
Labels
Milestone

Comments

@lthms
Copy link
Contributor

lthms commented Sep 6, 2016

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.

@lthms lthms added the question label Sep 6, 2016
@Nemikolh
Copy link
Contributor

Nemikolh commented Sep 6, 2016

Thanks for opening this issue! When we discussed that point with @Azamung the idea was to convert this pixel into a totally transparent one.

@lthms
Copy link
Contributor Author

lthms commented Sep 6, 2016

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)

@Nemikolh
Copy link
Contributor

Nemikolh commented Sep 6, 2016

Yes! That's idea. We were thinking of either detecting that automatically or provide a pen that would allow to select the color.

@lthms
Copy link
Contributor Author

lthms commented Sep 6, 2016

Probably we can imagine the following:

  1. A way to set by hand a hexa color code (an input)
  2. A pen to set this input to a selected pixel value
  3. And maybe later a way to detect it automatically (but it should be afterwards) and set the value of the input with the result

This is three steps we can do one by one. What do you think?

@Nemikolh
Copy link
Contributor

Nemikolh commented Sep 6, 2016 via email

@Nemikolh Nemikolh added this to the dilia-r14 milestone Sep 6, 2016
@Nemikolh Nemikolh modified the milestones: dilia-r16, dilia-r14 Feb 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants