[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Re: toolbar shows up when a document is opened
From:       Dominik Haumann <dhdev () gmx ! de>
Date:       2007-10-03 10:36:33
Message-ID: 200710031236.33213.dhdev () gmx ! de
[Download RAW message or body]

On Wednesday 03 October 2007, Anders Lund wrote:
> On Wednesday 03 October 2007, Mirko Stocker wrote:
> > What exactly is missing? I mean, you can enable/disable them and, for
> > the filesystem browser at least, a configuration page appears. But I
> > noticed that the configuration doesn't seem to be saved, I have to
> > enable the plug-ins every time I restart kate.
> >
> > > part of the reason the kate app does not use KPluginSelector is that
> > > we'd have to change the interfaces in a way that is simply not
> > > acceptible.
> >
> > Ah, I think I remember a discussion about that on a mailing list some
> > time ago..
>
> Kate stores those settings in the session. So if you use anonymous
> sessions, you should allways use a specified session (the default one for
> example). If you want to store defaults for all new sessions, use
> Sessions->save as default after configuring, but note that this will also
> save the open files as part of the default session.

no, it does not save the open files anmore. they are ignored.
(to be precise, iirc: it saves the open files, but loading a new/anonymous 
session does not load it, that's the impelementation right now, was 
easiest) :)

> Complex, yes...
>
> The problem with KPluginSelector in Kate is AFAIK that it will not let us
> decide where the information is saved: A design flaw.


_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]