(Sending a copy also to the gtk-app-devel-list. Please keep discussions that start on a public mailing list public unless you specifically have private personal or confidential matters to discuss in some messages.).
> I just found libwimp.dll off in some subfolder, but I don't think I added > that folder to my path, therefor it wasn't loaded at runtime. You have misunderstood. You don't need to add the "some subfolder" where libwimp.dll or other theme engines are to PATH for them to be found when required. Note the "when required". I.e., when your gtkrc file tells GTK+ to use a theme that uses such an engine. The gtk-theme-name line in the gtkrc file points GTK+ to *another* gtkrc file, in share/themes/<theme name>/gtk-2.0/gtkrc , which then contains lots of settings for the theme, and an "engine" line that tells the name of the engine module (DLL) to load. GTK+ knows where the engine modules are. > Initially I thought I only had to add ./bin, which would explain the lack of > "theme". No, you don't necessarily have to have the bin folder (where the GTK+ stack "normal" DLLs, i.e. those used by applications, are). If you run an executable that is located in the same bin folder (like gtk-demo.exe or your own executable you have copied into the same folder), it will find its DLLs. --tml _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
