These are the known problems in version 1.0 of Wing IDE.

* = Most critical items
- = All other items

Install
-------

* The tar format install doesn't do a check for dependencies, such
  as glib and gtk and enscript.  Use RPM, if you can, to avoid this.

Code browser
------------
* Opening some large files in the module view is very slow:  This is
  caused by presence of a 'from xxx import *' statement.
* Selecting on the filter check boxes can be sluggish if a lot of
  items are on the display
- Directory node doesn't auto update when directory contents change
  on disk

Code Analysis (affects browser, auto-completion, and editor popup menu)
-------------
* List of names in a method is wrong within a nested function
* Deleting and then restoring the end of a triple quoted string or 
  other continued line terminator may cause the rest of the buffer 
  to fail to be re-analyzed (work around: re-open the file without 
  closing it; this will cause from-scratch reanalysis)
- If multiple different functions or classes with the same name exist 
  in the same file, the construct names retrieved for these may be incorrect

Project manager
---------------
- Docstring area is not changed correctly when right-click is used on items
  (left-click works)
  
Gui Manager
-----------
* Text copied from other applications may not be pasted into an editor if
  text has been copied previously in Wing.  Workaround: use the middle
  mouse button to paste into the editor. 
* Real usable screen size isn't detected when running in an environment 
  with borders such as those in KDE or Gnome.  Workaround:  Set the
  gui.work-area-rect preference to limit Wing's use of screen space
* Assigning keyboard accelerators to menu items by pressing a key when 
  the item is displayed and selected (a gtk feature) screws up our key 
  accel table.
- Iconized windows don't show up when they are supposed to receive focus
  (e.g., when selected from windows menu or debugger tries to show the window)
- Window title only updates after editor gets focus after a name change.
- "Windows" menu width increases if it's torn off and the focus window
  changes
  
Source Editor
-------------
* Autocompletion bugs -- See the Code Analysis section above
* Setting/removing breakpoints cannot be done by clicking on the margin 
  in editor (currently need to position cursor and then use toolbar,
  menu item, or keyboard equivalent)
* Printing Python doesn't work if Adobe Acrobat isn't available.
  Work around:  Set edit.print-python-as-text=true in your preference file
  (but this gives only basic printing without hilighting Python language 
  keywords)
* Print is disabled on new files until you save the file to disk
- ~ and // in emacs mode file selection do not do what they should
- vi-style tab width recognized by the python tokenizer is not supported.

Debugger
--------
* In applications based on some GUI libraries (e.g., WXPython) where most 
  of the time is spent in C or C++ code, the debugger may time out if 
  you try to add breakpoints during a run, and on some other operations.
* Debugger filters out configured items like functions even if they
  are found in user-defined variables, parameters, and instance attributes
- Conditional breakpoints always stop if an exception is caused by
  the condition itself, but the exception is never reported to the user
- $WINGHOME/debug/server should not be in the PYTHONPATH when debuggee runs.