Re: [anjuta-devel] Installed gtk+-3.2... Some problems



Hi John,


Le 11/11/2011 07:08, John Coppens a écrit :
I don't think so (Johannes suggested the same problem). I checked the
dates of all the plugins, and they correspond to the compilation
date/time. These are the autotools-related files left
in /usr/lib64/anjuta (anjuta was compiled with --prefix=/usr
--libdir=/usr/lib64):

anjuta-build-basic-autotools.plugin
libanjuta-build-basic-autotools.la
libanjuta-build-basic-autotools.so

Anjuta is looking for .plugin file in $(libdir)/anjuta and in the directories listed in GNOME2_PATH environment variable.

Then anjuta-build-basic-autotools.plugin is not the autotools backend plugin but the build plugin. The autotools backend plugin is named am-project.plugin.

You could search for the string autotools or backend in all files with the .plugin extension to see if you haven't another autotools plugin with a different name. I think the old backend was named like gbf something.


I suggest that the button should have another caption - maybe 'Close
editor', or 'Close editor too' (or even 'Discard'). 'Delete' feels
contradictory to the message in the dialog that the file is already
deleted. I know it is just a semantic, but 'Delete' doesn't feel right.

Yes, I'm agree that 'Delete' is not completely right but I don't know what is the best replacement. 'Close' matches better the action but you can loose some data by using it, so 'Discard' is probably better.


Regards,

Sébastien



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]