Before 00c261652e the menu item icon
was always an ImageClass name.
After changing this to be a file name some themes defining menus
(e.g. Ganymede with button tweaks) did not work as intended wrt. button
menus.
So now we accept both.
Has been disabled by default for 5 years.
- Remove autofoo stuff.
- Unifdef ENABLE_TRANSPARENCY and ENABLE_THEME_TRANSPARENCY.
- Remove transparency settings from docs/e16.xml.
A .theme file is really the same as the usual .etheme file (i.e.
a tarball of the theme files, compressed or not), except that .theme
files may contain themes for multiple applications.
The difference in the handling of a .theme file is only the location
where it is extracted.
A normal theme file, say FOO.etheme (or FOO.tar, FOO.tar.gz, FOO.blah),
is (normally) extracted to ~/.e16/themes/FOO/.
e16 now expects the theme files to be located in
~/.e16/themes/FOO/*.cfg or ~/.e16/themes/FOO/e16/*.cfg.
A .theme file, e.g. FOO.theme, is extracted to ~/.themes/FOO/.
e16 now expects the theme files to be located in
~/.themes/FOO/*.cfg or ~/.themes/FOO/e16/*.cfg (the first one
should probably never be used, but it's how it works).
In order to find this new theme path it is added to the default theme
search path.
Suggested by Don Harrop.
Apparently, when using XShmGetImage to get an XImage for a window,
the image no longer includes subwindows (like when using
IncludeInferiors in GC).
When using XGetImage the XImage still includes subwindows.
Changing EImageGrabDrawable() to EImageGrabDrawableScaled() means that
we use imlib_create_scaled_image_from_drawable() instead of
imlib_create_image_from_drawable().
imlib_create_scaled_image_from_drawable() is implemented in such a way
that the drawable to be grabbed is always copied to a pixmap first.
At least in initially shaded SHADE_RIGHT pagers the client window would
be placed at a non-zero y offset in the container.
Not sure exactly why but this (WestGravity -> NorthWestGravity) fixes it.
The other cases got a similar treatment mostly because it seemed right.