boa-constructor / Bugs.txt

Bugs & Issues 
-------------

A strange thing which sometimes happens is that Boa uses 100% CPU after startup
on windows. Just minimizing and restoring the application makes the CPU return 
to 0%. Bizarre!

Sometimes (but rarely) Boa crashes at startup while opening files in the Editor.
To get around it you may start Boa with the command-line switch -E which will
start with an empty Editor. I don't think it's a Boa bug.

---
Current Designer behaviour may seem weird where a
single control is dropped on a frame; At first the control keeps its
default size, but when the frame is resized, it fills the frame.
(toolbars, statusbars and menubars connected to the frame are 
excepted from this rule)
This behaviour emulates the way frames/containers auto sizes a control 
if only one is dropped on a frame/container, but it gives you the 
chance to add a second control (before it fills the parent). 
If you have a control filling a parent and want to add another to
the parent, resize/move it out of the way and drop the second
(painful I know)

White space is quite significant for collection item methods!
The spacing/blank lines within the method delimit the 3 possible
sections, I might change this to rather be delimited by comments
(but I don't want to have meaningfull comments either :( )
Anyway don't mess with the whitespace and expect this to change.

Another biggish gotcha is that changes to many (there are exceptions) 
constructor properties and collection item constructor properties 
will only take effect after the frame has been opened and closed
or the property refreshed.
This is partially due to constructors only being called once ;)

Cyclops and wxGenButtons don't mix for some strange reason. Disable
any wxGenButtons code before running Cyclops.
To run Boa in Cyclops, turn the cyclopsing flag on in Palette.py

Other bugs
----------

Recreate controls not implemented for the Data View.

ToolBars confuse the Designer somtimes (and the author).
Components are offset by the height of the toolbar

Toolbars still cause big trouble by moving the frame coordinates down
when linked to a frame.
The only way I can see this working is by always having the toolbar
as the first component and immediately linking it before creating any
other components (this breaks the pattern completely ouch :()
Also have to compensate for all top level controls (ctrls directly on
frame) by adjusting their coordinates upon linking of the toolbar,
because their source won't be updated.
The moral of the story is to not have controls directly on a frame for
now, rather put them in a panel, this is the recommended procedure
in any case.

Parser must be fixed sometime to correctly parse
nested methods and nested classes

GTK
---

Still some problems with accelerator keys.

GTK Critical warnings are produced in the following cases:
- When there is a 'New' submenu connected under 'File'. Off by default on wxGTK.
- When controls are reparented from the Notebook to another control. 

---

Find in App does not search app

moduleparse.Module.name sometimes have extension, sometimes not. Decide!

Remove the silly assert for local uris (assertLocalFile), should be 
checkLocalFile that raises a TransportError

Top of Notebook now triggers selection but with wrong offset

Check AccelEnter -> Notebook paste bug

refreshCtrl is called twice on open pyd

Snap to grid snaps more to left/top sides
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.