https://bugs.kde.org/show_bug.cgi?id=411098
Konrad Materka changed:
What|Removed |Added
CC||mate...@gmail.com
--- Comment #9 from Konrad
https://bugs.kde.org/show_bug.cgi?id=411098
--- Comment #8 from Nate Graham ---
That's true, you're right.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411098
--- Comment #7 from David Edmundson ---
>Easiest overall solution is to only allow one-way drag-and-drop.
The danger with that is if you have asymmetric patterns you can have users drag
things across one way but with no visible undo process without
https://bugs.kde.org/show_bug.cgi?id=411098
--- Comment #6 from Nate Graham ---
So basically, DND would be exclusively for the purpose of switching between
"always show" and "always hide" states.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411098
--- Comment #5 from Nate Graham ---
Easiest overall solution is to only allow one-way drag-and-drop.
For bi-directional drag-and-drop, I think dragging an applet into the popup
should always cause the applet to enter "always hidden" state, on the
https://bugs.kde.org/show_bug.cgi?id=411098
--- Comment #4 from David Edmundson ---
But what about when you drag the other way?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411098
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=411098
--- Comment #2 from Hans-Peter Jansen ---
Hi David, thanks for the feedback.
> The challenge of drag and drop is we're moving something tri-state:
> - always shown
> - always hidden
> - determined by the icon itself (default)
Well, the items, that
https://bugs.kde.org/show_bug.cgi?id=411098
David Edmundson changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk
--- Comment #1
