On Mon, 10 Dec 2007 03:42:04 am Vladimir Prus wrote:
> On Sunday 09 December 2007 19:09:59 Hamish Rodda
wrote:
> > SVN commit 746588 by rodda:
> >
> > Initial working version of model/view based
variable viewer.
> > - ported to model/view: new class
VariableCollection, owned by the
> > controller, doubles as the model - new abstract
base class
> > AbstractVariableItem replaces TrimmableItem -
reworked implementations of
> > subclasses; moved MI command requests into
subclasses + away from viewing
> > widget - currently disabled special views for
variables like QString; I
> > plan to create a new interface for special view
plugins to be able to
> > make this much more customizable (including things
like easy access to
> > items in Qt's tulip classes)
> >
> > Current breakage includes:
> > - a new toplevel item is created for each
thread/frame. It seems to be a
> > feature of the previous code that got removed -
was this accidental or
> > not? Anyway, still need to make the latest frame
auto-expand
>
> If I understand correctly, that was a feature. If you
expand some variables
> in frame 0, go to frame 1, and then go to frame 0
again, you expect the
> tree state to be the same.
Yes, but in kdev3 as far as i remember, we just clear the
"locals" entry and
replace it... so now should i add a new frame entry and
expand + set focus on
that?
Cheers,
Hamish.
_______________________________________________
KDevelop-devel mailing list
KDevelop-devel kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel
|
