Re: [bug #30538] X11 backend should generate NSBackTabCharacter for shift-tab

[Fred Kiefer]

Thank you Derek for this additional explanation.

Now that I know that GNUstep has been incorrect even with regard to
OpenStep, I am going to change these two character values. Could
everybody out there who is managing a GNUstep application please see,
whether this handles NSTabCharacter and/or NSBackspaceKey. In that case
the application should be extended to handle NSBackTabCharacter the same
as NSTabCharacter plus shift and NSDeleteCharacter the same as
NSBackspaceCharacter or NSBackspaceKey.

There is one place where I am unsure about the concequences of this
change, that is key equivalents for menu items. These are stored in Gorm
or NIB files and any menu item with a backspace key equivalent may just
no longer work after this change.

Fred

Am 25.07.2010 23:51, schrieb Derek Fawcus:
> On Sun, Jul 25, 2010 at 08:58:48PM +0000, Fred Kiefer wrote:
>>
>> Update of bug #30538 (project gnustep):
>>
>>                   Status:                    None => Need Info              
>>              Assigned to:                    None => FredKiefer             
>>
>>     _______________________________________________________
>>
>> Follow-up Comment #1:
>>
>> Could you please explain the benefit of this change?
> 
> Just the general view that has been expressed a few times about how
> we should try to mirror OSX behaviour.  It is one less thing to deal
> with if/when porting between the two systems.
> 
> In this case (and the backspace/delete one) this is not only the
> OSX behaviour,  it is also the NeXT OPENSTEP behaviour,  so one
> could possibly make an argument that GNUstep has always been wrong.
> I don't know what Solaris OpenStep libraries did for this case,
> and maybe that would argue in the other direction.
> 
>> But this also requires that every application out there that has
>> special handling for tab and shift-tab build in will have to add a
>> special case for backtab as well.
> 
> Yup.  But then I found it because a program I'm writing and testing
> on OSX and GNUstep simultaneously needed special case code for this
> as things stand.  One way or the other will require extra code.
> 
>> Before we go out and break all these application we should know whether it is
>> worth it.
> 
> That'll have to be someone else's call.  What is compatibility with OSX worth?
>