Review Request: Don't save/restore active area across restarts
Andreas Pakulat
apaku at gmx.de
Sun Jan 22 21:09:05 UTC 2012
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/103764/#review10010
-----------------------------------------------------------
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?
- Andreas Pakulat
On Jan. 22, 2012, 5:07 p.m., Niko Sams wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/103764/
> -----------------------------------------------------------
>
> (Updated Jan. 22, 2012, 5:07 p.m.)
>
>
> Review request for KDevelop.
>
>
> Description
> -------
>
> Areas are used in a workflow:
> - debugging
> - commiting/patch reviewing
> and kdevelop switches automatically to that area (and back)
>
> Now when I have a running debug session (and debug area is opened) and I quit kdevelop, it will remember debug as active area and restore it on start.
>
> That doesn't make much sense in the way areas are used now, so my patch removes that functionality.
>
> ...ok to go into 1.3?
>
>
> Diffs
> -----
>
> shell/uicontroller.cpp 2091fdf
>
> Diff: http://git.reviewboard.kde.org/r/103764/diff/diff
>
>
> Testing
> -------
>
>
> Thanks,
>
> Niko Sams
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20120122/d2f6c437/attachment.html>
More information about the KDevelop-devel
mailing list