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

scatter3d with different marker.size enables transparency #4681

Open
archmoj opened this issue Mar 25, 2020 · 5 comments
Open

scatter3d with different marker.size enables transparency #4681

archmoj opened this issue Mar 25, 2020 · 5 comments

Comments

@archmoj
Copy link
Collaborator

@archmoj archmoj commented Mar 25, 2020

Transparency appears to be enabled by having different marker.sizes!
View from our docs:

Screenshot from 2020-03-25 09-42-36

@archmoj archmoj added the type: bug label Mar 25, 2020
@alexcjohnson
Copy link
Contributor

@alexcjohnson alexcjohnson commented Mar 25, 2020

For regular scatter this is intentional - bubble charts, which we define to be any chart with marker size set to an array - get some default transparency because overlap is common with large markers. I imagine we simply inherited that same behavior in scatter3d, so I might consider this a documentation issue rather than a bug.

@archmoj
Copy link
Collaborator Author

@archmoj archmoj commented Mar 25, 2020

@alexcjohnson thanks for the clarification.
This is still rather confusing.
With different marker sizes, how one could force a graph not to have any transparency?

@archmoj
Copy link
Collaborator Author

@archmoj archmoj commented Mar 25, 2020

@alexcjohnson
Copy link
Contributor

@alexcjohnson alexcjohnson commented Mar 25, 2020

marker.opacity = 1 ?

@archmoj
Copy link
Collaborator Author

@archmoj archmoj commented Mar 25, 2020

marker.opacity = 1 ?

That works for me!

@archmoj archmoj removed the type: bug label Mar 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.