https://bugs.kde.org/show_bug.cgi?id=366796
--- Comment #3 from Matthew Woehlke <mwoehlke.fl...@gmail.com> --- (In reply to Ian Wadham from comment #1) > (In reply to Matthew Woehlke from comment #0) > > Multi-select behavior should work like it does in every other application. > > Is there a standard on this? If so, Palapeli should follow it. Certainly there is the way it works in QAbstractItemView and derived classes. AFAIK this is consistent (most Qt applications at least are relying on this for selection behavior, and I think also most of the major toolkits agree on this selection behavior). Anyway, it makes sense to follow what QAbstractItemView does. Note of course I am talking about the ExtendedSelection mode, which seems to be the most commonly used, at least for instances when you think about selecting items (e.g. not systemsettings, configuration dialogs). Compare for example the behavior in gwenview or dolphin. (In reply to Ian Wadham from comment #2) > I have not checked the code, but I am pretty sure this behavior is nothing > to do with Qt or QGraphicsView. Sure; looking over the documentation, it seems QGraphicsView has some helpers for selecting things, but isn't primarily responsible for selection behavior. Previously, I didn't know if it was or wasn't. > There are some other mouse operations I am not happy about in Palapeli, such > as the possibility of crashing Palapeli when dragging and joining pieces. Ah... yeah, noticed that too :-). -- You are receiving this mail because: You are watching all bug changes.
