On Saturday, September 25, 2010, Marco Martin wrote:
> uhm, removing a containment in locked mode seems really uhm, wrong.
> from an interaction point of view would make sense to forbid removal of
> virtual desktops at all when locked, even if is not a directly plasma
> related thing and technicall
On Saturday, September 25, 2010, Chani wrote:
> how would this affect the "do you want to delete all the extra
> containments?" question when PVD is disabled?
it probably suffers the same problem :)
--
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB
On Friday 24 September 2010, Aaron J. Seigo wrote:
> On Friday, September 24, 2010, Chani wrote:
> > and while one may question whether deleting should be allowed while
> > locked, stopping while locked makes perfect sense.
>
> so i just ran across a related issue today on b.k.o[1]: when a new des
On September 24, 2010 20:41:47 Aaron J. Seigo wrote:
> On Friday, September 24, 2010, Chani wrote:
> > and while one may question whether deleting should be allowed while
> > locked, stopping while locked makes perfect sense.
>
> so i just ran across a related issue today on b.k.o[1]: when a new d
On Friday, September 24, 2010, Chani wrote:
> and while one may question whether deleting should be allowed while locked,
> stopping while locked makes perfect sense.
so i just ran across a related issue today on b.k.o[1]: when a new desktop or
a new screen comes or goes, containments will get ad
On Friday 24 September 2010, Chani wrote:
> On September 24, 2010 14:51:54 Marco Martin wrote:
> > On Friday 24 September 2010, Chani wrote:
> > > what we're going to do about this in trunk: the code for the activity
> > > stopping will be moved into Corona under a name like exportLayout (to
> > >
On September 24, 2010 14:51:54 Marco Martin wrote:
> On Friday 24 September 2010, Chani wrote:
> > what we're going to do about this in trunk: the code for the activity
> > stopping will be moved into Corona under a name like exportLayout (to
> > mirror importLayout). it won't actually know about a
On Friday 24 September 2010, Chani wrote:
> what we're going to do about this in trunk: the code for the activity
> stopping will be moved into Corona under a name like exportLayout (to
> mirror importLayout). it won't actually know about activities, it'll just
> know that a certain bit of config n
[this is a summary of an irc discussion today...]
so, I finally found out how to reproduce the elusive activity-duplication bug.
:)
it happens when plasma is locked: stopping the activity copies its config out
to a separate file, then tries to remove it from plasma-desktop-appletsrc, but
Applet:
