Bug description:

When using wxNotificationMessages on MSW with MSWUseToasts() enabled (like the dialogs sample does), clicking the notification or letting it timeout will both result in wxEVT_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:

1. Start 'dialogs' sample on MSW.
2. Open User Notification Test Dialog.
3. Click 'Show'.
4. Observe that whatever you do – click or no click –, the status text will soon show "Notification was clicked".

But why?

It looks like regardless of what the user actually did or didn't do, the overload of Invoke taking IInspectable* gets called, and that one sends the click event. (IInspectable is the base class for IToast{Dismissed,Failed}EventArgs, so it makes some sense.) The debugger shows that the contents of the args object is actually an IToastDismissedEventArgs.

Platform and version information

• wxWidgets version you use: master
• wxWidgets port you use: wxMSW
• OS and its version: Windows 10.0.19045.3996