MySQL Bugs: #8225: Schemata dosen't show last entry

Bug #8225	Schemata dosen't show last entry
Submitted:	31 Jan 2005 23:12	Modified:	1 Mar 2005 13:57
Reporter:	Alistair Maclean	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.1.5	OS:	Windows (Windows)
Assigned to:		CPU Architecture:	Any

Description:
In some circumstances, the very last entry in a long list of table names, in the Schemata display will not be accessable. It's there, you can see it, but you just can't get to it without resizing windows. The last listed table name can disappear under the horizontal slider/resizer. 

This is a really silly trivial item, probably not worth the effort to fix, but I thought in the interests of usability it needed to be recorded.

How to repeat:
It occurs with the last listed database instance. The total number of displayed tables must exceed the capacity of the schemata window. At least one table name needs to be longer that the window can display, and displayed within the schemata window at the same time as the last table name. 

The last table name entry will disappear under the horizontal slider - needed to allow viewing of the long table name. The now hidden table name can be seen if you grab the vertical slider and force it down to the bottom, but the entry cannot be clicked on.

If the schemata window is widened to allow full display of the long name, or the whole Query Browser window is shortened to make the schemata window short enough to hide that long entry then the last entry can be accessed again.

Suggested fix:
My guess is that the code that automatically causes the horizontal slider to appear needs to indicate it is present, and then the vertical slider can be made to go down one extra increment if it detects the horizontal slider.

Hi,

Thank you for the report, but I wasn't able reproduce it with my test tables.
What is the table name that QB doesn't display?
How many tables are listed?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".