-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
New homepage / activation experience in Settings #26816
Comments
This seems like a great "quick win" solution. It's similar to what Windows already does with Accessibility Features like Sticky Keys. JetBrains IDEs also do something similar with potentially confusing shortcuts like |
Shortcut for the dashboard with all active modules + shortcuts would be awesome! Often i forgot a shortcut for a module so i need a fast way for an overview. |
One change suggestion in the concept UI mockup - Don't display active and inactive sections side by side. I won't be using the inactive modules, and they'll just be occupying the space unnecessarily. Divide the Home page into two sections - Active at the top and Inactive below that. That way, I'll be able to see more number of active modules, possibly without needing to scroll. |
How can Image reziser, active and inactive at the same time? |
Love it! Maybe you could add keyboard shortcuts to the systray too? Would be useful as I forget the shortcuts sometimes. |
In opposition to @bagarwa, I think having the Inactive quickly in sight provide users visibility to enable powertoys modules. A one click enabling might increase usage because of the ease to do it. Perhaps having that section being collapsible (and persisted) could be a good compromise. |
@gigi2006 This is a visual comp (image) we created to conceptually show the idea and quickly gather feedback. It is not functional code. |
I really like this. I also like this inactive panel on the side - one of the motivations for the change is exposure to features that aren't enabled by default, so tucking them away at the bottom as was suggested previously negates that entirely, making the list no more useful than the modules sub sections that already exist on the left. Love the idea of shortcut keys being quickly visible. I didn't even know there was a shortcut for the Fanzy Zones editor until this mockup 😅. |
It may make sense to give modules categories to be sorted and displayed on the home page perhaps. More modules keep coming, it's no longer just a few modules within PowerToys. It's getting pretty cluttered. |
@crutkas, the mockup lacks a clear indication of updates and new additions of modules since the last installed version. Lazy users like me often find checking the changelog cumbersome, leading to ignorance, as suggested in #21122. It would be convenient to include small icons or indicators alongside updated and new modules, facilitating quick tracking module-by-module checks. Additionally, as suggested in #21122, a brief walkthrough since the last installed version would be pretty darn amazing! For those who don't need it, adding a quick-simple on/off switch on the homepage would suffice. |
The work associated with this issue has been released as part of the 0.75 sprint. Please update PowerToys to the latest. https://github.com/microsoft/PowerToys/releases |
Description of the new feature / enhancement
PowerToys is an incubation system for testing new work. Some features are on be default, others off. Most of the time, we will default them to on. This, from time to time, leads to unexpected results when someone quickly invokes find my mouse or other utilities.
My proposal is to have a more upfront system in both first time run / upgrade as well as the 1st page in settings to show crisply,
When new utilities come in, this line would also be added to the top of the upgraded dialog as well.
Scenario when this would be used?
Getting new users and upgrade paths crisply aware of new things and defaults
Concept
This is a very conceptual and quick-and-dirty comp of what a new homepage experience could look like:
The text was updated successfully, but these errors were encountered: