-
-
Notifications
You must be signed in to change notification settings - Fork 470
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
WinToast needs a special shortcut #5954
Comments
I can reproduce that, yeah. |
It's silly that we need to create a shell shortcut. We can fix the name if we initialize WinToast at the start (which calls Nerixyz@3bfe55f implements this. It's hard to properly test, because the system appears to be caching some stuff. If you're testing this, test portable first and try non-portable afterward. Also found a WinToast bug while testing 🙂 |
Thanks for trying to fix this @Nerixyz. Yes, the caching thing is really annoying while trying to debug this. With your patch applied, I get these results: Switching to normal mode, I get for the first notification no icon and ".Chatterino 2" as name, It looks like it only works if a shortcut is present. I also noticed the other bug you mentioned. Thanks for reporting and fixing this as well. |
This is the unfortunate thing. Maybe there could be an option to create a shortcut? Not sure. I don't want portable to mess with the start menu though - that's not what I'd expect from it. I'm also running portable when testing, so I wouldn't want that to plant itself in my start menu. |
Yes, we could add an option for this. We should also keep in mind that without a valid shortcut, options like |
I tried making this setting, could you try this and give me feedback? New diff
|
We should try to make the setting inverse. Currently, having this disabled will create a shortcut. I'd rather have it like In the user-visible setting name, it shouldn't mention WinToast (or even notifications). This could be explained in the tooltip for why it's needed. Maybe something like "Create explorer shortcut" or "Create start menu shortcut". We should also ensure that the installer creates the same shortcut. |
Applied your suggestions Another diff
|
This looks good. Mini nits: The argument for |
Checklist
Describe your issue
Windows uses a Shortcut with AUMI (App User Model ID) to associate a notification with an application.
If this shortcut is missing, notifications may fail to display or behave incorrectly See here
Since 6e0852f we disabled creation of this shortcut.
For me, if this is missing, the following unexpected behavior occurs:
System -> Notifications & actions
Maybe fixable with this patch
This should create a shortcut, unless you explicitly disable it (what #3817 was about).
I couldn't figure out a different way to get this working.
Check if your shortcut has AUMI configured
Use a Tool called [LECmd](https://github.com/EricZimmerman/LECmd) with this parameter on a shortcut file:LECmd.exe -f Chatterino2.lnk
If the shortcut has AUMI configured, you find this in the output
App User Model ID ==> .Chatterino 2
Manually create a shortcut with AUMI
Use a Tool called [make-shortcut-with-appusermodelid](https://github.com/Robertof/make-shortcut-with-appusermodelid)makelnk.exe ".Chatterino 2" "C:\PathToChatterino\chatterino.exe" Chatterino2
@Nerixyz if you have time, could you try to reproduce this?
Screenshots
*Reply Box removed since d0cf6c4
**Shortcut was renamed to
Chatterino
by myselfOS and Chatterino Version
Chatterino Nightly 2.5.2 (commit 449aefc) Qt 6.7.1 Running on Windows 10
The text was updated successfully, but these errors were encountered: