=============================================================================
Known Problems
=============================================================================

This section lists known limitations and problems in the Wing IDE product 
line.  Items are categorized as follows:

x : Common problems that are not bugs in Wing IDE
* : High priority bugs
- : Lower priority bugs

Please send bug reports and feature requests to bugs@wingide.com.

-----------------------------------------------------------------------------

x Python 2.1 nested scope of class within a function def will cause
  the debugger to segfault when the tracer hits a 'class' defn within the
  function. This is a bug in Python 2.1.0 but was fixed in 2.1.1.  A
  work-around for Python 2.1.0 is to use wingdbstub and issue the SuspendDebug() 
  call before the problem code is hit, and ResumeDebug() afterwards.
x Upgrading doesn't always work when bug fix patches have been applied.
  Uninstalling completely first works.
x Wing may fail to start a debug session if Python was installed directly
  over another older Python installation (in same disk location).  Uninstall 
  Python, remove all remaining files manually, and reinstall Python.
x Win32:  Cannot debug files on \\machine\path\to\share directories that 
  aren't mapped to a drive letter.
x Debugger may fail to report errors occurring during initial load of the 
  debug program; if this happens, turn on debug.verbose or set debug.logfile 
  preferences and try again; debug output will be shown in stderr or the 
  given log file (which must exist or else logging will be disabled)
x When debugging X code that calls XGrabPointer and similar calls, the 
  X server may remain locked when a breakpoint or exception is reached.
  The work-around is to conditionalize use of XGrab* so these calls are
  not made when in debugging mode.
x External change checking does not work for Samba volumes
x Wing may not start up on a Windows terminal server.  See the FAQ for
  a work-around.
x Hummingbird Socks Client has been known to break or hugely slow down
  debugging on Windows.
x Uncradling an iPaq while Wing is running may crash Windows

* Setting PYTHONHOME will cause Wing to fail to start up.  Work around:
  Set this instead in the Environment area of the Project Properties dialog.
* New Blank Window from the file menu sometimes requires a click on the window
  to get a newly opened view to appear in it instead of another window
* On win32 dual monitors, pull down menus show up on the primary monitor
  even if the window is on the secondary monitor

- Wing can time out during startup of debug process in some cases if files 
  have been altered outside of Wing.  Removing all breakpoints before starting 
  the process works around the problem.
- AnyGUI's msw (PythonWin) back end breaks Pause and altering breakpoints
  while the debug process is free-running.  Tk back end is known to work, 
  as should also wx and qt.
- Break point margin click doesn't work in source browser window
- Editor scrolling is off by one pixel on win32:  Artifacts appear at bottom 
  and right if window is just the right size.
- About box image sometimes looks odd when running on a display in 256 
  color mode.
- Windows menu slowly grows horizontally over time, as it is used

Notes for Mac OS X Beta
=======================

x Right-click for menus by holding down the option/alt key while clicking;
  Middle-click by holding down the control key while clicking
x Mod1 (Alt) is remapped by Wing IDE at startup to the apple key, replacing
  the defaults for that key.  To avoid this, set the preference
  main.alter-xmodmap=false and set up your own xmodmap settings.
* Printing is not yet available on OS X
- Pause does not work when debug process is in input() or raw_input()