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

A bug with the environment's coloring persists. #319

Closed
wants to merge 2 commits into from

Conversation

MaximeScope
Copy link
Contributor

When a environment is enabled and further disabled, changing the color property while keeping the environments disabled indeed updates the color for every atom, although a ghost of the previous environment's coloring remains on top of the current coloring. If the environment is then re-enabled and further re-disabled by the user, the "ghost" will disappear. But, changing the color property again will result in the same problem.

I tried to fix this issue today but I can't understand where the problem comes from. I need help @Luthaf

Although, I found another bug wwhere the color bar appeared when selecting a coloring per element again and fixed it!

Fixed the bug where the color bar appeared when selecting a coloring per element again.
@ceriottm
Copy link
Contributor

ceriottm commented Dec 9, 2023

I also noticed this problem, but have no clear idea how to fix it

@Luthaf Luthaf mentioned this pull request Dec 11, 2023
@Luthaf
Copy link
Contributor

Luthaf commented Dec 11, 2023

The issue was that we did not remove the GLModel from 3Dmol renderer when switching off the environments highlighting. It was not caught previously because both models had the same color anyway. This and the color bar re-appearing should be fixed by #322

@Luthaf Luthaf closed this Dec 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants