-
Notifications
You must be signed in to change notification settings - Fork 1.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
wxNotificationMessage always sends click event on MSW with toasts #24320
Comments
Cc @TcT2k |
lanurmi
added a commit
to lanurmi/wxWidgets
that referenced
this issue
Feb 19, 2024
No idea why this is needed, but would seem to fix wxWidgets#24320.
lanurmi
added a commit
to lanurmi/wxWidgets
that referenced
this issue
Feb 19, 2024
No idea why this is needed, but would seem to fix wxWidgets#24320.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description:
When using
wxNotificationMessage
s on MSW withMSWUseToasts()
enabled (like the dialogs sample does), clicking the notification or letting it timeout will both result inwxEVT_NOTIFICATION_MESSAGE_CLICK
being sent.Expected vs observed behaviour:
It is expected that
wxEVT_NOTIFICATION_MESSAGE_DISMISSED
would be sent in case of timeout or explicitly dismissing the notification.To Reproduce:
But why?
It looks like regardless of what the user actually did or didn't do, the overload of
Invoke
takingIInspectable*
gets called, and that one sends the click event. (IInspectable
is the base class forIToast{Dismissed,Failed}EventArgs
, so it makes some sense.) The debugger shows that the contents of theargs
object is actually anIToastDismissedEventArgs
.Platform and version information
The text was updated successfully, but these errors were encountered: