Old compatibility feature in KTabBar causing problems.

[Kevin Krammer]

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 distance, i.e. a 
threshold in pixel movement below which it is not yet considered a drag start?

> Do we still need such an old compatibility feature? Especially since
> virtually everything lets you move tabs with the left mouse button these
> days and middle-mouse-to-close is becoming the default.

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.

Applications that do not use MMB for anything could keep it available in case 
their users do use it.

Like having or not having pre-tab close buttons.

Cheers,
Kevin
-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20130731/b4efa462/attachment.sig>