[Bug 121895] Re: knetworkmanager systray right-click and left-click behaviors have swapped places
** Changed in: knetworkmanager Importance: Unknown = Wishlist -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to knetworkmanager in ubuntu. https://bugs.launchpad.net/bugs/121895 Title: knetworkmanager systray right-click and left-click behaviors have swapped places -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 121895] Re: knetworkmanager systray right-click and left-click behaviors have swapped places
** Changed in: knetworkmanager Status: In Progress = Fix Released -- knetworkmanager systray right-click and left-click behaviors have swapped places https://bugs.launchpad.net/bugs/121895 You received this bug notification because you are a member of Kubuntu Team, which is subscribed to knetworkmanager in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 121895] Re: knetworkmanager systray right-click and left-click behaviors have swapped places
Thanks for the pointer. That item is about something different, though: the filer seems to be asking to be able to right-click on individual networks and interfaces, rather than the knetworkmanager systray icon. I'd argue that knetworkmanager isn't an application, so while the behavior is perfectly appropriate for amarok, but it is inappropriate for knetworkmanager. Counterexamples to amarok: kmix, kmenu, klipper, knotes. These are all accessories, or utilities - as is knetworkmanager. It's a question of primary behavior, again. The new knetworkmanager behavior is to show properties by default. That might be ok if the user could change networks on the first screen of the connection status window, but that isn't possible. -- knetworkmanager systray right-click and left-click behaviors have swapped places https://bugs.launchpad.net/bugs/121895 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for knetworkmanager in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
