OK, let's start with the most simple case.* Output: *See attached file
1. Plasma starts up with *activity A* on *left screen* and *activity B*on *right* (main) *screen*. 2. Zoom out on *left screen.* (Notice: the activities are shown as [B][A], and not [A][B] as one would expect.) 3. Chose *activity B* to zoom in on *left screen*. Now you have the same activity (*B*) on both screens. At this point the Plasma feels broken: changing activity on one screen doesn't work and and some cashews disappear when I try to add activities and zoom in/out. Do you want plasma output beyond this point too? 2008/12/10 Aaron J. Seigo <[EMAIL PROTECTED]> > On Tuesday 09 December 2008, Hans Chen wrote: > > Hi Michael, > > > > It's perfectly OK me. > > > > -- > > > > *Aaron*: I've played around a bit and found that it works pretty good in > > trunk - except when I set the same activity to both screens. > > > ah, that shouldn't be possible. it *should* result in the activities > trading with each other. > > > > Afterwards I > > get the same issue as I described before (at the moment I can't change > > activity on either screen through the ZUI). > > > yes, that would be expected if both screens have the same activity > > > > Do you want some plasma outputs? Should I describe exactly what I do, or > is > > a log sufficient? > > > both please. =) > > > -- > Aaron J. Seigo > humru othro a kohnu se > GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 > > > KDE core developer sponsored by Qt Software > > > > _______________________________________________ > Plasma-devel mailing list > Plasma-devel@kde.org > https://mail.kde.org/mailman/listinfo/plasma-devel > >
plasma.log
Description: Binary data
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
