Replies: 1 comment
-
Hey there @semce2 Sorry for the delay in responding, I'm sure you've moved on since this posting this but just to ensure there's an answer here. The "help" for that parameter can be viewed with this command: Get-Help New-BurntToastNotification -Parameter ExpirationTime
The key is that expiration time doesn't affect how long it shows on screen (which is what you'd think it affects), instead it's a hint to Windows to tell it when it should be removed from the Action Center (where missed notifications live.) An example use case for this is sending out a notification saying that there's muffins in the lunchroom. Let's say you send this out at noon you might set the expiration time to 1PM, so that if someone missed it they don't see it after lunch, or the next day, and get confused when there's no muffins. (Yes, the example is contrived, but it seems to land with most people 😅) Better docs is part of what I'm working on for the BurntToast v1 release and so the usage of this parameter should be clearer in the future. |
Beta Was this translation helpful? Give feedback.
-
I am unable to get the expirationtime parameter to work. Seems to always default to the system timeout. I am using (Get-Date).AddSeconds(7). I have been unable to find help for this parameter. Thanks
Beta Was this translation helpful? Give feedback.
All reactions