https://bugs.kde.org/show_bug.cgi?id=427790
--- Comment #11 from Daniel Tang <danielzgtg.opensou...@gmail.com> --- I can see several ways to get this implemented though. The most direct way, adding an exit action on the notification, isn't a good idea. There is a limit to the number of actions that Android will allow before ignoring the rest. As an aside, I thinking about a debug screen. In that screen (I'm thinking of something like Facebook's internal settings), there could be menu items like "force crash" or "jvm exit". Although that would be some kind of button, I don't think it would be any more convenient than the force quit button so this won't be the main solution. To design a more comprehensive solution, I though of Termius, whose notifications are only active when there is an active connection. This also reminds me of KDE's WiFi settings. In those settings, there is a "connect automatically with priority" thing, similar to other OS's connect automatically checkbox. Unlike Termius, KDE Connect also receives incoming connections, so a separate toggle would be necessary for that. It is fortunate that plans already exist in the code, with this named as "discovery mode". So basically this solution would involve 3 changes: - Implement discovery mode (option to reject unknown devices when pairing is not open) - Add a "connect automatically" toggle for each device. When it's unchecked, disconnect if connected, and reject further connection attempt - Dismiss the notification and stop the background service if discovery mode is disabled and "connect automatically" is disabled for all devices. This could be considered an optimization that naturally follows from the fact that we will never have connections to any device if both the previous two options are disabled What do you think of this? -- You are receiving this mail because: You are watching all bug changes.
