Review Request: Don't save/restore active area across restarts
apaku at gmx.de
Mon Jan 23 21:03:52 UTC 2012
On 23.01.12 19:40:14, Niko Sams wrote:
> > On Jan. 22, 2012, 9:09 p.m., Andreas Pakulat wrote:
> > > I disagree, at least for the review-area. Maybe its ok if the review area is not needed anymore (i.e. the patch is comitted, no local changes anymore), but then the user would've ended up in the code area anyway before closing kdevelop.
> > >
> > > Maybe for the debug area kdevelop should rather start the debugee(s) that where left running again?
> > Aleix Pol Gonzalez wrote:
> > Hm... well for my perspective, these areas are places where you go to. Likewise, I never go from debug -> commit (even though it's possible).
> > Also I think it's not possible to restore the Patch Review state at the moment, so if you restore to Review, you get quite a useless screen (yes, I understand this patch is not fixing this, but it's a collateral effect).
> > I think Niko's change makes sense. I wouldn't put it in 1.3 though, sounds more like a wish to me.
> Restoring as much as possible on restart is good. But restoring the debugger is impossible. Starting the debugee again could be done but would be to me - as a user - confusing if not irritating (what if the debugee triggers some unwanted action?)
> If restoring the review is possible I don't know. Also think about changed repositories, ie. when the users commited changes outside kdevelop.
Ok, so there's no restoring of area when restarting kdevelop and while
using kdevelop there's the suggested workflow Code -> Debug -> Code and
Code -> Review -> Code. Makes me wonder wether there's a reason to
manually switch the areas at all. Hmm, I guess to exit out of the review
area, but for the debug-workflow I don't really see a necessity for that
More information about the KDevelop-devel