------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=150087
------- Additional Comments From bluedzins wp pl 2008-06-27 15:29 -------
Nope, because internal implementation should not affect the user experience.
Composer for me is not standalone application, it is just part (sub-component)
of KMail. It is as good as settings window, or about, or find.
It is good you can switch between KMail-Composer-Konq. but Konq is not part of
KMail, Composer is.
When I am done with find/settings/about I expect to be in KMail. The same
expectation is for Composer.
Btw. I can tell from my experience, that I never was in such situation that
switching to Konq. instead of Kmail was a tiny bit useful or intuitive (even)
for me. Because I have this notion in mind "hey, I am editing mail, I use
Kmail, send, oh, why I am in Konqueror now?".
In short -- the fact Composer is the biggest and most elaborate window of all
Kmail windows, does not change the fact that when it is called from within
KMail it is treated as KMail sub-component.
_______________________________________________
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
