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

Fade hold-for-menu button out completely on non-touch devices #26542

Merged
merged 1 commit into from Jan 18, 2024

Conversation

peppy
Copy link
Sponsor Member

@peppy peppy commented Jan 15, 2024

Supersedes #26128.
Addresses https://discord.com/channels/188630481301012481/188630652340404224/1187604735574954014

I re-PR'd this because the other attempt is a bit incorrect and fixing would be higher effort.

text.FadeInFromZero(500, Easing.OutQuint).Delay(1500).FadeOut(500, Easing.OutQuint);
touchActive = sessionStatics.GetBindable<bool>(Static.TouchInputActive);

if (touchActive.Value)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this intentionally checked only once ever?

It's a bit weird for me to first take out a config bindable to then only check it once...

Copy link
Sponsor Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's used in Update as well, to get the minimum alpha level. This one is just to decide how to animate, and there's not much point in checking beyond the initial load.

@bdach bdach self-requested a review January 18, 2024 10:00
@bdach bdach merged commit 2be989b into ppy:master Jan 18, 2024
15 of 17 checks passed
@peppy peppy deleted the non-touch-fade-button branch January 18, 2024 11:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants