> On 2008-09-05 07:53:09, Aaron Seigo wrote: > > good idea; however, i think a better approach would be to have a > > contextChanged(Plasma::Context*) signal, and then do connect(d->context, > > SIGNAL(contextChanged(Plasma::Context*)), this, > > SLOT(contextChanged(Plasma::Context*)));?
ok, done. but since this exposes the context instance wouldn't be the same simply make a getter for the context? or the context instance itself can change? - Marco ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard.vidsolbach.de/r/176/#review159 ----------------------------------------------------------- On 2008-09-05 11:19:45, Marco Martin wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviewboard.vidsolbach.de/r/176/ > ----------------------------------------------------------- > > (Updated 2008-09-05 11:19:45) > > > Review request for Plasma. > > > Summary > ------- > > this is the first time i try to scratch my itch with activity and context > stuff, so probably could be not the right approach(tm) > this adds a signal to the containment that notifies the activity has changed, > since i think could be useful tools that displays activities > i made this thing for activitybar in playground, that displays all the > containments in a tabbar for quick switching, so i need a way to sync the > name with the text on tabs. > a way could be this signal, or perhaps directly accessing the context object > fron the containment? > > > Diffs > ----- > > /trunk/KDE/kdebase/workspace/libs/plasma/containment.h > /trunk/KDE/kdebase/workspace/libs/plasma/containment.cpp > > Diff: http://reviewboard.vidsolbach.de/r/176/diff > > > Testing > ------- > > > Thanks, > > Marco > > _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
