On Mittwoch, 31. Juli 2013 12:03:12 CEST, Kevin Krammer wrote:
My guess would be that it is up to the application. If the
applications does
not want MMB drag, e.g. because it wants to use MMB for
something else, then
it should be able to deactivate that.
I would object this from a HIG POV.
On Tuesday, 2013-07-30, Hyperz wrote:
> The issue is that if the mouse moves even 1 pixel while the middle mouse
> button is being pressed/clicked to close a tab KTabBar doesn't
> emit mouseMiddleClick() and the tab doesn't get closed.
Hmm, shouldn't there be something like a minimum drag distanc
Hello,
There's and old compatibility feature in KTabBar for moving tabs using the
middle mouse button (see:
http://api.kde.org/4.10-api/kdelibs-apidocs/kdeui/html/ktabbar_8cpp_source.html#l00209
).
This compatibility feature can cause problems with applications that have
movable tabs and use the
