KDevelop UI states

David Nolden david.nolden.kdevelop at art-master.de
Fri Jul 24 10:07:47 UTC 2009


Am Freitag 24 Juli 2009 12:00:25 schrieb David Nolden:
> Am Freitag 24 Juli 2009 11:30:23 schrieb Andreas Pakulat:
> > > I've played around with the sessions widget a bit, and I couldn't get
> > > it to do what I want. How can I load another session?
> >
> > Just make it active and then close and re-open kdevelop. I'm not sure
> > right now wether I just delayed loading it directly in the running
> > instance or wether its not possible to do that.
>
> Isn't it planned to allow switching the session on-the-fly? If we want this
> to be convenient, then it has to be easier then that. Although it is not a
> bad thing to start a new kdevelop instance, so maybe we should just start a
> new instance with the selected session, and close the current instance,
> when a session is picked.

Actually having one fixed session for each KDevelop instance would allow 
binding the .kdevduchain/X instance directory to it, or maybe even directly 
putting the duchain directory into the session directory. Then we should allow 
each session to be opened only within one KDevelop instance at a time, and 
advertise the sessions a bit more, then we would have solved an important 
duchain problem (.kdevduchain/X directory getting too large because too many 
different projects share it).

Greetings, David





More information about the KDevelop-devel mailing list