Skip to content

Conversation

@akwasniewski
Copy link
Contributor

Description

In #3742 I accidentally broke ripple effect, it starts from point of previous click instead of current (first one starts from the middle).

Diagnosis and cure

This is because I added a call to setPressed in canBegin, which activates the effect before it knows where to start. I added those to make sure setPressed is called somewhere, but after some testing I think it is not necessary.

Test plan

@akwasniewski akwasniewski merged commit 24c4b8e into main Oct 30, 2025
4 checks passed
@akwasniewski akwasniewski deleted the @akwasniewski/fix-ripple branch October 30, 2025 12:54
j-piasecki pushed a commit that referenced this pull request Nov 3, 2025
## Description

In #3742 I accidentally broke ripple effect, it starts from point of
previous click instead of current (first one starts from the middle).

# Diagnosis and cure

This is because I added a call to `setPressed` in `canBegin`, which
activates the effect before it knows where to start. I added those to
make sure `setPressed` is called somewhere, but after some testing I
think it is not necessary.

## Test plan

<!--
Describe how did you test this change here.
-->
j-piasecki pushed a commit that referenced this pull request Nov 20, 2025
## Description

In #3742 I accidentally broke ripple effect, it starts from point of
previous click instead of current (first one starts from the middle).

# Diagnosis and cure

This is because I added a call to `setPressed` in `canBegin`, which
activates the effect before it knows where to start. I added those to
make sure `setPressed` is called somewhere, but after some testing I
think it is not necessary.

## Test plan

<!--
Describe how did you test this change here.
-->
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