Summary: | Regression: Tabs never change back to "no new activity" colour | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | Luke-Jr <luke-jr+kdebugs> |
Component: | tabbar | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | boris.bigott, cfeck, nate |
Priority: | NOR | ||
Version: | 18.12.0 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | https://commits.kde.org/konsole/7dfae7a7b526706c3e2f27b54842d487f753db75 | Version Fixed In: | 18.12.1 |
Sentry Crash Report: | |||
Attachments: | fix for bug |
Description
Luke-Jr
2018-12-24 22:38:57 UTC
Created attachment 117096 [details] fix for bug Looks like this was broken by commit 83ebda5bf4a31405af53fe8dc18797fb32fd6d5e Author: Tomaz Canabrava <tcanabrava@kde.org> Date: Wed Jul 4 11:07:39 2018 +0200 Use QTabBar: drop tons of code ...which dropped the currentTabChanged slot attachment for some reason. Added it back (updated to current code) and things work again! (Patch attached) I can't reproduce this on master; I'll try to figure out what fixed it and backport it On master, it looks like it was fixed in: commit 7a43e3b2cde05a70a38c0bcac39051b675425bf9 Author: Tomaz Canabrava <tcanabrava@kde.org> Date: Mon Dec 10 10:01:09 2018 -0500 Don't duplicate the tabs when Spliting the View I'm not sure it makes sense to backport this, as it looks to be more involved than just fixing issues...? Ok, I don't think I'm going to backport that - I'll look at your patch - thanks Fixed on master already. Backport/alternative patch is possible. Git commit 7dfae7a7b526706c3e2f27b54842d487f753db75 by Kurt Hindenburg. Committed on 26/12/2018 at 14:44. Pushed by hindenburg into branch 'Applications/18.12'. Fix regression on tab color not reverting back to 'no activity' color Already fixed in master with new tab code. FIXED-IN: 18.12.1 M +2 -0 src/ViewContainer.cpp https://commits.kde.org/konsole/7dfae7a7b526706c3e2f27b54842d487f753db75 *** Bug 396689 has been marked as a duplicate of this bug. *** *** Bug 402621 has been marked as a duplicate of this bug. *** |