https://bugs.kde.org/show_bug.cgi?id=464142
--- Comment #4 from H.H. <[email protected]> --- I still don't see, why someone really wants to get his clipboard shared with a not directly connected device. If would want that, I would have connected A anc C. I really think, this should be the default: >Technically there could be an option to explicitly break chaining by making >sure the clipboard changes coming from KDE Connect itself are not propagated, >but I still believe that the earlier proposed solutions are the right way. and one could optionally opt in to allow chaining. Perhaps you could deliver practical examples, why the current behaviour makes sense? I have a counter example: Two persons have a working PC each, and they have a shared device, which both are connected to, because sometimes its nice to share something with that device. But when person A is working, for each copy operation (which is quite often), a notification in KDE pops up on persons B PC, which is quite annoying. -- You are receiving this mail because: You are watching all bug changes.
