empty AppLogo as default value about burnttoast HOT 6 OPEN

Confirmed cannot remove default logo path from config.json, could change it to fake file but all toasts will generate warning.

Will get a getter options in the next update, @floh96, thanks for the suggestion!

from burnttoast.

@Windos - is this issue still up for grabs or has this already been implemented for the upcoming v1 release?

from burnttoast.

Hey @anthonyjvoss, yes consider this up for grabs.

v1 is still a ways out, and even then I'm thinking I'll need to support 0.x with updates even after it's out given how big of a change it'll be. That and anything fixed now will direct what "feature parity" is for v1.

from burnttoast.

You can get a toast without an AppLogo, at the moment though only by proving a path to a non-existent file (unless I'm forgetting something deep in my own code haha!)

New-BurntToastNotification -AppLogo C:\fake.png

You will get a warning that this file doesn't exist though.

The reason I never included this as an option was because in older versions of Windows 10 not having an AppLogo was ugly, but that changed in 20H2.

I think what we should do here is make it so that this works:

New-BurntToastNotification -AppLogo $null

And also make it so that you can remove the default AppLogo path in the config file in order to get no AppLogo (I think at the moment removing that will error, but haven't tested 🤔)

from burnttoast.

Or just a simple: -NoLogo option

from burnttoast.

Don't worry, v1 is on the way and there'll be a good option for this included ;)

from burnttoast.