ghost at cs.msu.su
Mon Dec 19 18:08:42 UTC 2005
On Friday 16 December 2005 11:14, Robert Gruber wrote:
> > And actually, why do you need to first communicate state to
> > gdbcontroller,
> > then check it in gdbcontroller?. Would not modifying
> > variableTree::slotCurrentFrame from:
> As far as our baseclass DbgController explicitly supports a state where no
> locals will be retrieved I thought why not using it!?!
> If you prefer not to use it, I'll be glad to change it.
> But if so, we should consider removing this state (s_viewLocals) at all.
> Until my commit yesterday it has been checked by GdbController but has
> never been activated at all.
I think removing s_viewLocals completely will be a good idea. The problem with
the current design is that gdbcontroller is too smart and is in charge of
everything which makes it complex. That's why I think it's better to move
more logic out of it into specific view classes.
More information about the KDevelop-devel