-
Notifications
You must be signed in to change notification settings - Fork 57
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
Update PanelSpriteButton.json #980
Conversation
Thank you for submitting an extension update. Did you consider applying an effect on the button after disabling it? |
No, I did not add an effect. I think people usually have a disabled button sprite/image. |
As the other states are already in images, it's a good to have this new state as an image too, to be consistent. |
Adding a new state means that every assets from the store must be updated with an image for this state. Also, I think it's not very practical to use an image when, for most buttons, it will just be a grey-ish version of the idle state. Effects performance is another matter. There is no need to evaluate a shader each frame on a still image. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please, extension team members, do not merge this PR.
I think we should start thinking about having different variations of buttons :) |
What did you suggest, kept the object in this version, and duplicate the a new object with improvment on a disabled state?
I agree.
I think the shaders from effects are calculated at every frame, I'm not sure. |
This PR should have the 'Extension updated' tag |
As per the thread above, the reviewers rejected these changes. Closing PR now. |
Add disabled state.
A disabled state is visible when the interactions are deactivated.