Known bugs and limitations in Project Analyzer 3.1.x

Please report any new bugs to vbshop@netgate.net.


===========
Limitations
===========

- In the 16-bit version, the number of certain things (like vars/consts
  and references) is limited to 32767. If you encounter this problem,
  use the 32-bit version
- The size of variable, constant and procedure names is restricted to 64
  characters to save some memory. Longer names are truncated.

==================
Known misbehaviour
==================

- Long lines don't word wrap on some report types
- Reports to .wri files look ugly
- Long procedural call tree reports (All procedures) can hang the computer
- "Sub [Dis]ConnectAddIn" is never "dead" even if your app is not an add-in
- In the hypertext window, letters in DefType statements may be 
  mistaken for one-letter variable names
- Constant references in the (declarations) section are not interpreted. 
  This may cause the following code to show WM_USER as a "dead" const:
  Global Const WM_USER = xyz
  Global Const WM_HELLO = WM_USER + 1
- ReDim MyTable(N) inside a procedure may be interpreted 
  as a new local array, even if it's a dynamic global array. 
  This is not a problem with module-level arrays.

- MyClass.MyProperty = 987      works OK (MyProperty Let), but
  MyClass(123).MyProperty = 987 doesn't (thinks it's MyProperty Get)
                                Problem with subscript.

- In the hypertext window, if you have two different definitions with the
  same name (e.g. Form1.MyVar and Form2.MyVar), the program may
  highlight the both in red when the other one is highlighted


=======================
Unsupported VB 4.0 code
=======================

- Compiler directives (#if xyz then)
- Line continuation character "_"

========================
Deficiencies in FRX view
========================

- Shows only graphical data.
  Textual data (like the List property of a ListBox) is not shown.
- Doesn't understand if one control has more than 1 picture
  => Shows only one picture
- Understands the following properties: .Picture, .Icon and .MouseIcon
- Can't handle SSCommand.Picture. Seems to me that these pictures
  are stored differently

================
For best results
================

- Always declare your local variables (use Option Explicit)
- Always save your files as text (VB 3.0)
- Use MS Word as RTF editor
- Wait for the analysis to end completely (it has 2 phases)