Tue 09 Nov 2004 06:51:51 PM UTC, original submission:
(Note: This may also be an AppKit issue, but it's far easier to reproduce this condition under Gorm, so this is how I'm categorizing this report.)
The first issue (there are two, but they seem very related) is that when I click in the rightmost portion of any NSTableView, an error, "not in frame, what's happening ?" is printed to standard output.
The second issue is that under particular circumstances, the column headers of an NSTableView are not drawn correctly. When this happens, the far right column is drawn in the left, and all other column headers aren't rendered.
To reproduce this: use Gorm 0.8.0 (or from CVS) to make a new application. Drop one NSTableView onto the main window, then drop another. When running a program with this interface, the first NSTableView you dropped onto the window will not render correctly. The second one does. However, both NSTableView column headers cause the program to print "not in frame, what's happening ?" to stdout when clicked on the far right.
Neither of these problems show up when using Gorm's "Test Interface". Also, this happens regardless of backend, or whether or not I have antialiased fonts enabled in the xlib backend.
A quick workaround: when you resize an NSTableView at runtime, both of the issues above disappear.
I've attached and thrown together a program that demonstrates all of these points.
|