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

Update PanelSpriteButton.json #980

Closed
wants to merge 1 commit into from
Closed

Conversation

gemmomoh
Copy link

Add disabled state.

A disabled state is visible when the interactions are deactivated.

image

@gemmomoh gemmomoh requested a review from a team as a code owner August 17, 2023 12:02
@D8H
Copy link
Contributor

D8H commented Aug 17, 2023

Thank you for submitting an extension update.

Did you consider applying an effect on the button after disabling it?

@gemmomoh
Copy link
Author

No, I did not add an effect. I think people usually have a disabled button sprite/image.

@Bouh
Copy link
Contributor

Bouh commented Aug 19, 2023

As the other states are already in images, it's a good to have this new state as an image too, to be consistent.
The effects are also rendered at each frame, which is a minor hit on the GPU, an additional cost that can be avoided.

@D8H
Copy link
Contributor

D8H commented Aug 19, 2023

As the other states are already in images, it's a good to have this new state as an image too, to be consistent. The effects are also rendered at each frame, which is a minor hit on the GPU, an additional cost that can be avoided.

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.

Copy link
Contributor

@D8H D8H left a 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.

@4ian
Copy link
Collaborator

4ian commented Aug 19, 2023

I think we should start thinking about having different variations of buttons :)

@Bouh
Copy link
Contributor

Bouh commented Aug 19, 2023

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?
It will duplicate the object buttons just for that difference...

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.

I agree.

Effects performance is another matter. There is no need to evaluate a shader each frame on a still image.

I think the shaders from effects are calculated at every frame, I'm not sure.
But if we can calculate the effect one time on the object its a wonderful solution.
Except the effects doesn't work on children objects in a EBO (Event Base Object) like I saw and shared on discord, so we can't use them for the moment to greyed a state.

@romw314
Copy link

romw314 commented Aug 24, 2023

This PR should have the 'Extension updated' tag

@arthuro555 arthuro555 added 🔄 Extension update An update for an existing extension 🔍 Reviewed extension An extension that is to be reviewed in great detail before merging. labels Sep 28, 2023
@arthuro555
Copy link
Member

As per the thread above, the reviewers rejected these changes. Closing PR now.

@arthuro555 arthuro555 added the ❌ Rejected A rejected extension label Dec 16, 2024
@arthuro555 arthuro555 closed this Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔄 Extension update An update for an existing extension ❌ Rejected A rejected extension 🔍 Reviewed extension An extension that is to be reviewed in great detail before merging.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants