Get-BurnToast

[tedkol]

Feature Request:

Get-BurntToastNotification - retrieve all notifications from the notification center.

[Windos]

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

[Windos]

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

[jwood79]

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.

[Windos]

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)

[AmineI]

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

[Windos]

It returns an object which includes the xml (which you can inspect to see the content), any bindable text (this is a whole topic in and of itself). The object also has the tag and group (which basically = the unique identifier)

…

On Wed, 27 Mar 2019, 12:03 PM Amine A., ***@***.***> wrote: Does Get-BTHistory also gets the notification's text/content ? That would allow, along with -UniqueIdentifier to manually add information to a toast :) — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#62 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGojChBG-xVCrKCEvhUvMt03s-FJqprtks5vaqdHgaJpZM4bNvLC> .

[AmineI]

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

[Windos]

Ooh, I should probably update that ticket. There'll be a *much* better way to update toasts in 0.7.0

…

On Wed, 27 Mar 2019, 12:31 PM Amine A., ***@***.***> wrote: 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 id, and recreate it with an additional info in the text for example, which could be a manual solution to #54 <#54> — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#62 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGojCke0LFDSEKkSN-EhVwSYDMptVTZqks5vaq24gaJpZM4bNvLC> .

[AmineI]

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)

[Windos]

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.

[AmineI]

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

[Windos]

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.