Closed craftyguy closed 8 months ago
@craftyguy okay, maybe a 'disable-warning' option of some sort should do right? The warning exists in case users need to check for any OBEX/Network related issues. This can be implemented.
@darkhz Ya totally makes sense why the warning is there in the first place!
I think most UIs will show an option to hide future warnings (like a checkbox or something), not sure if that's possible with the toolkit you are using. In any case, even just a config file option to hide it would be fine with me. Thanks for considering it!
This feature has now been implemented with the no-warning
command-line option.
To disable warnings, it can be done via the command-line:
bluetuith --no-warning
Or by setting the configuration parameter:
no-warning: true
Woohoo, thanks a lot!!
On October 24, 2023 9:04:36 PM CDT, darkhz @.***> wrote:
This feature has now been implemented with the
no-warning
command-line option.To disable warnings, it can be done via the command-line:
bluetuith --no-warning
Or by setting the configuration parameter:
no-warning: true
I don't use OBEX, and don't plan to, but use bluetuith constantly for managing bluetooth headsets and other peripherials. The warning on start is quite annoying :)