Bug 68015: Variables/Watch Window closes on first view
ghost at cs.msu.su
Fri May 20 10:15:08 UTC 2005
On Friday 20 May 2005 12:10, jbb wrote:
> > 1. Opening a tree item in framestack view does not switch current frame
> > and does not switch shows source file.
> > 2. Only explicit selection of a frame in framestack view changes current
> > frame, and shows the source.
> > 3. The variables view should show only variables in the current frame.
> 1 and 2 sound good to me.
> Is 3 an improvement? Well, yes, it probably is :-)
It either way, (3) is independent from the rest of my suggestions.
> > If point 3) is not OK, then at least the variables view can be modified
> > to not switch stack when opening item corresponding to frame.
> > Opinions?
> > I think this can be implemented by making variables and framestack widget
> > emit some other (new) signals, not 'slotSelectFrame'. Currently,
> > slotSelectFrame does many jobs -- it's switches the frame for showing the
> > frame in source view, it produces backtrace, and it produces info about
> > local vars. If more specific 'slotShowBacktrace' is introduced, we can
> > avoid accidental switching to different frame in source view.
> Does anybody disagreed that this should be done?
No, was it proposed previously.
> > - Volodya
> Would you like to attempt this?
Sure, I plan to code this.
More information about the KDevelop-devel