GNOME Bugzilla – Bug 430099
image paths are confusing at best
Last modified: 2009-01-21 08:01:12 UTC
A bug has been reported in the Debian BTS by Igor Stroh: http://bugs.debian.org/211179 "try to define a path to a window icon in the property box if GtkWindow. You can choose a file in a "File Select" dialog, but then, only the name of the icon (not the relative or absolute path) is set as attribute for the pixmap. So if all your images recide in /usr/shar/pixmap/<progname> you'd have to patch your .glade file and adjust the path manually." It's one of the oldies, as well. I'd go a bit farther, and say that the way we specify image paths is confusing, and sub-optimal; perhaps glade/libglade should work out some way of having an 'image loading' path-list, which the program code (through the build system) and/or the glade file could then control?
I support this report. I'm considering only the absolute/relative paths issue. Reasons: - They should be kept by the editor and saved in the glade file, as long as the file format supports it. - This is a productivity impediment for some types of workflows.
I should have closed this, recently in trunk I added a filechooser dialog that opens at the project's resource directory (the prefs dialog lets you set the directory which is the same as the glade file for default), this will result in a base name property, useful for the average use case at least, the power user can still edit the full or relative path manually in the entry and only the basename will be used to load from the project resource directory in the glade runtime (i.e. the real property path is only meant to be used in the target application). Please feel free to re-open this if you find there are remaining issues ... (I would like to add a completion to the entry for instance...)