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

[Settings] Deep link into Settings for a PowerToys Run Plugin #36775

Open
hlaueriksson opened this issue Jan 9, 2025 · 0 comments
Open

[Settings] Deep link into Settings for a PowerToys Run Plugin #36775

hlaueriksson opened this issue Jan 9, 2025 · 0 comments
Labels
Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams

Comments

@hlaueriksson
Copy link
Contributor

Description of the new feature / enhancement

It is possible to deep link into settings for a specific utility:

public static void OpenSettings(SettingsWindow window, bool mainExecutableIsOnTheParentFolder)

Or via:

PowerToys.exe --open-settings=<SettingsWindowName>

As a PowerToys Run community plugin author, it would be nice to be able to deep link directly in to the settings of a plugin.

For example with:

PowerToys.exe --open-settings=Run --plugin-id=CEA0FDFC6D3B4085823D60DC76F28855

Scenario when this would be used?

A plugin could display a result to the user to open the Settings and edit the plugin configuration.

This would be useful for:

  • A newly installed plugin that require configuration
  • A plugin that is in an invalid configuration state
  • A plugin that has a specific query for settings

If the plugin settings are opened, the plugin should be scrolled into position, expanded and focused:

Image

Supporting information

I would like to use this feature here:

@hlaueriksson hlaueriksson added the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams
Projects
None yet
Development

No branches or pull requests

1 participant