============================================================================= 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 - : Known bugs in Wing IDE Please send bug reports and feature requests to bugs@wingide.com. ----------------------------------------------------------------------------- x The Wing debugger may fail to work with a Python installation that was installed over another Python version. This is true of all forms of installer (RPM, source build, and Windows installer). To avoid this, uninstall, remove remaining files manually, and reinstall the desired version of Python. 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 Hummingbird Socks Client can break or slow down the Wing debugger on Windows 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 Wing doesn't always work when bug fix patches have been applied. Uninstall completely and remove remaining files manually to avoid this. x Cannot debug files on Windows \\machine\path\to\share directories that aren't mapped to a drive letter. x External file change checking does not work for Samba volumes - 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 - 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. - Editor scrolling is off by one pixel on win32: Artifacts appear at bottom and right if window is just the right size. - 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