[kontact] [Bug 362281] Kontact and kmail share New mail shortcut

[Andre Woebbeking]

https://bugs.kde.org/show_bug.cgi?id=362281

--- Comment #3 from Andre Woebbeking  ---
Daniel you made my day :-)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 362281] Kontact and kmail share New mail shortcut

[Daniel Vrátil]

https://bugs.kde.org/show_bug.cgi?id=362281

Daniel Vrátil  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  ---
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-1src/kmkernel.cpp
M  +1-1src/kmmainwidget.cpp

https://commits.kde.org/kmail/3033e8b58fe41d5911320599710b05e124e23cf6

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 362281] Kontact and kmail share New mail shortcut

[Denis Kurz]

https://bugs.kde.org/show_bug.cgi?id=362281

Denis Kurz  changed:

   What|Removed |Added

 CC||kde...@posteo.de
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
Version|unspecified |5.5.1

--- Comment #1 from Denis Kurz  ---
This is still an issue in 5.5.2. Although I cannot test with a completely fresh
configuration right now, I also get the ambiguity warning. However, the
"Configure shortcuts" dialog does not show any Ctrl+N shortcuts for the
Kontact. Only the KMail2 component contains the "New Mail" -> Ctrl+N shortcut.
So the only way for me to resolve the conflict is to remove the shortcut from
KMail, but then it wouldn't work any more in standalone KMail.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 362281] Kontact and kmail share New mail shortcut

[Andre Woebbeking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362281

Andre Woebbeking  changed:

   What|Removed |Added

 CC||woebbek...@kde.org

-- 
You are receiving this mail because:
You are the assignee for the bug.