nvda

4bde28c9 - UIA/ToastWin10/build 15063 and later: before announcing toasts, consult last toast message in case a repeat event was fired. re #7128 (#7376)

UIA/ToastWin10/build 15063 and later: before announcing toasts, consult last toast message in case a repeat event was fired. re #7128 (#7376) * UIA/ToastWin10/build 15063 and later: before announcing toasts, consult last toast message to make sure it is different, caused by possible problem in uIA Core in Creators Update and later. re #7128. According to mick Curran (NV Access), UIA Core may have bugs when it comes to firing multiple toast events after using UWP's for a while, so detect this by consulting last toast message if the build is 15063 or later. This does not affect older releases such as Anniversary Update (build 14393). * Duplicate toasts: check runtime ID and time instead of name. Reviewed by Mick Curran (NV Access): check runtime ID and timestamp instead of name alone. However, in latest Windows Insider build (1623x), toasts have same runtime ID, so both this and timestamp must be checked (leave the event if runtime ID's are the same and timestamps are less than a second apart). * ToastWin10: typo (toastTimestamt -> toastTimestamp). Caught by Mick Curran (NV Access): toastTimestamt -> toastTimestamp (thanks).