Make timeout for ConnectionNotifier configurable

[rpodgorny]

it would be really nice to have the ability to specify a timeout for ConnectionNotifier's toast messages. without it, the message hangs there forever forcing me to click it to make it disappear. this is really annoying on my zenbook duo, where i connect/disconnect the keyboard quite often.

[cschramm]

What is your notification daemon?

[rpodgorny]

mako

[infirit]

The ConnectionNotifier sends a timeout of -1 which means use whatever the default is in notifications daemons like mako.

[cschramm]

mako came up a couple times because its default is no timeout, opposed to seemingly all other daemons. You need to configure the default that you prefer.

If we'd specify an explicit timeout, all users would be left with it instead of the one they are used to and might even have chosen explicitly.

[rpodgorny]

hmmmm, didn't know that there's a default value. thanks! i will play with it and see.

anyway, i still think it would be nice to have the option to specify timeout value specific just for blueman (to allow me to make is somewhat shorter than other notifications).

[infirit]

I marked as feature request and its fairly simple to add to the plugin. Just need to find some time and motivation.

[rpodgorny]

mako came up a couple times because its default is no timeout, opposed to seemingly all other daemons. You need to configure the default that you prefer.

If we'd specify an explicit timeout, all users would be left with it instead of the one they are used to and might even have chosen explicitly.

well, i meant the default in blueman would be "-1" (no change) but a new option would allow user to change it whatever.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[hans-fritz-pommes]

Might it be that you are using an old version of blueman (<2.4.5)? In 2.4.5, the connection notifications are made transient.