Suggestion for Quick accent

[guidobalde]

Description of the new feature / enhancement

I find the "Sort characters by usage frequency" very useful when writing, since in this way just hitting the activation character while selecting the character to accent, I can quickly select the correct character.
But the frequencies reset each time Windows starts.
I would propose a feature that allows the order to be maintained even after a restart and an additional manual reset of the order inside the settings.
Otherwise I would suggest a "fix in place" for certain special characters in a custom order, or a manual ordering of the characters.

Scenario when this would be used?

As a power user this would be useful, since the order of the special characters would not change every time that Windows starts.

Supporting information

No response

[rnikander]

Yeah, I want a manual ordering. What I really need is a predictable way to type a character. Having to look at the popup bar, to see if the frequency ordering has kicked in or not, is a disruption to fast touch-typing.

[maximedrouhin]

I have the same problem which annoys me very often, I was going to make this an issue but you beat me to it ^^

I think the issue name is not enough descriptive though, do you think you could name it more clearly with something like "Quick Accent - fix usage frequency resetting on reboot"? Hopefully that makes it more visible and it can get the attention it deserves!

[maximedrouhin]

Yeah, I want a manual ordering. What I really need is a predictable way to type a character. Having to look at the popup bar, to see if the frequency ordering has kicked in or not, is a disruption to fast touch-typing.

@rnikander If we want to compare the 2 possibilities:

• This issue is a relatively simple fix, it only requires making the usage frequencies persistent, so basically storing them into a file instead of a variable. And it would fix the problems of many users.
• The manual ordering you're talking about (Customizing and sorting Quick Accent  #20393) would be great and would probably fix things for everyone, but it requires a lot more work, like making a UI for sorting the characters for each key, making QuickAccent fetch the character ordering dynamically when the user makes changes to the settings, and other things that require going deeper into the code. Not anything undoable, but definitely more involved.

So I totally agree with you, but I still think simply making the usage frequencies persistent should be relatively easy and pretty effective for many users, so I think it's totally worth doing it while we wait for someone with the motivation to do manual ordering and even maybe full customisability like described in the issue I mentioned - and your own issue (#33556), which looks to me like a duplicate - ^^

[cinnamon-msft]

/dup #20393

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!