yeah, u're right, always visible debug tabs make it hard to tell if the debugger running or not. but, if you are not on the debugger page, i.e. don't see it, you also can't guess what is going on, and the second reason for make them persistent was a bug when after several run/stop actions VTE stopped displaying input or output characters. Now I realized that it was not about it, probably it's better to change things back. As to showing debugger state, I was thinking of a toolbar button with Run or Stop image, based on debugger state, or how is itr done in most IDEs?
On Sun, 30 Jan 2011 18:40:55 +0200 Dimitar Zhekov <dimitar.zhe...@gmail.com> wrote: > On Sun, 30 Jan 2011 18:05:51 +0300 > Alexander Petukhov <alexander.petuk...@mail.ru> wrote: > > > need more bug reports/feedbacks to make it more stable. > > As of revision 36: > > Shows all tabs always, so I can't easily tell when a program is > running (Browse and Debugger in the Target tab are disabled, so there > is some indication). > > Applies the debug vertical scroll policy on Geany startup. > Interestingly, when Geany is started and debugger is activated after > that, the standard policy remains, even when debugging. > > -- > E-gards: Jimmy > _______________________________________________ > Geany-devel mailing list > Geany-devel@uvena.de > http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel > -- Alexander Petukhov <alexander.petuk...@mail.ru> _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
