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

[Bug Report] PPSSPP System keyboard has "&" shown as "&&" #19477

Closed
5 tasks done
Abbanon opened this issue Sep 19, 2024 · 2 comments · Fixed by #19482
Closed
5 tasks done

[Bug Report] PPSSPP System keyboard has "&" shown as "&&" #19477

Abbanon opened this issue Sep 19, 2024 · 2 comments · Fixed by #19482
Milestone

Comments

@Abbanon
Copy link
Contributor

Abbanon commented Sep 19, 2024

Game or games this happens in

n/a

What area of the game / PPSSPP

Using PPSSPP's system keyboard menu shows that & appears as &&
This does not impact any game, the issue is only within the system keyboard menu itself.
I have narrowed down the cause to be from Dev build 1.17.1-640-g7547126a7d.
The issue is not present in the previous Dev build of 1.17.1-638-g1f7310d4cf.

ULJM05500_00000

What should happen

& should appear as &, instead of &&

Logs

No response

Platform

Windows

Mobile device model or graphics card (GPU)

GTX 1660 Super

PPSSPP version affected

1.17.1-640-g7547126a7d, and all builds afterwards

Last working version

1.17.1-638-g1f7310d4cf

Graphics backend (3D API)

Vulkan

Checklist

  • Test in the latest git build in case it's already fixed.
  • Search for other reports of the same issue.
  • Try resetting settings or older versions and include if the issue is related.
  • Try without any cheats and without loading any save states.
  • Include logs or screenshots of issue.
@sum2012
Copy link
Collaborator

sum2012 commented Sep 21, 2024

That mean #19218

@hrydgard
Copy link
Owner

Oops, silly mistake. Will fix.

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 a pull request may close this issue.

3 participants