On Sun, Jul 25, 2010 at 09:27:06PM +0000, Fred Kiefer wrote: > > Follow-up Comment #1, bug #30539 (project gnustep): > > This is another controversial change.
Agreed. They were both submited largely for documentation and discussion purposes; and as I mentioned since the 'we should be compatible with OSX' view had been expressed. The same program I mentioned earier also highlighed this. Given the various views expressed over the years wrt to what backspace should generate in xterm and stty settings, I expected this one to be controversial. > When changing the key mapping here we also need to adjust the mapping > in NSInputManager Thanks for the pointer. My program is currently avoiding the input manager until I get some other stuff sorted out. So something else to look at if this is not accepted and I simply use it as a private patch. > and make sure that all applications relying on the current behaviour get > corrected as well. > > As I understand it, you tested the behaviour on an Apple computer and found > that the backspace key produces an NSDeleteCharacter. Yup. So does OPENSTEP for MACH 4.2, fwiw. > Looking through the Google hit for NSDeleteCharacter there seems to be a lot > of confusion even among the Apple developers. So I see, but it looks as if the confusion arises from the name of the enums. It does rather beg the question about what a bunch of the various NSxxxFunctionKey things were defined for. Maybe expectations of use if openstep had got wider acceptance? _______________________________________________ Bug-gnustep mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnustep
