When setting a font for the terminal, if it is not found properly by the
system, Qt attempts to use another font which is not an exact match. It
happens that the other font is not fixed-pitch, so konsole ends up using
an unsupported variable-pitch font for the terminal.
Place a warning when an exact match for the desired font has not been
found.
Move code responsible for 'forgetting' a view outside of code responding to the
TerminalDisplay deletion.
This avoids a loop like this:
~MainWindow
=> ~QStackedWidget
=> ~TerminalDisplay
=> QObject::destroyed
=> ViewContainer::viewDestroyed
=> ViewContainer::removeViewWidget
- internal cleanup
- try to remove TerminalDisplay from QStackedWidget which is being deleted and
crash
Instead the code now does:
~MainWindow
=> ~QStackedWidget
=> ~TerminalDisplay
=> QObject::destroyed
=> ViewContainer::viewDestroyed
=> ViewContainer::forgetView (does the internal clean up)
And if one tries to explicitly remove a view, sequence is:
ViewContainer::removeView
=> ViewContainer::forgetView
=> ViewContainer::removeViewWidget
The patch also removes ViewManager::focusActiveView() because it causes a crash
when closing a TerminalDisplay as it tries to put the focus on the deleted
TerminalDisplay. I initially called it through a queued connection, but realized
it is actually not needed for focus to be passed to the correct view, so just
removed it.
BUG: 331724
REVIEW: 118839
Fix box lines - using kmag is a great help
Thanks to Egmont Koblinger egmont gmail com for report and patch
BUG: 335339
FIXED-IN: 4.13.2
(cherry picked from commit 58d79e3624)
Coverity mentions the 128 array issue w/ possible Out-of-bounds writes.
The qFatal would catch it. However, adding comments on why [128] is
used and re-arranging the 'if' clarifies it.
(cherry picked from commit 14e9eb8b58)
This needs looked at later.
The below causes a noticable delay when opening the dialog - I'm not
entirely sure this is the best way to handle this.
Issue is QLineEdit->SetCompleter() won't work w/ KDE's KUrlCompletion
New feature in 2.13 allows columns/rows in profiles; however, the
rows would be incorrect depending on if tabbar was visible. Ideally,
this should not be needed but I would guess this won't get fixed
correctly until frameworks timeframe.
This calculation can still be wrong if ShowNavigationAsNeeded and
perhaps other times depending on height of tabbar.
FIXED: 2.13
(cherry picked from commit 73e1db3e3b)
This adds a push button to the Configure Konsole -> General Settings
Ideally, having a separate page listings all the possible entries
would be better.
BUG: 331474
FIXED-IN: 2.13
(cherry picked from commit 5a386ad591)
Feng Chao
Casian Andrei
Lukáš Tinkl
Luca Beltrame
Montel Laurent
Kurt Hindenburg
Aurélien Gâteau
Eike Hein
Alex Richardson
Alex Merry
Kevin Ottens
David Faure
Burkhard Lück
Yuri Chornoivan