Bug 365997 - Separating a tab to an own window is slow
Summary: Separating a tab to an own window is slow
Status: RESOLVED DUPLICATE of bug 371939
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 16.04.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-22 22:03 UTC by Jan Wiele
Modified: 2017-09-08 01:41 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Tab separates late from the konsole window. (219.75 KB, image/png)
2016-07-22 22:03 UTC, Jan Wiele
Details
GIF of the problem (1.23 MB, image/gif)
2016-10-14 14:28 UTC, Jan Wiele
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Wiele 2016-07-22 22:03:09 UTC
I often use the feature to separate a tab of one konsole to create a second konsole window.
But atm you cannot grab the tab and flip it to the edge of the screen to get a new window. It takes 1-2 seconds until the the tab follows the mouse cursor.

I've attached a screenshot, which shows the problem of the delay. As one can see, I'm already near the edge of my screen with the cursor, but the tab just separated.

Reproducible: Always

Steps to Reproduce:
1. Open konsole, create a second tab.
2. Grab the tab, dont release the mouse button, move the mouse a little bit.
3. It takes about one second until the tab is separated and follows the mouse.
4. If you dont wait until the tab is separated, nothing happens.
Comment 1 Jan Wiele 2016-07-22 22:03:48 UTC
Created attachment 100252 [details]
Tab separates late from the konsole window.
Comment 2 Jan Wiele 2016-10-14 14:28:45 UTC
Created attachment 101562 [details]
GIF of the problem

Today I talked to the user hendrix on #kde. He confirmed this behavior and also created a nice gif to show the problem.
Comment 3 Nate Graham 2017-09-08 01:41:37 UTC
Looks like this is a duplicate of https://bugs.kde.org/show_bug.cgi?id=371939, which is now fixed!

*** This bug has been marked as a duplicate of bug 371939 ***