Get-BurnToast about burnttoast HOT 12 CLOSED

Ah, thanks ! I was actually looking in Content instead of Data, and couldn't figure out what was wrong.

from burnttoast.

Sounds like a good idea, I'll see what I can do

from burnttoast.

Here's what I've found I can do:

List all notifications from a given AppId (generally all of the toasts from this module will be under the same banner.)

Clear all notifications from a given AppId

Clear a specific toast (based on unique identifier)

All looks good and will be in the next release! Thanks again for the suggestion

from burnttoast.

I like this feature.

I will be creating a notification every 30 minutes if a PC needs a reboot and it would be great if before iT created one, it checks to see if one is already there and closes it. That way there will not be a lot of notifications sitting there.

from burnttoast.

v0.7.0 will have functions for getting, and clearing toasts:

Get-BTHistory
Remove-BTNotification

These are feature complete, but need comment based help. Regardless, keep an eye out for the next release... soon(tm)

from burnttoast.

Does Get-BTHistory also gets the notification's text/content ? That would allow, along with -UniqueIdentifier to manually add information to a toast :)

from burnttoast.

from burnttoast.

Just noticed my comment didn't really make sense, It's a bit late here so forgive me about that - I meant manually *updating a toast's text - I could parse the previous toast in my script using its known identifier, and recreate it with an additional info in the text for example, which could be a manual solution to #54

from burnttoast.

from burnttoast.

Any way to get the binded text :/ ?

(The use case is that I'm looking to update a previously built toast by appending information to it, instead of replacing it)

from burnttoast.

Absolutely, one of the properties surfaced with Get-BTHistory includes the notification data, that stores that binding values:

You'd need to pull these out and use them to build up a new hashtable for the update, but it'll let you know what was originally there.

from burnttoast.

Yeah, unfortunately that content isn't the "compiled" end result (something I didn't realise I wish was a thing until now)... it'll include placeholders for the bindings in curly braces (e.g. "{FirstLine}") but it's up to the Windows API to smush that and the NotificationData together when displaying the notification.

from burnttoast.