On Friday 18 April 2014 13:52:20 Martin Klapetek wrote: > Hey, > > if there's no plasma config existing, plasma is run for the first time in a > multi-screen env, should plasma create a (default) panel on each screen?
thinking out load: if plasma is without config and started in a multi-screen env that means it's also for kscreen the first time. How does kscreen handle this case? Start in clone mode or in extended? If it starts in clone mode it's kind of awkward if the user changes to extended and another panel is created. Maybe even make it difficult to notice whether the command succeeded - still looks like cloned. If it starts expanded then there's also the possibility that the user might think it's cloned because both screens look the same. On the other hand having two screens and only a panel on one might seem unpolished. Do we really need all of what is in the panel on both screens? Do we need two launchers? Maybe not. Do we need two tasks applets? if it shows different tasks per screen: yes. Do we need to systrays? Rather no. Do we need two clock? Could be handy. So maybe different configuration per panel makes sense? Cheers Martin
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
