why bother and set "no icon" explicitly?

Mainly for consistency, these reasons:

1. Ensures what the chooser currently displays as the current selection represents code in the callback was actually executed for that choice, even if it's the default.
2. Future-proofs changes to the callback code; any additions to the callback for sure will be reflected on startup.
3. Avoids duplicate code in main() (e.g. setting win->icon(0))

You could also mention that the icon used in Alt+Tab is changed as well.

Sure, I'll add that to the small list.

I was trying to avoid too many window manager specifics, as they seem to change with the wind.

Originally I was just going to say "Sets the application's window manager icon" and leave it to the reader as to what that infers, but figured a few generic examples could only help.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.