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

[PowerRename] Can't use ALT GR shortcuts for special characters on AZERTY layout #14099

Closed
1 task done
JusteThom opened this issue Oct 29, 2021 · 17 comments
Closed
1 task done
Labels
Issue-Bug Something isn't working Product-PowerRename Refers to the PowerRename PowerToy Resolution-Fix Committed Fix is checked in, but it might be 3-4 weeks until a release.

Comments

@JusteThom
Copy link

JusteThom commented Oct 29, 2021

Microsoft PowerToys version

0.49.0

Running as admin

  • Yes

Area(s) with issue?

PowerRename

Steps to reproduce

On AZERTY keyboard layout, we can't type special characters with ALT GR key like ALT GR + 8 for "\" caracter.

✔️ Expected Behavior

For the shortcut to work

❌ Actual Behavior

Don't do anything

Other Software

No response

@JusteThom JusteThom added Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Oct 29, 2021
@franky920920 franky920920 added the Product-PowerRename Refers to the PowerRename PowerToy label Oct 30, 2021
@stefansjfw
Copy link
Collaborator

This is external WinUI + Xaml islands issue, as AutoSuggestBox UI element works fine with AltGr input on packaged apps, but doesn't accept AltGr input when hosted with Xaml islands.

Created bug ticket in WinUi repo:
microsoft/microsoft-ui-xaml#6217

@stefansjfw stefansjfw added External Dependency-WinUI 3 Dependency on WinUI External Dependency This bug or feature isn't resolved, but it's following an external work item. labels Nov 2, 2021
@niels9001 niels9001 reopened this Nov 2, 2021
@niels9001 niels9001 added the Status-Blocked We can't make progress due to a dependency or issue label Nov 2, 2021
@crutkas crutkas removed the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Nov 12, 2021
@tevey
Copy link

tevey commented Nov 15, 2021

I use Swedish qwerty keyboard layout and can't type anything at all in the fields in powerrenamer anymore, is this the same issue?

@stefansjfw
Copy link
Collaborator

@tevey I would say so.

@anttin2020
Copy link

anttin2020 commented Nov 25, 2021

where can I get old version back? This new version is unusable, first because of that ALTGR bug but also because the file name Original field width cannot be adjusted so there is no way to see the original filenames in full to see that the rename actually is correct.

Nevermind, I installed the original SmartRenamer, it works as expected.

@franky920920
Copy link
Contributor

@anttin2020
Copy link

hmm...I downloaded 0.49.1 and tried to install it but it said I already have newer version installed and update check says it is up to date (0.49.1)

@franky920920
Copy link
Contributor

@anttin2020 v0.49.1 is the latest version. Which version do you want to roll back?
You'll have to uninstall the newer version first before installing an older version.

@anttin2020
Copy link

Ah sorry, I misunderstood, I thought there was new release that might fix this problem :)
I hope to see it fixed soon, until then I'll use the SmartRename.

@theme1256
Copy link

I'm also having this issue.
I'm using a nordic QWERTY and a danish QWERTY keyboard on danish systems and on none of them AltGr shortcuts works.

@3PSY0N
Copy link

3PSY0N commented Dec 9, 2021

Same issue here, i can't use Alt Gr + other key combination in Power Rename for regular expressions.
I use AZERTY keyboard with French layout. And PowerToys version is v0.51.1
Thank you

@anttin2020
Copy link

anttin2020 commented Dec 9, 2021

So there are two updates after the previous reports of this serious keyboard problem and nothing is still done!
PowerRename is still totally unusable as no AltGr keys cannot be used.
If I was developing this kind of globally important tool, I would fix this kind of almost fatal bugs first, then continue with other things.

@stefansjfw
Copy link
Collaborator

Fix is on it's way

@stefansjfw stefansjfw added Status-In progress This issue or work-item is under development and removed External Dependency This bug or feature isn't resolved, but it's following an external work item. External Dependency-WinUI 3 Dependency on WinUI Status-Blocked We can't make progress due to a dependency or issue labels Dec 9, 2021
@stefansjfw stefansjfw added Resolution-Fix Committed Fix is checked in, but it might be 3-4 weeks until a release. and removed Status-In progress This issue or work-item is under development labels Dec 13, 2021
@sba923
Copy link

sba923 commented Dec 23, 2021

I confirm FWIW that the issue is still present in 0.51.1

@stefansjfw
Copy link
Collaborator

I confirm FWIW that the issue is still present in 0.51.1

Fix is merged and will be included in next release

@crutkas
Copy link
Member

crutkas commented Jan 6, 2022

This is fixed in 0.53, get it at https://aka.ms/installPowerToys

@crutkas crutkas closed this as completed Jan 6, 2022
@sba923
Copy link

sba923 commented Jan 7, 2022

This is fixed in 0.53, get it at https://aka.ms/installPowerToys

Confirmed.

I'm still astonished that in 2021 people can still write code that gets this (or handling non-ASCII characters, for that matter) wrong. Maybe I'll look at the fix to understand 🙃.

@crutkas
Copy link
Member

crutkas commented Jan 18, 2022

@sba923 when dealing with routing of stuff through different UX frameworks and when samples are incorrect, bugs happen. We've routed the feedback to the team who's sample was incorrect and caused our underlying issue.

We thank everyone for helping out alerting us to the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug Something isn't working Product-PowerRename Refers to the PowerRename PowerToy Resolution-Fix Committed Fix is checked in, but it might be 3-4 weeks until a release.
Projects
None yet
Development

No branches or pull requests

10 participants