@node Frequently Asked Questions, Related Software, Customization, Top
@comment  node-name,  next,  previous,  up
@chapter Frequently Asked Questions

@menu
* Netscape is not refreshed correctly::  
* Core Dump on Startup::        
* Missing Icons but Path is right::  
* Application fails to dock::   
* I want to suppress the App Icon::  
@end menu


@node Netscape is not refreshed correctly, Core Dump on Startup, Frequently Asked Questions, Frequently Asked Questions
@comment  node-name,  next,  previous,  up
@section Netscape is not refreshed correctly

This problem is not specific to WindowMaker. I noted this problem
with AfterStep, fvwm2 and olwm. It's probably something with Netscape
or XFree86. Note that this only happens when a menu or icon is
laying over the affected window. 

Fix:

@itemize @minus
@item Don't place menus over Netscape. 
@item Turn UseSaveUnders off.
@end itemize

@node Core Dump on Startup, Missing Icons but Path is right, Netscape is not refreshed correctly, Frequently Asked Questions
@comment  node-name,  next,  previous,  up
@section Core Dump on Startup

At present the code is not yet 100% fail-safe in situations where WindowMaker cannot
determine the path to an important program or directory.  Make sure that

@itemize @minus 
@item the user actually has the @file{~/gnustep/Library/WindowMaker/} directory so
that it can write the @file{dock} file.
@item the @b{Path} to your C pre-processor (cpp) is correct
(In Solaris System (and probably other SysV boxes), this is usually in
@file{/usr/ccs/lib/cpp}.
@item that the C pre-processor is compatible with GNU cpp.  Sun's cpp seems to require
extra options.  For example, @file{cpp -B} for the @file{//} style comments.  (We would
welcome more info regarding this).
@item you paid your taxes
@end itemize

@node Missing Icons but Path is right, Application fails to dock, Core Dump on Startup, Frequently Asked Questions
@comment  node-name,  next,  previous,  up
@section Missing Icons but Path is right

Are you sure?  Look again!  Note that there is a subtle detail which must be obeyed when
creating the paths.  You must make sure that you have a terminating @file{/} at the end of
each path, otherwise the path missing this closure will be invalid. For example, a path
specified as 

@example
PixmapPath=/usr/X11R6/include/X11/pixmaps/NeXT/:\
           /usr/local/GNUstep/Library/WindowMaker/Pixmaps:\
          ~/gnustep/Library/WindowMaker/Pixmaps/
@end example

@noindent will fail to load any icons located in
@file{/usr/local/GNUstep/Library/WindowMaker/Pixmaps} since the closing @file{/} is
missing.  Thus, the correct statement would be

@example
PixmapPath=/usr/X11R6/include/X11/pixmaps/NeXT/:\
           /usr/local/GNUstep/Library/WindowMaker/Pixmaps/:\
          ~/gnustep/Library/WindowMaker/Pixmaps/
@end example

@node Application fails to dock, I want to suppress the App Icon, Missing Icons but Path is right, Frequently Asked Questions
@comment  node-name,  next,  previous,  up
@section Application fails to dock

For applications to be properly dockable, you have to add session management support. Not
everything in the protocol is needed.  The important bits are the window properties

@itemize @bullet
@item WM_COMMAND
@item WM_CLIENT_LEADER
@item WM_CLASS
@end itemize

If an application fails to dock, it is because either or all of this information is
missing.  For example, Netscape fails to dock on it's own, XMosaic doesn't.  You are now
left with the following options

@enumerate
@item Look in the distributions @file{patches} directory to see whether a patch is
available
@item Convince the author or supplier to write X applications propperly @t{:)}
@item Add the missing bits yourself if you have access to the sources
@item Use the supplied dockapp script, which is found in the distributions @file{utils}
directory. 
@end enumerate

@node I want to suppress the App Icon,  , Application fails to dock, Frequently Asked Questions
@comment  node-name,  next,  previous,  up
@section I want to suppress the App Icon

If you intend to dock an application but don't want an Application Icon on startup (like
it is the case for @file{asclock}), try adding the following to the @file{app_options} file

@example
wmload.StartWithdrawn: true
@end example


