Thanks, I'll look into what they did


On 10 September 2013 01:55, Weng Xuetian <wengxt@gmail.com> wrote:
As far as I remember KDevelop used to have same problem but now they fixed it?

If you want to keep the splash screen you can check their code.


On Sat, Aug 31, 2013 at 7:36 AM, David Faure <faure@kde.org> wrote:
On Sunday 11 August 2013 01:32:09 Lindsay Mathieson wrote:
> On Sat, 10 Aug 2013 12:45:35 PM Lindsay Mathieson wrote:
> > I'm trying to add session restore to kleopatra and am completely stuck on
> > it.  The appropriate functions are being called but it appears to be
> > passed
> > the wrong session id each time.
>
> Figured out the problem - weirdly enough it was kleopatra's splash screen.
> Showing the splash screen caused KApplication::saveState(...) to be invoked,
> which forces a new session Id to be generated.
>
> Not a fan of splash screens myself - always obscuring things at the wrong
> moment. Anyone mind if I just remove it?

It's indeed not very common in KDE applications.
I wouldn't mind if it went away.
You even found a technical reason to do that :-)

--
David Faure, faure@kde.org, http://www.davidfaure.fr
Working on KDE, in particular KDE Frameworks 5


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<



>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<




--
Lindsay