Known Problems for Win32 version (Last update 9/23/99)
------------------------------------------------------

Note: This list predates our bugzilla database and is basically obsolete
at this point. For the current bugs listing you should check the online
bugzilla database; see the link from the FOX home page.

 o  The addInput() and removeInput() methods for FXApp, and related
    messages, are not supported under Windows.

 o  The FXDCWindow class has not been fully exercised yet and there are, no
    doubt, some differences between it and the X version. I think a
    good approach would be to develop a FOX test app which demonstrates
    all of the "DC" functions and then compare X & Windows versions side
    by side.

 o  Problems for the date/time representation used by the file list and
    directory list -- string repr.

 o  When the machine is especially loaded up, FOX doesn't seem to process
    its SEL_ENTER and SEL_LEAVE messages appropriately. This is most
    noticeable on toolbars with "coolbar"-style buttons in them; they pop
    up as the mouse moves over them and are supposed to pop back down when
    the mouse leaves, but they don't always do that.

 o  You cannot set the large and small icons for top-level windows (such
    as FXMainWindow). These settings are ignored.

 o  Should investigate the use of DeferWindowPos() to see if it speeds
    up window layout.

 o  Whenever we display a tooltip popup, the mouse cursor temporarily "enters"
    that window and we get a WM_MOUSEMOVE message which FOX translates into
    a SEL_MOTION message. In other words, even though you didn't move the
    mouse cursor, FOX thinks you did. This has the side effect (in some cases)
    of tooltips which flash repeatedly (see, e.g., an FXTreeList).

 o  For some graphics boards (like Vadim's) the FXGLViewer::drawLasso
    routine doesn't clean up after itself, so we see ghosts of the
    intermediate lasso-rectangles.

 o  For some graphics boards (like Vadim's) the FXGLViewer doesn't always
    repaint itself when you call FXGLViewer::update().

Possible bugs observed in the MDI test program:

 o  Click on the MDI child window which contains a button. Then
    click in the client area of a scroll window underneath it; it doesn't
    come to the top. It does if you click on its title bar, however.

 o  Click the Window menu item and then click on the menu bar itself (i.e.
    somewhere between the menu titles). Then try clicking any of the MDI
    child windows; they will not activate.

 o  Restart the program and click on File->New. The new child window does
    not appear. You have to click Window->Cascade or Window->Tile to see it.

Other Known Problems:
=====================

 o  Unable to specify some options after construct time:

        ARROW           FXArrowButton
    *   BUTTON          FXButton
        CHECKBUTTON     FXCheckButton
    *   DIAL            FXDial
    *   DIRLIST         FXDirList
    *   FRAME           FXWindow
    *   FILELIST        FXFileList
        GROUPBOX        FXGroupBox
    *   HSCROLLING      FXScrollWindow
    *   ICON/TEXT       FXFrame
    *   ICONLIST
    *   JUSTIFY         FXFrame
    *   LAYOUT          FXWindow
    *   LIST            FXList
    *   MATRIX          FXMatrix
    *   MENUBUTTON      FXMenuButton
    *   PACK            FXWindow
    -   PROGRESSBAR     FXProgressBar (allows setting percentage but not vertical)
        RADIOBUTTON     FXRadioButton
        SEPARATOR       FXFrame
    *   SLIDER          FXSlider
    *   TEXTFIELD       FXTextField
        TOGGLEBUTTON    FXToggleButton
    *   TREELIST
