Leopard weirdness

[Andreas Höschler]

Hi all,

we are in the process of migrating our software from MacOSX 10.2 and 
GNUstep to MacOSX 10.5 and figured out a bunch of weird issues 
[modifications to AppKit we dislike to say the least, or that we don't 
understand yet] that prevent our apps from working properly.

Our apps build NSTableViews programmatically (based on a property list) 
and sets the columns to editable or not using [tableColumn 
setEditable:flag]. All our tableviews also get

	[tableView setDoubleAction:@selector(performDoubleActions)];
	[tableView setTarget:self];

The behaviour we expect and are used to since the old OPENSTEP days 
(the same on MacOSX 10.2 and GNUstep) is that a doubleclick in an 
editable column starts editing the cell, a doubleclick on a 
non-editable column invokes the doubleaction of the tableview. On 
MacoSX 10.5 the action is always invoked, no cell is editable anymore 
whether setEditable:YES was invoked or not. :-( Is this supposed to be 
a feature? If so I don't understand the reasoning. Or am I missing 
anything.

We commented out the line that sets the action for now. Now the columns 
that got a setEditable:YES are editable. However, one has to do a 
direct hit on the text to start editing. If one doubleclicks slightly 
to the right of the text (but still within the cell) editing is not 
started anymore. This is pretty annoying!! :-(

Please tell me that I am doing things wrong and that these 
incompatibilities can be overcome with a few #ifdefs! I can't believe 
what I see...

Thanks,

   Andreas