[Shortcut Guide] Restore long-press Windows key activation

[niels9001]

Summary of the Pull Request

Restores the pre-V2 long-press Windows key activation for Shortcut Guide. Users can now choose between the customized keyboard shortcut (default Win + Shift + /) or holding the Windows key for a configurable duration (default 900 ms). The two modes are mutually exclusive, matching the v0.99 behavior.

Closes #48491

PR Checklist

• Closes: [Shortcut Guide] Restore Press and Hold shortcut #48491
• Communication: I've discussed this with core contributors already.
• Tests: Added unit tests for the new view-model properties (defaults, persistence, serialization round-trip).
• Manual tests: Verified switching activation modes triggers immediate runner re-registration; long-press fires the overlay; conflict warning surfaces appropriately.
• Localization: New strings (ShortcutGuide_PressTime.Header, .Description) added; the activation-method and warning strings already existed in Resources.resw from v0.99 and are reused as-is.

Detailed Description of the Pull Request / Additional comments

New settings (settings.json)

Key	Type	Default
use_legacy_press_win_key_behavior	bool	false
press_time	int (ms)	900

When use_legacy_press_win_key_behavior is true:

• The C++ module returns std::nullopt from GetHotkeyEx() so the runner does not register the customized shortcut.
• The module returns true from keep_track_of_pressed_win_key() and the configured ms from milliseconds_win_key_must_be_pressed(), which causes powertoy_module.cpp::UpdateHotkeyEx to register a press-action on VK_LWIN/VK_RWIN via CentralizedKeyboardHook::AddPressedKeyAction.
• Toggling the setting in the Settings UI fires IPC -> set_config -> UpdateHotkeyEx immediately, so no restart is needed.

Simplifications vs v0.99

v0.99 had two press-time settings (press_time and press_time_for_taskbar_icon_shortcuts). V2 shows the taskbar indicator inline whenever the selected section has a <TASKBAR1-9> marker, so the dual-stage timing is no longer meaningful. This PR ships one press_time setting.

Backwards compat

• Existing V2 users with no extra keys -> defaults apply, no behavior change.
• Users upgraded from v0.99 silently pick up their existing use_legacy_press_win_key_behavior / press_time values.

Files changed

File	Change
ShortcutGuideProperties.cs	Added UseLegacyPressWinKeyBehavior and PressTime (default 900 ms)
ShortcutGuideModuleInterface/dllmain.cpp	Parses new keys; overrides keep_track_of_pressed_win_key / milliseconds_win_key_must_be_pressed; gates GetHotkeyEx
ShortcutGuideViewModel.cs	New observable properties wired through NotifyPropertyChanged (which both raises change and saves+sends IPC)
ShortcutGuidePage.xaml	New Activation method ComboBox; the existing shortcut card and the new press-duration NumberBox toggle visibility; warning InfoBar
Resources.resw	New ShortcutGuide_PressTime.Header / .Description
Settings.UI.UnitTests/ViewModelTests/ShortcutGuide.cs	3 new tests

Validation Steps Performed

• Settings.UI.Library, ShortcutGuideModuleInterface, PowerToys.Settings, Settings.UI.UnitTests all build clean (exit 0, empty errors logs) on arm64 / Debug.
• Settings.UI.UnitTests -> all 10 ShortcutGuide tests pass, including the 3 new ones.
• Manually toggled the new ComboBox; verified the shortcut card hides, the press-duration NumberBox appears, and changing the duration takes effect without restart.
• Verified long-press triggers the overlay; verified switching back to Custom shortcut re-registers the shortcut.

[github-actions]

@check-spelling-bot Report

🔴 Please review

See the 📂 files view, the 📜action log, 👼 SARIF report, or 📝 job summary for details.

❌ Errors and Warnings	Count
⚠️ binary-file	1
⚠️ duplicate-pattern	2
❌ forbidden-pattern	1
⚠️ large-file	1

See ❌ Event descriptions for more information.

Some files were automatically ignored 🙈

These sample patterns would exclude them:

^src/modules/ZoomIt/ZoomIt/rnnoise/rnnoise_data_little\.c$
^src/modules/ZoomIt/ZoomIt/selfie_segmentation\.onnx$

You should consider adding them to:

.github/actions/spell-check/excludes.txt

File matching is via Perl regular expressions.

To check these files, more of their words need to be in the dictionary than not. You can use patterns.txt to exclude portions, add items to the dictionary (e.g. by adding them to allow.txt), or fix typos.

To update file exclusions, you could run the following commands

... in a clone of the git@github.com:niels9001/PowerToys.git repository
on the niels9001/restore-shortcut-guide-long-press-win branch (ℹ️ how do I use this?):

curl -s -S -L 'https://raw.githubusercontent.com/check-spelling/check-spelling/cfb6f7e75bbfc89c71eaa30366d0c166f1bd9c8c/apply.pl' |
perl - 'https://github.com/microsoft/PowerToys/actions/runs/27473829785/attempts/1' &&
git commit -m 'Update check-spelling metadata'

Forbidden patterns 🙅 (1)

In order to address this, you could change the content to not match the forbidden patterns (comments before forbidden patterns may help explain why they're forbidden), add patterns for acceptable instances, or adjust the forbidden patterns themselves.

These forbidden patterns matched content:

Should be a

\san (?=(?:[b-dfgjklpqtvwz]|h(?!onou?r|our|s[lv]|tml|ttp|ref)|n(?!ginx|grok|pm)|r(?!c)|s(?!s[ho]|vg))[a-z]|x(?!\b|[-\d]|ml))

If the flagged items are 🤯 false positives

If items relate to a ...

• binary file (or some other file you wouldn't want to check at all).

  Please add a file path to the excludes.txt file matching the containing file.

  File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.

  ^ refers to the file's path from the root of the repository, so ^README\.md$ would exclude README.md (on whichever branch you're using).

• well-formed pattern.

  If you can write a pattern that would match it,
  try adding it to the patterns.txt file.

  Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.

  Note that patterns can't match multiline strings.