[Geany-devel] ANN: Configurable Build Menu Alpha in SVN

Enrico Tröger enrico.troeger at xxxxx
Mon Aug 17 21:24:18 UTC 2009

On Sun, 16 Aug 2009 15:00:18 +1000, Lex wrote:

Hey guys,

I won't respond on all details of this part of the thread due to lack
of time and more importantly because of lack of knowledge at some parts.

One comment though: a Perl dependency is not an option even not if it
were installed on 100% of all users' systems :).

>I can see that you may want to kill a long build that you started by
>accident or when you realise you forgot to do something first.  I've
>done that more than once ;-)

I guess we all had this issue already. At the time we added the Stop
button for the Run command we also tried implementing this for the Make
commands. But as you both noticed in this thread, it's not that easy. I
don't say it's not possible but it's just not as easy as it may sound.

>Due to problems on windows, builds have to be run synchronously on
>windows, ie the whole of Geany freezes while the build runs (why? I
>don't understand exactly, maybe Enrico can explain it).

I think I did explain it in
http://lists.uvena.de/pipermail/geany-devel/2009-April/000584.html. If
not, just ask again what exactly is not clear, then I'd be happy to
explain it in more detail.

>That means that cancelling a windows build can't be done from Geany

Yes, sort of. In theory it should be even easier to kill a synchronous
build but the problem is the user can't do this because the GUI is
frozen and doesn't react to any input until the build is finished. So
yes, you are right, the process can't be killed at all. Anyway, I don't
see this as a major issue as the whole synchronous build thing on
Windows is not meant to be the final way. It's more or less only a
temporary hack until someone shows up with time and/or knowledge
(ideally both) on how to do it right on Windows :).

>Whilst Linux builds are still asynchronous only one is allowed at a
>time so that output isn't mixed up in the error parser.  So all build
>commands are set insensitive until completion.  To have one menu item
>still enabled and to have it change to stop is going to be quite a bit
>of fiddling unless it is always a fixed menu item or a toolbar button.

Yes, as you say it, I'm thinking about. We actually could add a
separate Stop button for the toolbar and the Build menu, That would
obsolete a lot of not so nice code in build.c which deals with the
double action of the button. And since the toolbar is pretty easy to
configure these days, that probably would not be a big deal UI-wise.
Though I don't have a strong opinion on that. Just share your thoughts
about this, maybe in a separate new thread.


Get my GPG key from http://www.uvena.de/pub.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.geany.org/pipermail/devel/attachments/20090817/788d57d5/attachment.pgp>

More information about the Devel mailing list