https://bugs.kde.org/show_bug.cgi?id=362281
Daniel Vrátil <dvra...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version Fixed In| |5.6.1
Latest Commit| |https://commits.kde.org/kma
| |il/3033e8b58fe41d5911320599
| |710b05e124e23cf6
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Daniel Vrátil <dvra...@kde.org> ---
Git commit 3033e8b58fe41d5911320599710b05e124e23cf6 by Daniel Vrátil.
Committed on 21/08/2017 at 17:37.
Pushed by dvratil into branch 'Applications/17.08'.
Don't set KMKernel::xmlGuiInstanceName() by default
This is a porting regression - KMKernel by default should have an
invalid xmlGuiInstance, which implies that KMail is not running as
a component. When xmlGuiInstance is set, like from KMail::Part, then
we know we are running inside Kontact or similar. Before this change
xmlGuiInstance was always set by the Kernel, so code that was using
this to check if it's running inside Kontact or not did not work.
Together with a porting typo fix, this fixes the ambiguous Ctrl+N
shortcut in KMail inside Kontact.
FIXED-IN: 5.6.1
M +0 -1 src/kmkernel.cpp
M +1 -1 src/kmmainwidget.cpp
https://commits.kde.org/kmail/3033e8b58fe41d5911320599710b05e124e23cf6
--
You are receiving this mail because:
You are watching all bug changes.
