-
Notifications
You must be signed in to change notification settings - Fork 171
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
Toastnotifications are not displayed after reconnecting to Terminalserver (RDP) sessions #99
Toastnotifications are not displayed after reconnecting to Terminalserver (RDP) sessions #99
Comments
I installed VS on a the terminalserver and ran the BasicUsageExample from source in Debug with "JustMyCode" disabled.
|
Tracked it down to collapsing the NotificationsWindow:
When setting this.Visibility = Visibility.Hidden the issue does not seem to occur.
There seem to be some obscure RDP/WPF issues at play here. Edit: This also occurs when using the "normal" remote desktop and not only when using TerminalServer |
Fixes rafallopatka#99 Workaround for wonky WPF/RDP behaviour when using Transparency & Visibility.Collapsed
…ions Update NotificationsWindow.xaml.cs
Not sure what happend here but closing this was not on purpose. |
There are chances toast will not show after computer wake up or after screen saver closed. |
Connecting to a Terminalserver ToastNotifications are displayed. If the User sessions is disconnected (by Admin or after timeout for example) and the user reconnects, the session and software is still open but no Messages are displayed anymore.
Library version
ToastNotification.Messages 2.5.1
Expected behaviour
Messages should be displayed after reconnect.
Actual behaviour
Messages are not displayed/visible after reconnect.
Steps to reproduce behaviour
Run attached demo in Terminalserver sessions, disconnect user and reconnect again.
Code to reproduce behaviour
ToastNotificationDemo.zip
Questions
The text was updated successfully, but these errors were encountered: