8000 Fix trait selection requiring extra key press to update by ShaPhi7 · Pull Request #297 · pvpoke/pvpoke · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Fix trait selection requiring extra key press to update #297

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

Merged
merged 1 commit into from
May 26, 2025

Conversation

ShaPhi7
Copy link
Contributor
@ShaPhi7 ShaPhi7 commented Feb 16, 2025

Minor fix but it was annoying me :) To search by traits on the rankings screen...
Before the change:

  1. On the rankings screen (any format).
  2. Next to Search Pokemon, click (+) to Search Traits e.g. select "Bulky".
  3. Ok the Search Traits dialog.
  4. You now need to press a key with focus on the textbox to get it to update.

After the change:
Steps 1)-3), but now it updates automatically (no need for step 4).

Technical:
There are multiple poke-search's on the screen (some hidden).
We were grabbing all of them and triggering updates on all of them, so that by the time we ended up at submitSearchQuery, we had the wrong target, so applied the visual update to the wrong poke-search. To the user it appears that the screen didn't update automatically. Now, we will grab the poke-search that was clicked on, so that we always update visuals in the correct place.

Tested on both the ranking screen, and the team builder ("select alternatives") screen.

@ShaPhi7
Copy link
Contributor Author
ShaPhi7 commented Feb 16, 2025

@pvpoke a quick fix for you to review here please.

@pvpoke pvpoke merged commit 9608941 into pvpoke:master May 26, 2025
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.

2 participants
0