Windows Movie Maker 2.6 Archive

[Rene Seiler]

Havequestions about Window Maker? If so, look no further. Below is ourcollection of Frequently Asked Questions and their corresponding answers. Manyof these have been adapted from the original FAQby Chris Green. Questions are routinely taken and added in from the mailinglists and IRC forums.

Window Maker is an X11 window manager originally designed to provideintegration support for the GNUstep Desktop Environment. In every waypossible, it reproduces the elegant look and feel of the NEXTSTEP[tm] userinterface. It is fast, feature rich, easy to configure, and easy to use. It isalso free software and part of the GNU Project, with contributions being madeby programmers from around the world

An appicon is the icon produced by an application that initially is in thebottom left corner of the screen while an application is running. For anexample, run xterm and notice the icon in the corner (make sure that you usexterm and not a default rxvt when testing, because many versions of rxvt do notproperly set their window attributes).

Window Maker has two kinds of these icons. One kind is created when anapplication - technically, a window group - is started. It represents theentire application and is called an appicon. Such icons are square tilescontaining only the picture which represents the application; they have notitles.

The second kind of icon in Window Maker is created when a particular window(possibly one belonging to an application displaying more than one window) isminiaturized (which is the same action as minimizing or iconifying inother window management models) using the miniaturization button on thewindow's titlebar. These miniaturized windows are called miniwindows and cannormally be distinguished from appicons by their small titlebar at the top ofthe tile.

The numbering scheme is relatively simple, and is in the format of threenumbers separated by dots. The first number is the "major" revision number.The second is the "minor" revision number. And finally, the third is the "patchlevel" number.

To put this all into perspective, let's examine the version number "0.65.1".This number signifies that there has not been a major revision release, thatits minor revision is newer than the previous one (0.64.x), and that it's onthe first patch level after the 0.65.0 release. This still might be confusing,so go away with this in mind: numbers ending in .0 tend to be new featurereleases but less stable than .1, .2, .3 patch level releases, the latter ofwhich are used to fix bugs.

As of WindowMaker version 0.15.0, the default setup includes .tiff icons whichrequire you to have compiled Window Maker with libtiff support. For assistanceon compiling libtiff, see the following question.

In general, you will want to ensure the latest version of libtiff is installed(see ). Typically on non-Linux systems, libtiff will belocated under /usr/local, with includes and libs in those respectivesub-directories.

Often, it will be necessary to add /usr/local/lib to the system'sLD_LIBRARY_PATH environment variable (especially so on Solaris, but see 'manld' for details on your platform). Furthermore, it is possible to supplyspecial flags to the configure script to help it find where the libraries are.An example is given below:

This should do it although I did have problems sometimes initially which Ifixed by randomly trying absolute pathes for wmaker in .xsession/.xinitrcand/or making the dtprofile/.xinitrc/etc executable. It helps logging in on theconsole (select from CDE login screen) and start X manually using "X". If itworks that way it should work when logging into the CDE environment. Rememberto Check your paths!

If it doesn't work, you can also substitute some other window manager forwmaker in the .xinitrc and see if that works. If it does you know at least that.xinitrc is getting called/executed, so your WM path is wrong or not set.

Build and install WM wherever you want, as described in Method 1. You caninstall and run WM just fine from your home directory. That's what I'm doing,since I don't have root access at work :(. Then, in your Xdefaults file in yourhome directory, add the following line:

I've been told that the difference between setting the resource and Peter'smethod is that if you override the window manager with the resouce, you stillget the CDE resources read into the resource database (so you still have yourcolor settings & such from CDE), whereas with Peter's, the CDE resourcedon't get read into the database. I don't know if this is true or not, however.Also, another thing to note with Window Maker and HP-UX 10.20 - if you select"Exit Session" from the WM root menu, WindowMaker and all of your applicationsare killed, but you may not be logged out. Again, this might be an artifactfrom my work environment, or the way I start Window Maker.

If this is necessary, it will be listed in the NEWS file included in the sourcedistribution. Since 0.15.x, the domain files have been changed in such a waythat re-running wmaker.inst is redundant. The user config files are by defaultmerged in with the global ones normally located in/usr/local/share/WindowMaker/Defaults. So, even if new options are added, theyshould be automatically added to the environment.

Most likely, the problem is that Window Maker can not find a copy of the C preprocessor in a directory such as /lib. The file /lib/cpp should be a symboliclink to whatever C compiler's cpp you are using. For example:

Assuming you installed Window Maker according to the README's that come withthe source, all you need to run Window Maker on a Solaris box is an entry inthe .xinitrc. This should work for any version. When you run wmaker.inst thefirst time, allow it to make changes to the .xinitrc file. Mine looks likethis:

Believe it or not, that's all that it takes. This, in fact, runs Window Makerinstead of OpenWindows. In order to choose Window Maker, you simply choose"OpenWindows Desktop" in the "Options - Session" Menus And Choose "CDE Desktop"if you want CDE.

First, make sure that /usr/local/lib ( or whatever directory you installedWindow Maker to) is listed in your /etc/ld.so.conf ). You need to run ldconfigso the new shared libraries will be loaded. After running ldconfig as root, thelinker should properly load the libraries. You need to run this every time youupdate Window Maker.

You need to install libtool. It also must be a libtool different from version1.2b ( shipped with redhat 5.2 ). You can get libtool from ftp.gnu.org/pub/gnuMake sure the autoconf and automake versions you have installed are at least:

First things first. As always, make sure there are not older copies of libjpegfloating around on your system. ]Some distributions by default come with an oldlibjpeg.so.1 in the /usr/X11R6/lib/ directory. This can simply be deleted. Orif something complains after you delete it, recompile it if you can to look forthe new lib in the right place, or if that fails, as a last resort, you mightadd a symlink to the new lib like so:

Now on to the error. This is basically caused by your application having beencompiled to dynamically use the libjpeg.so shared library. When you install anew lib and then try to run your program again, it expects the lib it wascompiled against, in this case the older libjpeg.so.6.0.1 and instead findslibjpeg.so.6.0.2 and reports the error.

Users have had a few problems with giflib... it seems that the install processdidn't install the header file libgif.h, so although the Window Maker configurefound the lib (libgif.so.x), when you actually try to compile, it fails when itlooks for the header to include the make. One solution is to simply copy itfrom the libgif source directory to the local system include directory.(/usr/local/include/ on many systems).

This relates to a shared memory problem on Solaris. Usually one can't see it -but it is visible if X is started from command line (or fail-safe session forthat matter). In any of the cases, on the stderr you get an error message likethis:

This one is generated by wrlib if Window Maker is compiled with shared-memoryusage enabled (which is the default). The explanation is that Solaris bydefault comes with a shared memory segment size of maximum 1 M. What happendsis that if you have a really-really cool(tm) background, it is usually muchbigger than that 1 M segment of shared memory. To see your defaults relatingthe IPC settings check the output of the "sysdef" command (look for IPC SharedMemory). There you should see the maximum allocable size for a shared memorysegment. If it is less than 5 M you should really increase it by adding thefollowing line in your /etc/system file:

If you look in there, you'll find Xresources.ow and Xsession.ow, respectively.All you need are two files that set up Window Maker (or any other windowmanager) in a similar fashion, calling them Xresources.wm and Xsession.wm (orwhichever extension you prefer).

The libPropList dependency has been removed as of Window Maker version 0.70.0,and is replaced by cleaner, more robust code in the WINGs toolkit. This newcode maintains existing proplist compatibility, so there are no visable changesfor users, and existing file formats will work as they did before.

There is now an option available to emulate appicons so that Window Maker candock just about anything now. To dock a misbehaving application, right click onthe title bar and select the attributes menu. Next, select the pull down menu's"Advanced Options" item. Under the Advanced Options menu, select theEmulate Application Icon Option then Save, Apply and close the dialog.

Emulate Appicon does exactly the same as dockit. So if Emulate Appicon does notwork, dockit will not work either. For such apps you can do nothing. They arebadly coded (they do not set the instance.class hints). For these Attributesare also not available, since attributes apply to an instance and/or classhint.

Right Click on the title bar and go to the attributes menu. Click on WindowAttributes and click the the Disable titlebar and Disable Resizebar options.Click Save, and then click Apply then close the Attributes panel.

3a8082e126