[Gambas-user] Issue 113 in gambas: Database manager toolbar crashes IDE

[gambas at ...2524...]

Status: New
Owner: ----
Labels: Version Type-Bug Priority-Medium OpSys-Any Dist-Any Arch-Any  
Desktop-Any GUI-Any

New issue 113 by adamn... at ...626...: Database manager toolbar crashes IDE
http://code.google.com/p/gambas/issues/detail?id=113

1) Describe the problem.
Clicking on some of the toolbar buttons when there is no proper selection  
in the tableview on the table fields tab crashes the IDE with
[21] Out of bounds.
FConnectionEditor.tbvField_Click.550

2) GIVE THE FOLLOWING INFORMATIONS (if they are appropriate):
Version: TRUNK
Revision: r4147
Operating system: Linux
Distribution: mine ...
Architecture: x86
GUI component: QT4 / GTK+
Desktop used: LXDE

3) Provide a little project that reproduces the bug or the crash.
N/A

4) If your project needs a database, try to provide it, or part of it.
N/A

5) Explain clearly how to reproduce the bug or the crash.
This is a simple way to show the crash,  but it happens in other ways as  
well (see later)
a) create a new sqlite connection and a new sqlite database, called  
e.g. "crash"
b) open the connection (i.e. the database manager window)
c) click on "New Table" in the main toolbar, call it "test"
d) The table fields view is shown and it looks like the "id" field is  
selected
e) click on the Add button at the top of the Fields tab (i.e. try to add  
another field)
==> IDE "unexpected error"

This also happens when I
f) restart the IDE, and reopen the database manager for the "crash" database
g) click on the test table
h) click once on the "id" field (row still looks selected)
i) click on the add field button
==> same error

Same thing happens even if I click on the id field until the field name is  
highlighted and then click on the add field button

I also got his to happen with the field delete button and on one occassion,  
one of the move buttons.

It seems that the fields tableview is loosing focus after one of these  
buttons is clicked (but I dont know if that has anything to do with it).

6) By doing that carefully, you have done 50% of the bug fix job!

IMPORTANT NOTE: if you encounter several different problems or bugs, (for
example, a bug in your project, and an interpreter crash while debugging
it), please create distinct issues!