| blob | 4df3dc79cec05dac5df1934d81663451f269dce0 |
21 <?
24 ?>
28 <p>Have questions about Window Maker? If so, look no further. Below is our collection of Frequently Asked Questions and
30 "http://web.archive.org/web/20030401182339/http://www.dpo.uab.edu/~grapeape/wmfaq.html">original FAQ</a> by Chris
52 <?
53 }
55 ?>
67 <B>1.10</B> <A href="#39">What is the difference between appicons, mini-windows, and minimized applications?</A><BR>
68 <B>1.11</B> <A href="#126">How do I make sense of Window Maker's version number scheme?</A><BR>
69 </UL>
70 <BR><HR><BR>
71 <A name="30"></A>
72 <h2>1.1 What is Window Maker?</h2>
73 Window Maker is an X11 window manager
74 originally designed to provide integration
75 support for the GNUstep Desktop Environment.
76 In every way possible, it reproduces the
77 elegant look and feel of the NEXTSTEP[tm]
78 user interface. It is fast, feature rich,
79 easy to configure, and easy to use. It is
80 also free software and part of the GNU
81 Project, with contributions being made by
82 programmers from around the world
83 <A name="31"></A>
84 <h2>1.2 Where can I get Window Maker?</h2>
85 Window Maker can be obtained from the
86 official website, http://windowmaker.org/,
87 or from various mirror sites listed at
88 http://windowmaker.org/mirrors.html
89 <A name="32"></A>
90 <h2>1.3 Where are the mailing lists and archives?</h2>
91 All information regarding the Window Maker
92 mailing lists can be found at http://windowmaker.org/lists.html
93 <A name="33"></A>
94 <h2>1.4 Where can I find more documentation?</h2>
95 Additional documentation can be found in
96 the Window Maker source distribution, or
97 at http://windowmaker.org/documentation.html
98 <A name="34"></A>
99 <h2>1.5 What is an appicon?</h2>
100 An appicon is the icon produced by an
101 application that initially is in the
102 bottom left corner of the screen while
103 an application is running. For an example,
104 run xterm and notice the icon in the
105 corner (make sure that you use xterm and
106 not a default rxvt when testing, because
107 many versions of rxvt do not properly set
108 their window attributes).<BR><BR>
110 For a more indepth discussion of how an
111 appicon relates to Window Maker, see
112 question 1.10
113 <A name="35"></A>
114 <h2>1.6 How can I get a question added to the FAQ?</h2>
115 For now, the best method is to E-mail your
117 working on a web-based submission form
118 to our FAQ system, which will enable
119 users to submit questions for review.
120 <A name="36"></A>
121 <h2>1.7 How do I report bugs?</h2>
122 You can look at the BUGFORM file in
123 the source distribution of Window Maker.
124 Alternatively, you can use the
125 Window Maker Bug Tracker at
126 http://windowmaker.org/cgi-bin/bugs
127 <A name="37"></A>
128 <h2>1.8 Is there an anomymous cvs server?</h2>
129 Yes there is. To check out from cvs, first
130 <P>
131 <PRE>
133 cvs login
134 </PRE>
135 There is no password, so simply hit enter when prompted.
136 <P>
137 Then issue the following command ("wm" is the name of the module):
138 <P>
139 <PRE>
140 cvs -z3 checkout -d WindowMaker wm
141 </PRE>
142 To update your source tree, cd to the WindowMaker directory and type
143 <P>
144 <PRE>
145 cvs -z3 update -dP
146 </PRE>
147 inside the WindowMaker directory.
148 <P>
150 For more detailed CVS instructions, please
151 visit http://windowmaker.org/development-cvs.html
152 <A name="38"></A>
153 <h2>1.9 Where can I find the Window Maker IRC channel?</h2>
154 The official Window Maker IRC channel can be accessed by connecting to irc.windowmaker.org on port 6667,
155 and joining #WindowMaker
157 <A name="39"></A>
158 <h2>1.10 What is the difference between appicons, mini-windows, and minimized applications?</h2>
159 Thanks to Jim Knoble for this answer:
160 <P>
161 Many window managers are capable of turning large windows into
165 Window Maker has two kinds of these icons. One kind is created when
168 icons are square tiles containing only the picture which represents
169 the application; they have no titles.
170 <P>
171 The second kind of icon in Window Maker is created when a particular
172 window (possibly one belonging to an application displaying more than
175 the miniaturization button on the window's titlebar. These
177 distinguished from appicons by their small titlebar at the top of the
178 tile.
181 The numbering scheme is relatively simple,
182 and is in the format of three numbers separated
183 by dots. The first number is the "major" revision
184 number. The second is the "minor" revision number.
185 And finally, the third is the "patch level" number.
186 <P>
187 To put this all into perspective, let's examine the
189 that there has not been a major revision release,
190 that its minor revision is newer than the previous
192 after the 0.65.0 release. This still might be
193 confusing, so go away with this in mind: numbers
194 ending in .0 tend to be new feature releases
195 but less stable than .1, .2, .3 patch level releases,
196 the latter of which are used to fix bugs.
197 <P>
198 It is generally safe to go with the highest numbered
199 patch release.
201 <?
202 }
204 ?>
206 <h1>Chapter 2: Installing Window Maker</h1>
207 <UL type="disc">
208 <B>2.1</B> <A href="#41">Why are no icons showing up after installing Window Maker?</A><BR>
209 <B>2.2</B> <A href="#42">How do I make Window Maker link against libtiff?</A><BR>
210 <B>2.3</B> <A href="#44">How do I switch CDE's window manager to use WindowMaker?</A><BR>
211 <B>2.4</B> <A href="#46">Do I need to rerun wmaker.inst with every new version of Window Maker?</A><BR>
212 <B>2.5</B> <A href="#47">Why am I only getting a root menu with xterm and exit items?</A><BR>
213 <B>2.6</B> <A href="#48">How do I get Window Maker to use more than 16 colors on my SGI Indy Workstation?</A><BR>
216 <B>2.9</B> <A href="#52">How do I fix an error such as libwraster.so.1: cannot open shared object file?</A><BR>
217 <B>2.10</B> <A href="#53">How do I fix an error dealing with aclocal: configure.in: 15: macro 'AM_PROG_LIBTOOL' not found in library?</A><BR>
218 <B>2.11</B> <A href="#55">When I run wmaker, it quits complaining about '__register_frame_info'</A><BR>
222 <B>2.15</B> <A href="#59">How do I make giflib or libungif to link against Window Maker?</A><BR>
223 <B>2.16</B> <A href="#60">How do I fix an error similar to "wrlib: could not allocate shared memory segment: invalid argument"</A><BR>
224 <B>2.17</B> <A href="#61">How do I add Window Maker to the Solaris dtlogin screen?</A><BR>
236 Many UNIX operating systems have
237 difficulty finding third party libraries
240 them all.
242 In general, you will want to ensure the
245 systems, libtiff will be located under
250 to the system's LD_LIBRARY_PATH environment
252 for details on your platform). Furthermore,
253 it is possible to supply special flags to the
254 configure script to help it find where the libraries
255 are. An example is given below:<BR>
256 <P>
257 <PRE>
258 ./configure --with-libs-from="-L/usr/local/lib" \
259 --with-incs-from="-I/usr/local/include"
260 </PRE>
262 <P>
263 Also, you will want to make sure you're using GNU make
267 Method 1:
268 <P>
269 Peter Ilberg gives us this answer:
270 <P>
271 Install WM wherever you want it, mine is in /opt/WindowMaker-0.16.0 (eg. use
272 ./configure --prefix=/opt/WindowMaker-0.16.0). Run the install script wmaker.inst in
273 your home directory.
274 <P>
275 Add the following two lines to .dtprofile in your home directory:
276 <P>
277 <PRE>
278 SESSIONTYPE=xdm; export SESSIONTYPE
280 </PRE>
281 This tells CDE to go looking for an .xinitrc/.xsession instead of using the default
282 environment.
283 <P>
284 Make your .xsession/.xinitrc executable (VERY IMPORTANT, wmaker.inst did NOT
285 do this automatically for me) using eg.
286 <P>
287 <PRE>
288 chmod ugo+x .xsession
289 </PRE>
290 Your .xsession/.xinitrc should look something like this:
291 <P>
292 <PRE>
293 #!/bin/sh
294 </PRE>
295 <PRE>
296 <some other init stuff that you want/need>
297 </PRE>
298 <PRE>
299 exec wmaker
300 </PRE>
303 This should do it although I did have problems sometimes initially which I fixed by
310 the .xinitrc and see if that works. If it does you know at least that .xinitrc is getting
311 called/executed, so your WM path is wrong or not set.
312 <P>
313 Method 2:
314 <P>
315 Thomas Hanselman gave this alternative answer (via Peter Ilberg):
316 <P>
317 Build and install WM wherever you want, as described in Method 1. You can install
320 the following line:
326 Nortel thing), you should be in Window Maker heaven ;).
327 <P>
328 Difference between the methods: (according to Thomas)
329 <P>
331 that if you override the window manager with the resouce, you still get the CDE
332 resources read into the resource database (so you still have your color settings &
338 start Window Maker.
340 Owen Stenseth adds:
342 When using this method it is possible to exit Window Maker cleanly by using the
346 "Exit Session" EXEC dtaction ExitSession
349 The only problem I have at the moment is I seem to get multiple copies of asclock
350 running when I log in again.
353 Dan Pascu reveals the answer:
356 file included in the source distribution.
360 merged in with the global ones normally located
363 be automatically added to the environment.
366 Most likely, the problem is that Window Maker can not find a copy of the C pre
368 whatever C compiler's cpp you are using. For example:
369 <P>
370 <PRE>
371 cpp -> /usr/bin/cpp-2.95*
372 </PRE>
373 Another possibility is your /usr/X11/lib/X11/xinit/xinitrc is a
374 broken symlink. Either create a new symlink, or do something like:
375 <P>
376 <PRE>
377 $ cp /usr/X11/lib/X11/xinit/xinitrc.fvwm2 \
378 /usr/X11/lib/X11/xinit/xinitrc.wmaker
379 </PRE>
380 <PRE>
381 $ ln -sf /usr/X11/lib/X11/xinit/xinitrc.wmaker \
382 /usr/X11/lib/X11/xinit/xinitrc
383 </PRE>
386 most probably the very last line).
387 <P>
388 Thanks to Tomas Szepe for the second part.
389 <A name="48"></A>
390 <h2>2.6 How do I get Window Maker to use more than 16 colors on my SGI Indy Workstation?</h2>
391 Thanks to Peter H. Choufor this answer:
392 <P>
393 By default, the SGI X Server uses 8-bit Pseudocolor mode.
394 To change it, edit (as root) the file /usr/lib/X11/xdm/Xservers.
395 Change it to read:
396 <P>
397 <PRE>
398 :0 secure /usr/bin/X11/X -bs -c -class TrueColor -depth 24
399 </PRE>
400 <A name="49"></A>
401 <h2>2.7 Using WindowMaker with Solaris 2.6 CDE</h2>
402 Thanks to Rob Funk for this answer:
403 <P>
404 Assuming you installed Window Maker according to the README's that come
405 with the source, all you need to run Window Maker on a Solaris box is
411 #!/bin/sh
412 # Window Maker Default .xinitrc
416 instead of OpenWindows. In order to choose Window Maker, you simply choose
417 "OpenWindows Desktop" in the "Options - Session" Menus And Choose "CDE
418 Desktop" if you want CDE.
419 <P>
420 The color schemes and settings for Window Maker are seperate from CDE.
421 I tested on a SPARC 10, but I assume Solaris x86 would work also.
422 <P>
423 (webmaster note: It works fine on Solaris x86)
424 <A name="51"></A>
425 <h2>2.8 How do I install Window Maker on a Solaris box?</h2>
426 Here are some hints from John Kemp:
427 <P>
428 Installing Window Maker on a Solaris 2.6 box might require
429 one or two little hints. Here you are (this was on a system
430 running xdm by the way, but similar suggestions apply otherwise):
431 <P>
432 1) /usr/openwin/lib/X11/xdm/Xservers like this:
433 <P>
434 :0 local /usr/openwin/bin/X -dev /dev/fb defdepth 24 defclass TrueColor
435 <P>
436 2) Turn off shm in the WindowMaker configure:
437 <P>
438 ./configure --disable-shm
439 <P>
440 3) might have to modify your LD_LIBRARY_PATH:, or make "wmaker"
441 <PRE>
442 a script that does it for you (mv wmaker wmaker.exe):
443 </PRE>
444 LD_LIBRARY_PATH=/usr/local/lib:/usr/local/X11/lib:/usr/lib:/usr/openwin/lib
445 export LD_LIBRARY_PATH
446 /usr/local/bin/wmaker.exe $*
447 <P>
448 The real key is the "--disable-shm".
449 <P>
450 (webmaster note: Window Maker should work fine with
451 SHM enabled, at least it does under Solaris 8. Try
452 the default first, and then use this if you run into
453 problems with it)
454 <A name="52"></A>
455 <h2>2.9 How do I fix an error such as libwraster.so.1: cannot open shared object file?</h2>
456 If you have an error when running Window Maker such as
457 <P>
458 <PRE>
459 libwraster.so.1: cannot open shared object file
460 </PRE>
461 These are the instructions for Linux.
462 <P>
463 First, make sure that /usr/local/lib ( or whatever directory you installed Window Maker to)
464 is listed in your /etc/ld.so.conf ). You need to run ldconfig so the new shared libraries will be loaded.
465 After running ldconfig as root, the linker should properly load the libraries.
466 You need to run this every time you update Window Maker.
467 <P>
468 Thanks to Joseph Czapiga, the BSD procedure for adding shared
469 library directories is
470 <P>
471 <PRE>
472 ldconfig -m /usr/local/lib (m means merge)
473 </PRE>
474 <A name="53"></A>
475 <h2>2.10 How do I fix an error dealing with aclocal: configure.in: 15: macro 'AM_PROG_LIBTOOL' not found in library?</h2>
476 You need to install libtool.
477 It also must be a libtool different from version 1.2b ( shipped with redhat 5.2 ).
478 You can get libtool from ftp.gnu.org/pub/gnu
479 Make sure the autoconf and automake versions you have installed are at
480 least:
481 autoconf 2.12
482 automake 1.3
483 libtool 1.2
484 <P>
485 <PRE>
486 From Blaine Horrocks:
487 </PRE>
488 "You can also work around this problem on RedHat5.2 by copying the
489 distributed aclocal.m4 to acinclude.m4 before running configure for the
490 first time. Configure works fine and doing the make succeeds."
491 <A name="55"></A>
493 This is related to having compiled Window Maker on a system whose libraries were compiled
494 by egcs or gcc 2.8.0, and then using the binaries on a system whose libraries were compiled
495 by gcc 2.7.2.x
496 <P>
497 Try compiling Window Maker with the newer gcc or recompile your system libraries
503 How many of you have seen that darned "lib reports 62 caller expects 61" type
504 of error? Here are some answers that will possibly help you out.
515 to properly manage your library cache (or other appropriate
516 mechanism).
517 <P>
518 On Linux, this would mean having /usr/local/lib in
519 /etc/ld.so.conf and then running ldconfig.
520 <P>
521 Now on to the error. This is basically caused
522 by your application having been compiled to
523 dynamically use the libjpeg.so shared library.
524 When you install a new lib and then try to run
525 your program again, it expects the lib it was
526 compiled against, in this case the older
527 libjpeg.so.6.0.1 and instead finds libjpeg.so.6.0.2
528 and reports the error.
529 <P>
530 The fix is actually rather simple. Along with adding a
531 libjpeg.so.6 symlink like so (just in case):
532 ln -s libjpeg.so.6.0.2 libjpeg.so.6 where you installed
533 your new lib, you simply need to recompile your app to
534 link it against the new library.
535 <P>
536 Also, make sure to use GNU make for the Window Maker compile.
537 <A name="57"></A>
538 <h2>2.13 How do I start Window Maker after running wmaker.inst?</h2>
539 As of version 0.53.0, the wmaker.inst script will modify your X startup script
540 ( .xinitrc or .Xclients or .Xsession ) to do something thats (hopefully)
541 appropriate.
542 <P>
543 In order to run wmaker, a user needs to have an ~/.xinitrc
544 file consisting of something similar to
545 <P>
546 <PRE>
547 #!/bin/sh
548 exec wmaker
549 </PRE>
550 <P>
551 This will vary from system to system, but the existance
552 of an .xinitrc file will generally override the system
553 defaults.
554 <A name="58"></A>
555 <h2>2.14 How do I make libpng link against Window Maker?</h2>
556 The newest png libs are availible at http://www.libpng.org/pub/png/libpng.html
557 <P>
558 You should also get the newest zlib libs from
559 http://www.gzip.org
560 <P>
561 Generally, the same rules apply here as with libjpeg. Make sure there are no
562 older versions of the necessary libs floating around on your system, then try
563 to configure and make again.
564 <P>
565 Also, make sure to use GNU make (gmake) for the Window Maker compile.
566 <A name="59"></A>
567 <h2>2.15 How do I make giflib or libungif to link against Window Maker?</h2>
568 The newest versions of both these libraries are available at
569 http://prtr-13.ucsc.edu/~badger/software/
572 Users have had a few problems with giflib... it seems that the install process didn't
577 systems).
581 <h2>2.16 How do I fix an error similar to "wrlib: could not allocate shared memory segment: invalid argument"</h2>
582 This relates to a shared memory problem on
584 is started from command line (or fail-safe session for that
585 matter). In any of the cases, on the stderr you get an error
586 message like this:
587 <P>
588 <PRE>
589 "wrlib: could not allocate shared memory segment: invalid argument"
590 </PRE>
591 This one is generated by wrlib if Window Maker is compiled with
592 shared-memory usage enabled (which is the default). The explanation
593 is that Solaris by default comes with a shared memory segment size
594 of maximum 1 M. What happends is that if you have a really-really
595 cool(tm) background, it is usually much bigger than that 1 M segment
596 of shared memory. To see your defaults relating the IPC settings check
597 the output of the "sysdef" command (look for IPC Shared Memory). There
598 you should see the maximum allocable size for a shared memory segment. If
599 it is less than 5 M you should really increase it by adding the following
600 line in your /etc/system file:
601 <P>
602 <PRE>
603 set shmsys:shminfo_shmmax=20971520
604 </PRE>
605 <P>
614 at boot time the kernel will complain of not finding such a module
617 recognition", for evil things may happen at boot time.<BR>
618 <P>
619 After adding this to your /etc/system you need to reboot
620 in order for the new limit to take effect.
621 Also, you may want to check the new limit just
622 to make sure it has been set.
623 <P>
624 Thanks to Bogdan Iamandei for this answer.
625 <A name="61"></A>
626 <h2>2.17 How do I add Window Maker to the Solaris dtlogin screen?</h2>
627 The two files that
628 determine alternate window managers are:
629 <P>
630 <PRE>
631 /usr/dt/config/C/Xresources.d/Xresources.*
632 /usr/dt/config/Xsession.*
633 </PRE>
639 Here is an example setup:
643 #
644 **************************************************************************
645 #
646 # Window Maker config file
647 # Mike Bland <mbland@cmu.edu>
648 #
649 # /usr/dt/config/C/Xresources.d/Xresources.wm
650 #
651 # used by dtlogin
652 #
653 #
654 **************************************************************************
663 #Dtlogin*altDtLogo: /usr/local/share/logos/WM_logo.xpm
666 # Once I get a logo ready, I'll add it to the dtlogin screen by
667 uncommenting
668 # the last line.
674 #!/bin/ksh
675 #
676 **************************************************************************
677 #
678 # Window Maker startup script
679 # Mike Bland <mbland@cmu.edu></A>
680 # /usr/dt/config/Xsession.wm
681 #
682 # used by dtlogin
683 #
684 #
685 **************************************************************************
689 # environment variables (especially
690 # LD_LIBRARY_PATH=/usr/local/lib:...);
691 # make sure it's executable.
697 export WINDOW_MANAGER
705 and is replaced by cleaner, more robust code in the WINGs toolkit. This new code maintains existing proplist compatibility,
706 so there are no visable changes for users, and existing file formats will work as they did before.
710 For developers, there is a proplist-compat.h header that provides a mapping between the old and new function names. See the comments in this file for further instructions.<BR>
713 <?
714 }
716 ?>
722 <B>3.4</B> <A href="#76">How do I get my Meta-Tab to cycle through windows correctly?</A><BR>
723 <B>3.5</B> <A href="#77">How do I get a tile background for my appicons (those things in the dock)?</A><BR>
724 <B>3.6</B> <A href="#78">How do you dock <insert program here> that doesn't have an appicon in the new version of WindowMaker?</A><BR>
725 <B>3.7</B> <A href="#79">How do I get x11amp to not have a title bar ( or any other program for that matter )?</A><BR>
726 <B>3.8</B> <A href="#80">How do I set a pixmap background?</A><BR>
727 <B>3.9</B> <A href="#81">Can I put pixmaps in my root menu and title bars?</A><BR>
728 <B>3.10</B> <A href="#82">How do I get my Minimize Icon to look like the triangle I see in screenshots?</A><BR>
729 <B>3.11</B> <A href="#83">Why does Netscape have a black and white Icon when I minimize it?</A><BR>
730 <B>3.12</B> <A href="#84">How do I get superfluous bells and whistles working?</A><BR>
731 <B>3.13</B> <A href="#85">How do I get the classic NeXT(tm)-like style back?</A><BR>
732 <B>3.14</B> <A href="#86">How do I get the window menu with only a two button mouse?</A><BR>
733 <B>3.15</B> <A href="#87">How do I edit my root menu?</A><BR>
734 <B>3.16</B> <A href="#88">WPrefs disappeared from the Dock! How do I get it back?</A><BR>
735 <B>3.17</B> <A href="#89">How can I define my own Icon for a program? (instead of the Icon the Application Supplies?)</A><BR>
736 <B>3.18</B> <A href="#90">How do I turn off the workspace titles between workspaces?</A><BR>
737 <B>3.19</B> <A href="#91">How do I add dynamic items to my root menu?</A><BR>
738 <B>3.20</B> <A href="#92">How do I remove or hide appicons?</A><BR>
739 <B>3.21</B> <A href="#93">I disabled my titlebar. How can I get it back?</A><BR>
740 <B>3.22</B> <A href="#94">How do I remove ALT+Mouse1 from the action Window Maker grabs for an application?</A><BR>
741 <B>3.23</B> <A href="#95">How do I configure the Dock and Clip to use less space on a small screen?</A><BR>
742 <B>3.24</B> <A href="#128">Why do dashes not work as menu entries?</A><BR>
743 </UL>
744 </FONT>
745 <BR><HR><BR>
746 <A name="73"></A>
747 <h2>3.1 What are those files inside my ~/GNUstep directory?</h2>
748 Here is a synopsis of the files in ~/GNUstep
749 <P>
750 ~/GNUstep/WindowMaker/WindowMaker is main config file. This
751 file controls options such as keybindings, fonts,
752 pixmaps, and focus modes.
753 <P>
754 ~/GNUstep/WindowMaker/WMWindowAttributes controls the
755 "attributes" for individual applications and appicons.
756 Options such as what icon to use are set here. For the
757 most part, this is now best accessed via a right click
758 on a title bar of an application and selecting
759 "Attributes"
760 <P>
761 ~/GNUstep/Defaults/WMState is the file that is
762 automatically generated and contains the current
763 dock settings. It is not recommended to edit this
764 file by hand.
765 <P>
766 ~/GNUstep/Defaults/WMRootMenu specifies what file to use
767 as the root menu. In Window Maker 0.19.0 and higher, this
768 file should be replaced by plmenu from ~/GNUstep/Defaults/WindowMaker
769 so that one can use WPrefs.app to edit the menu.
770 <P>
771 ~/GNUstep/Library/WindowMaker/menu is used to change your root menu,
772 if you are using the old menu style.
773 <A name="74"></A>
774 <h2>3.2 How do I enable the normal X sloppy focus mode?</h2>
777 <P>
779 <P>
780 You may also use a text editor on
781 <P>
782 <PRE>
783 ~/GNUstep/Defaults/WindowMaker
784 </PRE>
785 and change the following:
786 <P>
787 <PRE>
788 FocusMode = sloppy;
789 </PRE>
790 <A name="75"></A>
791 <h2>3.3 How do I get my auto-arrange icons to work?</h2>
794 <P>
795 Or in
796 <PRE>
797 ~/GNUstep/Defaults/WindowMaker
798 </PRE>
799 set
800 <PRE>
801 AutoArrangeIcons=YES;
802 </PRE>
803 and the icons should now auto-arrange.
804 <A name="76"></A>
805 <h2>3.4 How do I get my Meta-Tab to cycle through windows correctly?</h2>
808 <P>
809 Or you can use a text editor to make sure that these settings are in your
810 ~/GNUstep/Defaults/WindowMaker file:
811 <P>
812 <PRE>
813 CirculateRaise = YES;
814 RaiseDelay = 1;
815 </PRE>
819 These can all be adjusted by the ``Appearance Preferences'' tab in
820 WPrefs.
823 choose any of the different tile background options in the
831 The last parameter is the color that fills in any transparent
832 parts of your icon.
834 <h2>3.6 How do you dock <insert program here> that doesn't have an appicon in the new version of WindowMaker?</h2>
835 There is now an option available to emulate appicons so that Window Maker
836 can dock just about anything now. To dock a misbehaving application, right click
837 on the title bar and select the attributes menu. Next, select the pull down menu's
843 Dan Pascu adds:
852 from the top dock icon.
854 Elliott Potter adds:
856 There's another way to dock applications that misbehave ... I've only
858 remember at the moment).
861 work:
862 <P>
863 Dock another application to the clip, where you want your application to
864 go. I used gv, but anything you can dock will work.
865 Quit WindowMaker
866 Edit ~/GNUstep/Defaults/WMState
869 <PRE>
870 {
871 Command = gv;
872 Name = GV.gv;
873 AutoLaunch = No;
874 Forced = No;
875 BuggyApplication = No;
876 Position = "6,0"
877 Omnipresent = No;
879 },
880 </PRE>
881 Edit it to use the info for your new application:
882 <PRE>
883 {
884 Command = acroread; # use the full pathname if you have to
885 Name = acroread.acroread;
886 AutoLaunch = No;
887 Forced = No;
888 BuggyApplication = No;
889 Position = "6,0"
890 Omnipresent = No;
892 },
893 </PRE>
894 Then edit WMWindowAttributes, and add a line for your application's
901 it around like any other docked app now, but the Attributes section
902 still won't work.
903 <A name="79"></A>
904 <h2>3.7 How do I get x11amp to not have a title bar ( or any other program for that matter )?</h2>
905 Right Click on the title bar and go to the attributes menu. Click on Window Attributes and click
906 the the Disable titlebar and Disable Resizebar options. Click Save, and then click
907 Apply then close the Attributes panel.
908 <P>
909 By Default, to get back to the attributes menu, use the key combination Control-Esc.
910 <A name="80"></A>
911 <h2>3.8 How do I set a pixmap background?</h2>
912 Here is the in depth explanation straight from the NEWS file:
913 <P>
914 wmsetbg now accepts the following options:
915 <PRE>
916 usage: wmsetbg [-options] image
917 options:
918 -d
919 dither image
920 -m
921 match colors
922 -t
923 tile image
924 -s
925 scale image (default)
926 -u
927 update Window Maker domain database
928 -D <domain>
929 update <domain> database
930 -c <cpc>
931 colors per channel to use
932 </PRE>
933 <P>
934 <P>
935 By default, it will try to guess if dithering is needed or not and proceed
936 accordingly.
937 Using -d or -m will force it to dither or match colors.
938 <P>
939 Dithering for more than 15bpp is generally not needed, and will only result
940 in a slower processing.
944 -u
946 will update the WorkspaceBack in the default database
948 Maker refresh the screen. Please note that this option only
950 other window managers, since it rely on Window Maker to
951 update the image after it reads the updated defaults
952 database.
954 -D
959 -c
962 PseudoColor visuals. Window Maker will automatically pass
963 the value read from the Window Maker domain database.
970 "Images" OPEN_MENU BACKGROUNDS_DIR
973 This should give you an idea on how to add other entries for different image
974 directories. See the help info at the top of the
979 of XV's special modes, edit the file ~/GNUstep/Library/WindowMaker/autostart
980 and insert the line
981 <P>
982 <PRE>
983 xv -root -quit -maxpect ~/background.jpg
984 </PRE>
985 or
986 <PRE>
987 xv -root -quit -max ~/background.jpg
988 </PRE>
989 you can also try variations of this to get different tiling and other effects
990 (where X is a number 1-9 I believe):
992 <P>
993 If you would like xv functionality in your menu, heres a nice little tip from
994 Alfredo:
995 <P>
996 Add the following line to your ~/GNUstep/Library/WindowMaker/menu file. (all on
997 one line)
998 <P>
999 "More Backgrounds" OPEN_MENU /home/whoever/backgrounds xv -root -maxpect -quit
1000 <A name="81"></A>
1001 <h2>3.9 Can I put pixmaps in my root menu and title bars?</h2>
1002 Put the pixmaps in a directory that is located in your pixmap path set
1004 <P>
1007 and then search for the texture.
1008 <P>
1009 You can use a similar procedure for any type of menu editing.
1010 <P>
1011 You can use png, gif, ppm, tiff, jpeg and xpm images interchangeably in
1012 Window Maker if you have compiled in support for those formats.
1013 <A name="82"></A>
1014 <h2>3.10 How do I get my Minimize Icon to look like the triangle I see in screenshots?</h2>
1015 This involves a minor source tweak. Instructions are available at
1016 http://largo.windowmaker.org/tips.php#titlebar_icons
1017 <A name="83"></A>
1018 <h2>3.11 Why does Netscape have a black and white Icon when I minimize it?</h2>
1019 Craig Maloney has this answer:
1020 <P>
1021 If you happen to --enable-openlook at compile time,
1022 Netscape (and presumably other apps as well) believe
1025 Netscape minimizes with the correct icon.
1031 Alternatively, you may add
1040 select the classic look.
1042 Or you can add
1050 to a button of choice.
1061 and
1070 with a GNUStep icon backgroud ). Note that this will replace any oldstyle
1071 menus and there is no way to convert the oldstyle menu to the
1081 try
1084 touch menu
1086 to force the modification time into the future.
1089 Pascal Hofstee offers this answer:
1091 You should just start it from a terminal by supplying it's FULL path-name,
1092 which is usually the following:
1093 <P>
1094 <PRE>
1095 /usr/local/GNUstep/Apps/WPrefs.app/WPrefs
1096 </PRE>
1098 At this point, a new appicon should be generated
1099 which can be placed back into the Dock.
1100 <A name="89"></A>
1101 <h2>3.17 How can I define my own Icon for a program? (instead of the Icon the Application Supplies?)</h2>
1102 You can right click on the titlebar of the running app and choose the
1103 "Attributes..." option, then click on the "Ignore client supplied icon"
1104 checkbox. Click "Apply", "Save" and close the Attributes Editor.
1105 <P>
1106 Another method is to edit ~/GNUstep/Defaults/WMWindowAttributes by hand and
1107 use the AlwaysUserIcon=YES; option for the app. For example:
1108 <P>
1109 xmcd = { Icon = "Radio.xpm";
1110 AlwaysUserIcon=Yes;
1111 };
1112 <A name="90"></A>
1113 <h2>3.18 How do I turn off the workspace titles between workspaces?</h2>
1114 In Window Maker 0.60.0, an option was added to turn this off.
1115 <P>
1116 By editing
1117 <PRE>
1118 ~/GNUstep/Defaults/WindowMaker
1119 </PRE>
1120 insert or modify the key
1121 <P>
1122 <PRE>
1123 WorkspaceNameDisplayPosition = none;
1124 </PRE>
1125 Other valid options for this include
1126 center/top/bottom/topleft/topright/bottomleft/bottomright;
1127 <A name="91"></A>
1128 <h2>3.19 How do I add dynamic items to my root menu?</h2>
1129 A few programs are floating about, notably wkdemenu.pl that can produce
1130 output from other menu styles. In order to get WindowMaker to launch the process everytime
1131 you want to use the menu, use something like
1132 <P>
1133 <PRE>
1134 ("External Menu", OPEN_MENU, "| bob.sh")
1135 </PRE>
1136 in a proplist style menu. You can tell if you have a proplist style menu if you can
1137 edit it with WPrefs.
1138 <P>
1139 You can do this directly in WPrefs by going to the menu editor, adding an "external menu",
1140 and then clicking the "ask guru button" and filling in the process name.
1141 <P>
1142 Thanks to Igor P. Roboul
1143 <A name="92"></A>
1144 <h2>3.20 How do I remove or hide appicons?</h2>
1145 There are two options here, and you need to consider which one you prefer.
1146 Read both of these before you decide.
1147 <P>
1148 First, if you do not want to use the clip or dock at all, you can launch wmaker with
1149 with
1150 <P>
1151 <PRE>
1152 wmaker --no-clip --no-dock
1153 </PRE>
1154 and then in
1155 <P>
1156 <PRE>
1157 ~/GNUstep/Defaults/WMWindowAttributes
1158 </PRE>
1159 add
1160 <P>
1161 <PRE>
1162 "*" = {NoAppIcon=Yes;};
1163 </PRE>
1164 The problem with this method is if you use the dock for dockapps, it renders them
1165 with out an appicon to write to.
1166 An alternative method if you are willing to let the clip be on your desktop is
1167 to right click on the clip > clip options > auto attract.
1168 Double click the clip so that it is grayed and all appicons will be hidden.
1169 Then you can hide the clip behind the dock so that it is out of your way.
1170 This will allow appicons to work.
1171 <A name="93"></A>
1172 <h2>3.21 I disabled my titlebar. How can I get it back?</h2>
1173 Thanks to Jim Knoble for this answer
1174 <P>
1175 Set the focus to the window and then use the keystroke assigned to the
1178 commands menu' item in the list of actions. The keystroke assigned to
1180 <P>
1181 Typically it is Control-Esc or F10 in older version of WindowMaker.
1182 <A name="94"></A>
1183 <h2>3.22 How do I remove ALT+Mouse1 from the action Window Maker grabs for an application?</h2>
1184 Do [Button3Down] (for righthanded mouse users, [RightButtonDown]) on
1188 inspector.
1194 instead of performing their usual action.
1207 desktop.
1208 <P>
1209 For the Dock, try the following:
1210 <P>
1211 (1) Exit Window Maker.<BR>
1212 (2) Log in via a text console or using a different window manager.<BR>
1213 (3) Edit ~/GNUstep/Defaults/WMState using your favorite text editor
1214 (for example, vi, emacs, or pico).<BR>
1217 command you want the top tile to launch. Change the `Name' item
1218 to the "<instance>.<class>" name of the application you just made
1224 should still also be able to move the Dock up and down using
1229 <A name="128"></A>
1230 <h2>3.24 Why do dashes not work as menu entries?</h2>
1231 If you wish to use a - as part of a menu item name, you must enclose the name in double quotes. This will only apply if you're editing the ~/GNUstep/Defaults/WMRootMenu file manually, as it is handled properly within WPrefs.
1234 This will work:
1239 This will not:
1248 <?
1249 }
1251 ?>
1255 <B>4.2</B> <A href="#63">What is the difference between the Exit and Exit Session Option?</A><BR>
1257 <B>4.4</B> <A href="#65">Why do none of my key bindings (ie: Alt+#) work in Window Maker?</A><BR>
1259 <B>4.6</B> <A href="#67">How can I resize a window if the window is larger than my current desktop?</A><BR>
1261 <B>4.8</B> <A href="#69">I docked an application but when I run it the button is permanently shaded and I can't run new instances.</A><BR>
1262 <B>4.9</B> <A href="#70">When I run wmaker it complains about not being able to load any fonts.</A><BR>
1263 <B>4.10</B> <A href="#71">When I set the root background with wmsetbg by hand it works, but when I do that from the configuration files it doesnt!</A><BR>
1264 <B>4.11</B> <A href="#72">What is the purpose of being able to draw a box on the root menu with a left click?</A><BR>
1265 </UL>
1266 </FONT>
1267 <BR><HR><BR>
1268 <A name="62"></A>
1269 <h2>4.1 How do add new icons to the Dock?</h2>
1271 appears in the bottom left corner of the screen, left click and drag it over
1272 near the Dock. You will see a slightly opaque square of where the
1273 Dock will place the appicon. When you do, release the mouse
1274 button and the appicon should now be in the Dock.
1275 <P>
1276 Next, right click on the desktop to bring up the menu.
1277 Select Workspace -> Save Session to make this permanent.
1278 <A name="63"></A>
1279 <h2>4.2 What is the difference between the Exit and Exit Session Option?</h2>
1280 Another answer from Dan Pascu:
1281 <P>
1282 "Exit will exit wmaker, but can leave other X apps running, provided that it was
1283 not the last app launched in the .xinitrc (for instance, if you had exec wmaker,
1285 running so you could start another window manager, etc.) This is accomplished
1286 because X will not shutdown unless all X apps are closed.
1287 <P>
1288 Exit session will exit wmaker, but will also
1289 close all running apps, thus the X server will be closed
1290 too."
1291 <A name="64"></A>
1292 <h2>4.3 How do I "dock" icons on the clip?</h2>
1293 Just drag icons near it like you would for the dock. If you are having a problem
1294 docking icons, you should try moving the clip away from the dock.
1295 <A name="65"></A>
1296 <h2>4.4 Why do none of my key bindings (ie: Alt+#) work in Window Maker?</h2>
1297 If you are using XFree86, make sure scroll lock and numlock are off or no bindings
1298 will work (XFree bug). You can try using the XFree86 Numlock Hack by editing the
1299 line #undef NUMLOCK_HACK in $(WindowMaker)/src/wconfig.h and changing it to
1300 #define NUMLOCK_HACK.
1301 <P>
1302 With the release of 0.18.0, this hack is now working and hopefully no
1303 one will have to ask this question again.
1304 <A name="66"></A>
1305 <h2>4.5 How do I rename workspaces?</h2>
1306 Right click to bring up the root menu. Go under
1307 the Workspaces menu item and hold the control key down.
1308 Next, click on the workspace entry you
1309 would like to rename, type the name, and
1310 press enter.
1311 <A name="67"></A>
1312 <h2>4.6 How can I resize a window if the window is larger than my current desktop?</h2>
1313 David Reviejo best summed up this answer:
1314 <P>
1315 "Maybe you know:
1316 Alt+Left click and drag
1317 to move the window.
1318 <P>
1319 Try this:
1320 Alt+Right click and drag
1321 to resize (by moving the nearest window corner)
1322 <P>
1323 Another move/resize tip: while you are moving or resizing a window, you
1324 can change the move/resize mode by pressing the SHIFT key."
1325 <A name="68"></A>
1326 <h2>4.7 How do I "undock" appicons?</h2>
1327 If the program is not running, just drag the icon to the middle of your
1328 desktop and watch it disappear. If the program is running, hold down Meta and drag the icon off the dock.
1329 <A name="69"></A>
1330 <h2>4.8 I docked an application but when I run it the button is permanently shaded and I can't run new instances.</h2>
1331 You probably docked the application with dockit. To fix it
1334 Then restart the application to get the application icon you
1336 It can also mean that you did something you shouldn't, which is
1337 changing the program that is ran from the docked icon. For example,
1338 if you docked rxvt you must NOT change it to xterm, for example.
1345 do, unset the LANG environment variable before running wmaker.
1346 <P>
1347 TODO: give complete explanation
1348 <A name="71"></A>
1349 <h2>4.10 When I set the root background with wmsetbg by hand it works, but when I do that from the configuration files it doesnt!</h2>
1350 If you set the root background with wmsetbg by hand, it will obviously
1351 find the image, since you have explicitly specified it by hand. But if you
1352 simply put it in
1353 <PRE>
1354 ~/GNUstep/Defaults/WindowMaker
1355 </PRE>
1356 in some option like WorkspaceBack, it will not find the image because Window Maker can't read
1359 the path for the directory you put your background images in the PixmapPath
1360 option. You can also put all your background images in places like
1364 or
1368 David Green says that another possibility is that you have two copies of the worker programs:
1371 <h2>4.11 What is the purpose of being able to draw a box on the root menu with a left click?</h2>
1376 their relative positions.
1383 <?
1384 }
1386 ?>
1391 <B>5.3</B> <A href="#98">Where do I get the nifty clock program I always see on people's desktops?</A><BR>
1392 <B>5.4</B> <A href="#99">How do you dock asclock?</A><BR>
1393 <B>5.5</B> <A href="#100">Where can I get more dockapps?</A><BR>
1394 <B>5.6</B> <A href="#101">How do I get an appicon for rxvt so I can dock it?</A><BR>
1395 <B>5.7</B> <A href="#102">How do I allow Alt+# to work in an rxvt/xterm session?</A><BR>
1396 <B>5.8</B> <A href="#103">How do I get different icons for different rxvt's and xterms?</A><BR>
1397 <B>5.9</B> <A href="#104">How do I launch multiple instances of XTerm from one appicon?</A><BR>
1400 <B>5.12</B> <A href="#107">How do I dock an arbitrary console application like mutt?</A><BR>
1402 <B>5.14</B> <A href="#109">How can I dock an application from a remote machine using ssh?</A><BR>
1403 <B>5.15</B> <A href="#110">How do you make an omnipresent window not take focus whenever switching workspaces?</A><BR>
1409 You can enter the following line in WMWindowAttributes:
1415 click on the title bar of an app, click on the droplist->Icon and WorkSpace entry, enter the icon file name (
1421 You don't need to patch the XEmacs code, just run
1422 <P>
1423 <PRE>
1424 ./configure --with-session=yes (in addition to any other options you use)
1425 </PRE>
1426 in your XEmacs 20.3+ sourcedir and rebuild it. Then XEmacs shows an appicon
1427 when running and you can easily dock it.
1428 <A name="98"></A>
1430 It's called asclock. Once included with Window Maker, it now is available
1431 at <A HREF="ftp://ftp.windowmaker.org/pub/contrib/srcs/apps/asclock.tgz">ftp://ftp.windowmaker.org/pub/contrib/srcs/apps/asclock.tgz</A>
1432 <P>
1433 asclock was written by Beat Christen and used to have its own website, which
1434 seems to have disappeared. However, references to it exist all over
1435 the place, and can be found by searching <A href=http://www.google.com/search?q=asclock%22>Google</A>.
1436 Beat Christen wrote this awhile back:
1437 <P>
1438 "Please note that the asclock-gtk version 2.0 beta 4
1439 (asclock-gtk-2.0b4.tar.gz) does not have the -d switch yet and that the
1440 asclock-xlib-2.1b2.tar.gz does not have the shaped asclock builtin."
1441 <P>
1442 A wonderful alternative to asclock is Jim Knoble's
1447 It is highly recommended that you use the asclock mentioned previously in question 5.3. The asclock that is typically included in AfterStep will not properly dock with Window Maker. At this point, there are at least four or five different versions of asclock floating about.
1460 select autolaunch.
1462 In order to make asclock launch every time you start Window Maker, right click on the
1465 button.
1467 If you get an error such as sh: /dev/console: Permission denied, login as root, cd to /dev/ and run
1469 ./MAKEDEV console
1473 The Window Maker team got tired of people E-mailing constantly asking where the websites for obscure dockapps disappeared to. So we've created the ultimate dockapps community website.
1474 Visit <a href="http://dockapps.org/">dockapps.org</a> for the latest, up-to-date links, information, and download for Window Maker and related dockapps.
1475 <P>
1476 Another large index of dockapp links is available at <A HREF="http://www.bensinclair.com/dockapp">http://www.bensinclair.com/dockapp</A> . The downside to this is that they're only links, so if someone stops maintaining a dockapp, or their web hosting provider cuts them off, you won't be able to get to it. Still, Ben Sinclair's site was the first big "dockapp warehouse" site, so we give credit where credit is due. :)
1481 newest development version of rxvt is availible from
1482 <A HREF="ftp://ftp.math.fu-berlin.de/pub/rxvt/devel">ftp://ftp.math.fu-berlin.de/pub/rxvt/devel</A>/. As of the time of this writing, the version is
1485 John Eikenberry has also created an rpm which is available from
1486 <A HREF="ftp://ftp.coe.uga.edu/users/jae/windowmaker">ftp://ftp.coe.uga.edu/users/jae/windowmaker</A>
1490 option of rxvt.
1496 should be able to run your session without the shortcuts.
1499 The hint is the -name option for xterm or rxvt. This will allow you to change the exact
1500 WM_CLASS in the attributes menu and assign a unique icon.
1501 <P>
1502 <PRE>
1503 rxvt -name foo -title Testing
1504 </PRE>
1505 Then Right click on the title bar to bring up the attributes menu, and you will be able
1506 to edit the properties for foo.XTerm (ie: assign a unique icon).
1507 <A name="104"></A>
1508 <h2>5.9 How do I launch multiple instances of XTerm from one appicon?</h2>
1509 Thanks for the update by Sara C. Pickett:
1510 <P>
1511 The easiest way to accomplish this is to dock XTerm as normal. Then
1512 Go to the Attributes menu -> Application Specific and select no application icon
1513 for XTerm.
1514 <P>
1515 Then right-click on the docked appicon and select settings. Change the
1516 Application Path with arguments section to
1517 <P>
1518 <PRE>
1520 </PRE>
1521 <A name="105"></A>
1522 <h2>5.10 Window Maker breaks scilab.</h2>
1523 If you refer to the problem of the "graphics" window of scilab not showing
1524 up in Window Maker, this is caused by a bug in scilab. You can see the
1525 cause of the problem by yourself, by running xprop on the graphic window:
1526 WM_NORMAL_HINTS(WM_SIZE_HINTS):
1527 <PRE>
1528 user specified location: 136679205, 1074468360
1529 user specified size: 400 by 300
1530 program specified minimum size: 400 by 300
1531 </PRE>
1534 obviously falls outside the screen no matter how big is your monitor ;)
1538 on the ScilabGraphic entry. The window should be brought to your
1540 titlebar) and open the Attributes panel. Go to the "Advanced Options"
1541 section, check the "Keep inside screen" option and save.
1542 <P>
1543 If you can recompile Scilab, this came from a Scilab developer:
1544 <P>
1545 replace
1546 <PRE>
1547 size_hints.flags = USPosition | USSize | PMinSize;
1548 </PRE>
1549 with
1550 <PRE>
1551 size_hints.flags = /** USPosition |**/ USSize | PMinSize;
1552 </PRE>
1553 in routines/xsci/jpc_SGraph.c
1554 <A name="106"></A>
1555 <h2>5.11 How do I get a transparent xterm/rxvt/xconsole?</h2>
1556 You need a terminal emulator that has support for transparency, like
1557 Eterm, the latest rxvt, wterm, aterm or gnome-terminal.
1558 <P>
1559 You can find these programs on <A HREF="http://www.freshmeat.net/">http://www.freshmeat.net</A>
1560 <A name="107"></A>
1561 <h2>5.12 How do I dock an arbitrary console application like mutt?</h2>
1562 There are two key things to do if you want a program (such as mutt) to
1563 be able to start in a terminal window from the Dock or the Clip:
1564 <P>
1565 (1) Make the terminal window start the program you want to run
1566 instead of a shell. Both xterm and rxvt (and its descendants)
1567 are capable of doing this. For example:
1568 <P>
1569 <PRE>
1570 xterm -e mutt
1571 rxvt -e mutt
1572 gnome-terminal -e mutt
1573 </PRE>
1574 (2) Convince Window Maker that the resulting terminal window is not a
1575 regular terminal window, but rather some other program instance.
1576 Both xterm and rxvt are also capable of doing this. Make sure
1577 that -e is the last command option. For example:
1578 <P>
1579 <PRE>
1580 xterm -name muttTerm -e mutt
1581 rxvt -name muttTerm -e mutt
1582 gnome-terminal --name=muttTerm -e mutt
1583 </PRE>
1584 This causes the instance of the terminal window that you start to
1585 have an <instance-name>.<class-name> pair of `muttTerm.XTerm'
1590 these are BAD instance names:
1603 the `special' terminal window running your program (make
1604 sure you choose the exact `muttTerm.XTerm' window
1605 specification in the Attributes editor).
1609 background colors).
1615 example:
1616 <P>
1617 <PRE>
1619 </PRE>
1620 Xterm works the same way.
1621 <P>
1622 (4) These are getting to be a lot of command-line options. Make a
1626 mkdir ~/bin
1628 #!/bin/sh
1630 EOF
1634 above using the simple:
1642 muttTerm
1646 when you want to change anything in the really long command
1653 <P>
1654 (c) Replace the text in the `Application path and arguments'
1655 field with the following:
1658 muttTerm
1661 <P>
1662 Note that Window Maker needs to know that ~/bin is on your PATH
1663 for this to work; you may need to exit your X session and start
1664 it again.
1665 <P>
1666 To change the instance name of the terminal window (e.g., from
1668 `terminalWindowRunningMutt'), you need to do the following
1669 <P>
1670 (e) Change your muttTerm script
1671 (f) Undock your old muttTerm
1672 <P>
1673 (g) Run your muttTerm script
1674 <P>
1675 (h) Dock the resulting terminal window
1676 <P>
1677 (i) Do the stuff in [a] through [d] above again.
1678 <P>
1679 Good luck.
1680 <P>
1681 <P>
1682 Thanks to Jim Knoble for this answer.
1683 <A name="108"></A>
1684 <h2>5.13 How do I get an appicon for Netscape?</h2>
1685 If you are not using one of the latest Navigators, you can
1686 <P>
1687 1) Right click on the title bar
1688 <P>
1690 <P>
1692 <P>
1694 <P>
1695 5) Click Save
1696 <P>
1697 and older netscapes should now produce an application icon.
1698 <P>
1699 If you are using a newer rpm from Redhat Linux, try running
1700 <PRE>
1701 grep irix `which netscape`
1702 </PRE>
1703 This seems to have been introduced in their 4.7 update. Comment out
1704 irix-session management restart netscape. Alternatively, you may run
1705 either
1706 <P>
1707 <PRE>
1708 /usr/lib/netscape/netscape-communicator
1709 </PRE>
1710 or
1711 <PRE>
1712 /usr/lib/netscape/netscape-navigator
1713 </PRE>
1714 depending on which rpms you have installed.
1715 <A name="109"></A>
1716 <h2>5.14 How can I dock an application from a remote machine using ssh?</h2>
1717 This answer asumes that you have already set up RSA
1719 <PRE>
1721 </PRE>
1723 <P>
1724 With the addition to ~/.xsession of
1725 <P>
1726 <PRE>
1727 eval `ssh-agent`
1728 ssh-add /dev/null
1729 </PRE>
1730 just before
1731 <PRE>
1732 exec wmaker
1733 </PRE>
1734 Then ssh will no longer prompt for the RSA-key passphrase.
1737 <P>
1738 The following procedure shows how to dock a remote xterm
1740 X11 application, including most Dock applets.
1741 <P>
1743 <P>
1744 <PRE>
1745 ssh -a -C -X remote.example.net "xterm -name blah"
1746 </PRE>
1749 to run. The -C option turns on compression, very
1750 useful for things such as X)
1751 <P>
1752 2) When the remote xterm appears, find the appicon. If it's not
1757 contains only:
1760 xterm -name blah
1762 Change that to:
1768 contents of 'Command for files dropped with DND' in the same
1777 three dots at the lower lefthand corner to indicate the app is no
1778 longer running.
1786 to the Dock.
1790 create a feedback loop by causing additional network traffic, which
1793 <h2>5.15 How do you make an omnipresent window not take focus whenever switching workspaces?</h2>
1795 they will appear on every workspace. This causes the app to often get
1796 the focus unintentionally when switching workspaces.
1798 To remedy this,
1802 hit 'Control+ESC' at the same time to bring up the title bar menu on apps
1808 right corner of the window frame.
1810 Now the window will not take focus when switching workspaces.
1815 <?
1816 }
1818 ?>
1825 <B>6.5</B> <A href="#125">I untarred a theme in ~/GNUstep/Library/WindowMaker like the README says,but it doesnt show up in the menu!</A><BR>
1831 Themes are a great aspect of Window Maker allowing a user to simply
1832 save the entire 'look' of their desktop in an archive to distribute freely among
1835 See the <a href="themepacks.php">theme-HOWTO</a> for an in-depth walk-through on making a Theme archive.
1840 and have it be accessable to all users, or you can untar it to your own
1841 ~/GNUstep/Library/WindowMaker/ directory for your own personal use.
1842 <P>
1843 Use your favorite variation of the following:
1844 <P>
1845 <PRE>
1846 gzip -dc "Theme.tar.gz" | tar xvf -
1847 </PRE>
1848 Note that directory may differ on different systems
1849 <A name="123"></A>
1850 <h2>6.3 Why do my themes not load the background?</h2>
1851 Likely you have not compiled Window Maker with support for the background
1852 image format, usually JPEG.
1853 <P>
1854 You can check this by the following command
1855 <P>
1856 <PRE>
1857 ldd `which wmaker`
1858 </PRE>
1859 If libjpeg is not listed, you will need to install libjpeg that is available
1860 from ftp.windowmaker.org
1861 <A name="124"></A>
1862 <h2>6.4 How do I make a Theme?</h2>
1863 Please see the <a href="themepacks.php">theme-HOWTO</a> for details on making both new and old style themes (and the differences
1864 between the two), here is a short summary on making old style themes.
1865 Also, read the README.themes file included with the Window Maker
1866 distribution in the WindowMaker/ directory.
1867 <P>
1868 In this walk-through when I use WindowMaker/, it can refer to the global
1869 /usr/local/share/WindowMaker/ directory or the users own
1870 ~/GNUstep/Library/WindowMaker/ directory.
1871 <P>
1872 To make a Theme.tar.gz, these are the steps I take:
1873 <P>
1874 1. Optionally create a README for your theme in WindowMaker/, call it
1875 something like "ThemeName.txt"
1876 <P>
1877 2. Use the following command to add the Theme files to your .tar file.
1878 <P>
1879 <PRE>
1880 tar cvf ThemeName.tar ThemeName.txt Themes/ThemeName
1881 Backgrounds/ThemeNameBG.jpg Backgrounds/ThemeNameTile.xpm
1882 </PRE>
1883 You can add as many more images as you need from the
1884 appropriate directories under WindowMaker/ following that general
1885 idea. You can even optionally add an IconSets/ThemeName.iconset and
1886 it's associated icons to your theme in the same manner. This should
1887 be stated in your README if you decide to include these.
1888 <P>
1889 3. Then gzip your .tar file to make your ThemeName.tar.gz file with this command:
1890 <P>
1891 <PRE>
1892 gzip -9 ThemeName.tar
1893 </PRE>
1894 4. Now give it to your friends!
1895 <A name="125"></A>
1896 <h2>6.5 I untarred a theme in ~/GNUstep/Library/WindowMaker like the README says,but it doesnt show up in the menu!</h2>
1897 Make sure the OPEN_MENU command for the Themes entry in your menu has
1898 the path for your personal themes directory included in it. To be sure,
1899 add
1900 <PRE>
1901 #define USER_THEMES_DIR ~/GNUstep/Library/WindowMaker/Themes
1902 </PRE>
1903 in your wmmacros file.<BR>
1904 </BLOCKQUOTE>
1905 <?
1906 }
1907 if ($chapter==7) {
1908 ?>
1909 <h1>Chapter 7: Miscellaneous Questions</h1>
1910 <UL type="disc">
1911 <B>7.1</B> <A href="#115">Is there a pager for Window Maker?</A><BR>
1912 <B>7.2</B> <A href="#116">How do I use getstyle and setstyle?</A><BR>
1913 <B>7.3</B> <A href="#117">Why was libPropList removed from the distribution?</A><BR>
1914 <B>7.4</B> <A href="#118">Why don't you distribute normal diff or xdelta patches?</A><BR>
1915 <B>7.5</B> <A href="#119">Will you add GNOME or KDE support?</A><BR>
1916 <B>7.6</B> <A href="#120">How can I produce a backtrace when Window Maker keeps crashing?</A><BR>
1917 </UL>
1918 </FONT>
1919 <BR><HR><BR>
1920 <A name="115"></A>
1921 <h2>7.1 Is there a pager for Window Maker?</h2>
1922 Not at the moment because there is not a pressing need for a pager. The concept of
1923 multiple desktops does exist and there are currently 3 ways to switch between them.
1924 <P>
1925 First, the Meta+Number combination will switch between desktops. The Workspaces
1926 menu will also let you switch workspaces. Lastly, the clip will also scroll one through
1927 workspaces. For those that would like to send an application to a specific workspace, either drag
1928 it to the edge of the desktop onto the next workspace, or right click on its
1929 title bar, select 'Move To', and click the workspace you want it to be
1930 moved to.
1931 <P>
1932 However, Window Maker does support KDE and GNOME protocols, including their
1933 workspace management, so you may use their pager in conjunction with Window Maker
1934 in these. Note that in order for this to work, you must enable support when
1935 you configure Window Maker (using the --enable-kde and
1936 --enable-gnome configure options).
1937 <P>
1938 Note also that the Blackbox pager application will work with
1939 Window Maker.
1940 <A name="116"></A>
1941 <h2>7.2 How do I use getstyle and setstyle?</h2>
1942 To capture the current Window Maker style, use the command
1943 <P>
1944 <PRE>
1945 getstyle > current.style
1946 </PRE>
1947 To replace the current style, use the command
1948 <P>
1949 <PRE>
1950 setstyle filename.style
1951 </PRE>
1952 <A name="117"></A>
1953 <h2>7.3 Why was libPropList removed from the distribution?</h2>
1954 Alfredo Kojima writes:
1955 <P>
1956 libPropList was removed from Window Maker because other programs also
1957 use it, such as GNOME. If libPropList is distributed with wmaker, it
1958 would cause problems with whatever version of libPropList you already
1959 had installed.
1960 <P>
1961 Now, there is no more GNOME libproplist and Window Maker libproplist. There is
1962 only libPropList which is worked on as a single community effort.
1963 <A name="118"></A>
1964 <h2>7.4 Why don't you distribute normal diff or xdelta patches?</h2>
1965 Whenever possible, plain diff patches are distributed. If the new version has
1966 new binary files, normal diff won't be able to handle them, so a patch
1967 package is distributed instead. We don't use xdelta because a) most
1968 systems do not have xdelta installed and b) xdelta is picky and requires
1969 the files to be patched to be exactly the same as the one used to make the patch.
1970 The patch package scheme used is much more flexible.
1971 <P>
1972 We do not distribute a simple diff with the binary files separately (and
1973 variations, like uuencoding the binary files) because a) it is more
1974 complicated and error prone to require the user to manually move the files
1975 to the correct places b) the current patch package scheme <I>does</I> distribute
1976 the binary files and diff files separately. If the user wants to install
1977 everything by hand, nobody will object to that and c) sooner or later someone will
1978 certainly ask for a script to automate the file moving stuff.
1979 <P>
1980 So we hacked a script (mkpatch) that automatically creates a patch
1981 package with the normal text diff file, a list of removed files and the binary
1982 files that have changed or been added, plus a script that does the patching
1983 automatically. If you don't like the script, you can apply the patch and move
1984 the files manually. Or download the whole distribution.
1985 <A name="119"></A>
1986 <h2>7.5 Will you add GNOME or KDE support?</h2>
1987 Support for GNOME and KDE hints has been included since 0.50.0.
1988 <P>
1989 Note that you must enable this support at compile time with the proper
1990 arguments to configure (--enable-kde and --enable-gnome).
1991 <A name="120"></A>
1992 <h2>7.6 How can I produce a backtrace when Window Maker keeps crashing?</h2>
1993 Thanks to Paul Seelig for this answer:
1994 <P>
1995 You can use the GNU debugger "gdb" to get exact information about how
1996 and where wmaker crashed. Sending this information to the developers
1997 is the most convenient way to help in debugging.
1998 <P>
1999 The wmaker binary needs to be compiled with debugging turned on
2000 ("./configure --with-debug etc.") for this to work.
2001 <P>
2002 Exit wmaker and start a failsafe X session with an open xterm.
2003 <P>
2004 First type the command "script" to log the following session into a
2005 file commonly called "~/typescript". Then enter "gdb wmaker" at the
2006 shellprompt:
2007 <P>
2008 <PRE>
2009 [shell prompt]~ > script
2010 Script started, output file is typescript
2011 [shell prompt]~ > gdb wmaker
2012 GNU gdb 4.17.m68k.objc.threads.hwwp.fpu.gnat
2013 Copyright 1998 Free Software Foundation, Inc.
2014 GDB is free software, covered by the GNU General Public License, and you are
2015 welcome to change it and/or distribute copies of it under certain conditions.
2016 Type "show copying" to see the conditions.
2017 There is absolutely no warranty for GDB. Type "show warranty" for details.
2018 This GDB was configured as "i486-pc-linux-gnu"...
2019 (gdb)
2020 </PRE>
2021 At the gdb prompt simply type "run" to start the WMaker session:
2022 <P>
2023 <PRE>
2024 (gdb) run
2025 Starting program: /usr/bin/X11/wmaker
2026 </PRE>
2027 Try to reproduce the error which has provoked the crash before and if
2028 you succeed the session will simply freeze and you will see something
2029 similiar to following prompt:
2030 <P>
2031 <PRE>
2032 Program received signal SIGSEGV, Segmentation fault.
2033 0x809ea0c in WMGetFirstInBag (bag=0x0, item=0x811e170) at bag.c:84
2034 84 for (i = 0; i < bag->count; i++) {
2035 (gdb)
2036 </PRE>
2037 Now you just type "bt" for "backtrace" and gdb will show you where the
2038 crash happened:
2039 <P>
2040 <PRE>
2041 (gdb) bt
2042 #0 0x809ea0c in WMGetFirstInBag (bag=0x0, item=0x811e170) at bag.c:84
2043 #1 0x807c542 in wSessionSaveState (scr=0x80c28e8) at session.c:299
2044 #2 0x807bd88 in wScreenSaveState (scr=0x80c28e8) at screen.c:1089
2045 #3 0x807cf54 in Shutdown (mode=WSExitMode) at shutdown.c:111
2046 #4 0x8078101 in exitCommand (menu=0x80f7230, entry=0x80fdb38)
2047 at rootmenu.c:193
2048 #5 0x8078403 in wRootMenuPerformShortcut (event=0xbffff360) at rootmenu.c:401
2049 #6 0x80630f7 in handleKeyPress (event=0xbffff360) at event.c:1492
2050 #7 0x8061c86 in DispatchEvent (event=0xbffff360) at event.c:232
2051 #8 0x8093092 in WMHandleEvent (event=0xbffff360) at wevent.c:585
2052 #9 0x8061dae in EventLoop () at event.c:322
2053 #10 0x806b238 in main (argc=1, argv=0xbffff404) at main.c:594
2054 (gdb)
2055 </PRE>
2056 To quit the debugger just type "quit" and say "y":
2057 <P>
2058 <PRE>
2059 (gdb) quit
2060 The program is running. Exit anyway? (y or n) y
2061 [shell prompt]~ >
2062 </PRE>
2063 To quit the script session type "exit" again:
2064 <P>
2065 <PRE>
2066 [shell prompt]~ > exit
2067 exit
2068 Script done, output file is typescript
2069 [shell prompt]~ >
2070 </PRE>
2071 Send the resulting "~/typescript" together with a concise explanation
2072 about how to reproduce the bug (please use the included BUGFORM for
2073 instruction) to the <A HREF="http://www.windowmaker.org/feedback.php?mailto=developers">developers</A>.<BR>
2074 </BLOCKQUOTE>
2075 <?
2076 }
2077 if ($chapter==8) {
2078 ?>
2079 <h1>Chapter 8: Troubleshooting Tips</h1>
2080 No questions are currently available for this chapter.</FONT>
2082 <?
2083 }
2084 if ($chapter==9) {
2085 ?>
2086 <h1>Chapter 9: Programming for Window Maker</h1>
2087 <UL type="disc">
2088 <B>9.1</B> <A href="#111">How do I get a normal X application to produce an appicon?</A><BR>
2089 <B>9.2</B> <A href="#112">How do I get my tcl/tk application to produce an appicon?</A><BR>
2090 <B>9.3</B> <A href="#113">What is WINGs?</A><BR>
2091 <B>9.4</B> <A href="#114">Where can I get more information about WINGs?</A><BR>
2092 </UL>
2093 </FONT>
2094 <BR><HR><BR>
2095 <A name="111"></A>
2096 <h2>9.1 How do I get a normal X application to produce an appicon?</h2>
2097 Another insightful answer from who else but Dan Pascu.
2098 <P>
2099 "You must define the WM_CLASS (XSetClassHint()) and the CLIENT_LEADER or
2100 XWMHints.window_group properties, which are automatically set by most
2101 applications that use Xt (Motif, Athena ...), but if you use plain Xlib you must set them
2102 by hand.
2103 <P>
2104 Also you must make a call to XSetCommand(dpy, leader, argv, argc);
2105 <P>
2106 Take a look at WindowMaker-0.12.3/test/test.c that is an example for writing such an
2107 app (which also have an app menu).
2108 <A name="112"></A>
2109 <h2>9.2 How do I get my tcl/tk application to produce an appicon?</h2>
2110 Oliver Graf writes:
2111 <P>
2112 The main window (normally this is called '.' [dot] in tk) should use the following lines:
2113 <P>
2114 <PRE>
2115 wm command . [concat $argv0 $argv]
2116 wm group . .
2117 </PRE>
2118 All child windows attached to the same app-icon should use:
2119 <P>
2120 <PRE>
2121 toplevel .child
2122 wm group .child .
2123 </PRE>
2124 where .child should be replaced by the actual window path.
2125 <P>
2126 Replace '.' with the actual main-window path and 'wm group .child .' should be
2127 added for each 'toplevel .child' call.
2128 <A name="113"></A>
2129 <h2>9.3 What is WINGs?</h2>
2130 WINGs Is Not GNUstep. ;)
2131 <P>
2132 It is the widget library written for the widgets in Window Maker.<P>
2133 It is currently under heavy development but several people have started
2134 writing applications in it. Its goal is to emulate the NeXT(tm)-style widgets.
2135 <P>
2136 <A HREF="http://www.ozemail.com.au/~crn/wm/wings.html">http://www.ozemail.com.au/~crn/wm/wings.html</A> is the closest thing to an
2137 information center about WINGs. You can find out more information in our
2138 <A href="http://www.windowmaker.org/development.php?show=wings">WINGs development</A> section.
2139 <A name="114"></A>
2140 <h2>9.4 Where can I get more information about WINGs?</h2>
2141 Nic Berstein has created a WINGs development list.
2142 <P>
2143 The purpose of this list is to provide a forum for support, ideas,
2144 suggestions, bug reports etc. for the WINGs widget set library.
2145 <P>
2146 To subscribe to this list, send a message with the word ``subscribe'' in
2147 the _BODY_ of the message to: <A HREF="mailto:wings-request@postilion.org"><wings-request@postilion.org></A>.<BR>
2148 </BLOCKQUOTE>
2150 <?
2151 }
2152 if ($chapter > 0) {
2153 ?>
2154 <HR size="1" noshade width="100%" align="center">
2155 <DIV align="center">
2156 <A href="FAQ.php">Top level of FAQ</A>
2157 </DIV>
2158 <?
2159 }
2160 ?>
2165 </td>
2166 </tr>
2167 </table>
2171 <?php include("footer.php"); ?>
2173 </body>
2174 </html>