Leopard weirdness

[Andreas Höschler]

Hi Christiaan

> Another change in behavior is tabbing. Previously tabbing would go 
> through a column and would be circular. Now it will go through a row, 
> and leave the table after the last column. I'm personally not sure if 
> going through a row was a good choice (I would have liked to have a 
> setting for that, as now I have to override it in some tableviews). 
> But being able to leave the table using tab is an improvement IMO.

The current (old) behaviour is that after editing the last column cell, 
pressing tab will bring you into the first cell/column of the next row. 
That's how it's supposed to be. I just realized that they have changed 
the behaviour to what your describe above. This is a very bad 
modification IMHO!!! :-(

Filling in a bunch of cells in a tableview is now close to impossible 
(terribly inefficient). One has to use the mouse to get into the 
tableview (again) after each row. And since a doubleclick no longer 
works one first has to select the next row manually, wait a second and 
then select the cell to be edited with another single-click. It could 
hardly be worse! Who has come up with that?? :-(

>
>>> You can't simply revert back to the old editing behavior, it would 
>>> require you to override several methods in NSTableView, like 
>>> mouseDown:. It's very tricky to do that correctly. Moreover, this is 
>>> now the standard behavior, so better be consistent. So I advice you 
>>> to get used to it.
>>
>> It's actually an incompatibility issue for us since some users are 
>> working on Macs, others (most) are working on Sun Rays 
>> (GNUstep/Solaris). But that's our problem and Apple couldn't care 
>> less. :-)
>>
>
> That's not an incompatibility. When you implement it correctly, it 
> will just work on both systems. It will just work differently on the 
> different systems.

That's the problem. If user switch between Mac and Sun Ray desktops 
they will get confused. But we can live with that. What concerns me 
more is this new tabbing behaviour. :-( Can that at least be modified 
with a default (old behaviour)?

>  On Leopard it will behave as I described, while on Tiger or 
> GNUstep/Solaris it will behave as before. Without the need to have 
> separate code paths or special overrides

Regards,

   Andreas