On Thu, 6 Dec 2007 12:24:37 -0300, "Diego Jacobi" jacobidiego@gmail.com wrote:
Hi,
I downloaded the file: http://files.uvena.de/geany/geany-0.13svn_r2091_win32.zip and the build menu was disabled with a previously opened project ( with only a main.c file ). I have to open the main.c to compile it and run it.
Was the main.c opened when starting Geany or was only the project loaded without any opened files?
In Project properties, to choose the file to be run (it shoulnd't be necessary becouse when compiling the output file should have the project name) it opens a windows open-dialog behind the
No, I don't agree. Project name and executable filename are two different things.
properties-dialog and makes some drawing problems when moving the open-dialog. Also it starts with a filter to geany-project-files and it should be all files to select a .exe file.
Yes, this is a bug and will be fixed soon. Thanks. I'll also have a look at the problem of opening dialogs behind others. This happens also sometimes with the file open dialog on Windows.
Second, the open, save, paths-selection, etc. dialogs are gtk'd dialogs, i think that there should be some uniform design and in my opinion if you could make all of it as windows dialogs it will be easier and cleaner for a windows user, becouse gtk'd dialog are too diferent to windows dialog and doesn't look or adapt so well as in linux. An example. A gtk dialog can not follow shortcuts.
Please read the manual. There were the default Windows dialogs for a long time but we changed back to default GTK dialogs because there is no way(at least I don't know it) to add custom widgets to a Windows file open/save dialog. When using the Windows dialogs, all additional features of Geany's open/save dialogs are lost. If you really need them, compile Geany from source and set GEANY_USE_WIN32_DIALOG to 1 in src/geany.h (see http://geany.uvena.de/manual/index.html#compile-time-options)
Third, when compiling or running a python scripts, it needs to be on the path, but the python installer doesn't place it on the path. So, there are 3 options:
- tell to place the python folder on the windows path.
- ask for the python folder in some config dialog.
Open Build->Set Includes and Arguments and then adjust the Execute field to the path to your python executable as necessary.
- ask to the OS where is python installed automatically.
How to do that? Doesn't the $PATH variable exist exactly for that reason?
Regards, Enrico