-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
Allow us to move Windows Notifications #73
Labels
Idea-New PowerToy
Suggestion for a PowerToy
Comments
Hi, I'm adding the "Suggested PowerToy" label, as it may be possible to achieve it through a PowerToy. In any case, the place to send Windows suggestions would be through the Feedback Hub: https://support.microsoft.com/en-us/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub |
ryanbodrug-microsoft
pushed a commit
to ryanbodrug-microsoft/PowerToys
that referenced
this issue
Apr 14, 2020
…nintab Add option to open web search in new tab or new window
crutkas
changed the title
Suggestion: Allow us to move Windows Notifications
Allow us to move Windows Notifications
Sep 9, 2020
This was referenced Sep 9, 2020
SocietasEvanescentes
closed this as not planned
Won't fix, can't repro, duplicate, stale
Jul 9, 2022
stefansjfw
pushed a commit
that referenced
this issue
Dec 18, 2024
* Allows `enter` to activate items again * populates the context menu in the `ActionBar` with real values, as the user moves the selection * Also adds a generic `PerformCommandMessage`, which lets us have one message for "go to a page, or invoke a command" ref #73
stefansjfw
pushed a commit
that referenced
this issue
Dec 18, 2024
stefansjfw
pushed a commit
that referenced
this issue
Dec 18, 2024
A lot of this is just samples work, so skip on down to `src/modules/cmdpal/Microsoft.CmdPal.UI.ViewModels/ActionBarViewModel.cs`. * Updates the Action Bar with the title of the currently active page when we navigate to it * listens for PropChanged events from `ICommandItem`s in lists and on `IPage`'s (to display a loading bar) * Also didn't put this on the ShellPage quite yet, because the diff was already massive, and there's complicated "are _we_ loading the page? did the `IPage` say it was loading?" plumbing that needs to be done. * adds rudimentary support for showing an exception, if there's an error we catch * I didn't add log this everywhere yet though, since we're not 100% confident on the messaging infrastructure here * I decided against putting this on the shell page, because I want users to be able to _go back_ from a page with an exception, and that didn't seem trivial if it was on the shellpage itself * Then updates a bunch of extensions to better utilize the loading state. * Then discovers a really weird bug with event callbacks in WinRT, so I decided to wrap those in try/catches to have extensions explode less often. (#181) * Then also adds a bunch of "evil" samples, to make a unified place of "things to try and break us" ref #73 --------- Co-authored-by: Mike Griese <zadjii@gmail.com>
stefansjfw
pushed a commit
that referenced
this issue
Dec 18, 2024
Doesn't use all these everywhere, but starts plumbing them into ViewModel's so that @niels9001 can start using more things in more places. ![image](https://github.com/user-attachments/assets/f1c7c0c4-c4b2-49a4-889f-2c2e5f595f63) I didn't actually colorize the tags, because that requires a Brush, and I don't think I'm supposed to put brushes in the viewmodels ref #73
stefansjfw
pushed a commit
that referenced
this issue
Dec 18, 2024
…sions-on-close Ref #73. What it says on the tin. Terminate extensions when the main window closes.
stefansjfw
pushed a commit
that referenced
this issue
Dec 18, 2024
Get the other two types of pages back in. Form pages and Markdown pages. ![image](https://github.com/user-attachments/assets/27d10b91-6920-421e-912b-a64ca26baf93) When forms fail to parse, we'll display the exception by replacing the card with one of our one authoring ![image](https://github.com/user-attachments/assets/e3e74d7c-d6da-4d8a-b91b-d66aff8b3d9c) Markdown pages support multiple bodies, and possibly details: ![image](https://github.com/user-attachments/assets/8abb36e9-d3aa-4d1a-b045-d34d84fe16e6) ![image](https://github.com/user-attachments/assets/047d4bdd-e356-4a70-b62d-4ccd678b7285) Ref #73
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Windows 10 by default shows notifications in the bottom right. It feels weird to interface with them down there. If there is something Windows 8/8.1 and macOS did right, it's notifications being in the top right
The text was updated successfully, but these errors were encountered: