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

Nodes originally with color 0 don't update their color #463

Open
chiefcll opened this issue Dec 3, 2024 · 2 comments
Open

Nodes originally with color 0 don't update their color #463

chiefcll opened this issue Dec 3, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@chiefcll
Copy link
Contributor

chiefcll commented Dec 3, 2024

I have an element InViewPort and tried changing the color and it didn't update. I had to set strictBounds=false and then it updated the color. All the parent nodes are also inViewPort. It didn't update the color until I set the strictBounds to false

image
@chiefcll
Copy link
Contributor Author

chiefcll commented Dec 3, 2024

After some research it seems if the node is originally color 0 and you try to update it, it won't change. But if it has some color and you change it to a different value it will update.

@chiefcll chiefcll changed the title strictBounds preventing updates to nodes that are inViewPort Nodes originally with color 0 don't update their color Dec 3, 2024
@chiefcll chiefcll closed this as completed Dec 5, 2024
@chiefcll chiefcll reopened this Dec 5, 2024
@chiefcll
Copy link
Contributor Author

chiefcll commented Dec 5, 2024

OK - looks like the renderer doesn't update the isRenderable on the coreNode when the color changes. So with 0 the isRenderable is false and then when you change it it doesn't update isRenderable to true

@wouterlucas wouterlucas added the bug Something isn't working label Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants