https://bugs.kde.org/show_bug.cgi?id=427790
Frank Steinmetzger <war...@gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |war...@gmx.de
--- Comment #15 from Frank Steinmetzger <war...@gmx.de> ---
(In reply to Daniel Tang from comment #13)
> > I just want to close the app
I have the same problem as the OP. I use kdeconnect very sporadically, usually
to transfer one or a few files, nothing more (although I appreciate all the
other possibilities it provides). But because of the notification issue, I
usually go to Total Commander instead and do it The Old Way via sftp, even
though that requires me to input a password. It’s just too much hassle to
afterwards go into settings, wait for the app list to load, scroll dooooown,
find the app and kill it. I, too, like the way Syncthing implemented it with
its “Exit” menu item. In contrast, its “competitor” Nextcloud Sync Client has
the same issue as kdeconnect: there is no exit function and it has a permanent
notification. Which is why I usually avoid it, because usually I just need one
file from my nextcoud—not a permanent sync.
> How about a further "Disconnect from all devices" button on the settings
> screen that does the 3 things, causing the app and service to exit?
That doesn’t sound so bad. But did you mean the screen behind the cogwheel, or
the menu that can be slided in from the left? I think a “Disconnect all” would
suffice and as soon as there is no active connection, the notification can go
away. Of course this would mean it no longer listens to incoming connection
requests. Hm... I understand your desire to not make it too complicated for
non-techie users, so a toggle “Listen for incoming connections” is maybe too
overengineered. I’m afraid I’m a bit old-school for the modern Android-approach
on UI things. :)
Please don’t get me wrong. I think a service that auto-discovers and -connects
is a reasonable and useful feature. But only if you want it. If not, then it’s
in your way. Another aspect to consider for an always-running service: it
consumes power for CPU and network, possibly needlessly. Also, when I am in a
different network, I might not want to broadcast search requests for other
kdeconnect instances as soon as I load the app.
I just had a look at kdeconnect on my phone and connected it to my KDE machine.
And I currently cannot see any disconnect option there, neither on the Android
end nor on the KDE desktop. The only “option” I had was to shut down the WiFi
on a participant. But this left the app UI in a strange state. I might write
another ticket about that.
--
You are receiving this mail because:
You are watching all bug changes.
