Known Problems in MagiCapture
=============================

 1. In certain cases, the configure script will not find the header
    files and libraries necessary to compile MagiCapture. If you are
    sure you have the latest version of all required libraries, perform
    the following steps:
 
    a. Add the header file path(s) to the CFLAGS environment variable
       using the -I option.

    b. Add the library path(s) to the LDFLAGS environment variable
       using the -L option.
 
    c. Remove the config.cache file, if it exists, and re-run
       the configure script.

    The following is an example of adding header and library paths,
    using a Bourne-compatible shell. In this example, X11 is installed
    in the /usr/local/X11R6 directory and ImageMagick is installed in
    the /opt/ImageMagick directory. MagiCapture will be installed in the
    /opt/MagiCapture directory.

       CFLAGS="-O2 -I/usr/local/X11R6/include -I/opt/ImageMagick/include" \
       LDFLAGS="-s -L/usr/local/X11R6/lib -L/opt/ImageMagick/lib" \
       ./configure --prefix=/opt/MagiCapture

 2. MagiCapture uses the XImportImage function call in the
    ImageMagick API in order to capture a single window, a rectangular
    region, or the entire display. Because of this feature, there are
    several points to consider:
 
    * If you are choosing to capture a single window, be sure
      that you are not clicking or holding down any of the mouse buttons
      upon the end of the pre-capture delay. Otherwise, the XImportImage
      call will fail because it can't use the mouse.

    * If you wish to capture a transient window, such as a menu,
      you will need to capture the full screen while selecting the menu in
      question. The current version of ImageMagick used at the time of this
      writing (Version 4.2.8) does not properly capture all types of menus
      in all circumstances.

 3. A progress dialog box appears when an image is being saved. Sometimes,
    the dialog box will remain empty even as the file is being written to
    disk. The WriteImage function call in ImageMagick blocks the GUI,
    preventing GTK+ from fully updating the dialog box contents before
    saving the file.

