-
Notifications
You must be signed in to change notification settings - Fork 78
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
Option to set shortcutPolicy when creating PhotinoWindow #85
Comments
From: https://docs.microsoft.com/en-us/windows/win32/shell/enable-desktop-toast-with-appusermodelid This was enabled to allow toast notifications in a pull request by @mynameisvasco. We need to either allow opting out of native notifications on Windows or add a feature to remove the shortcut on shutdown. |
I hit this same problem. The workaround I used was to force a failure in the Photino native code that creates the shortcut. Since the shortcut is created from the window title when the window is first created, this can achieved by setting the Windows title to an empty string before calling WaitForClose(). To give the window a title set in the window created event handler instead:
|
We probably have to think about making the notification system startup configurable through a setter for the PhotinoWindow to prevent this issue. |
This is still something we'd like to have an option for. |
Our problem is currently that the customer has demanded the version number of the software in the titlebar. So whenever he installs a new version, it spams another icon in the start menu. Our installer (wix toolkit) however wont uninstall those icons, as he is not aware of the creation. I thought i tricked it by launching the window without the version number and add it afterwards, so the name of the shortcut would be identical to the one the installer creates. Still he creates another. Ours is in the system wide start menu, while photino creates another one in the user start menu. The customer currently is super unhappy having 10+ icons meanwhile (one release all 2 weeks), and we just cant disable this behavior. He demanded we fix that before the application goes into public availability. Ill try the empty-string title workaround, but in a long term i would love to see an option to disable this feature. Or at least fix that it recreates the shortcut with the exact same name. |
Every time a Photino application starts up, Photino.Native attempts to creates a shortcut in windows start menu.
I would like to avoid that for a portable application.
There is a setShortcutPolicy method in Photino.Native. Can I request a feature to forward a shortcutPolicy from Photino.Net when calling "new PhotinoWindow"?
Great work on this framework, its been a pleasure to use!
The text was updated successfully, but these errors were encountered: