Comments on: Bad UI: The Pulsing Taunt of Futility http://nslog.com/2003/02/25/bad_ui_the_pulsing_taunt_of_futility The Weblog of Erik J. Barzeski Wed, 08 Oct 2008 09:59:04 +0000 http://wordpress.org/?v=2.6.2 By: Josh http://nslog.com/2003/02/25/bad_ui_the_pulsing_taunt_of_futility#comment-735 Josh Wed, 26 Feb 2003 04:26:46 +0000 http://nslog.com/2003/02/25/bad_ui_the_pulsing_taunt_of_futility/#comment-735 Not sure why you thought reinstalling the OS would help...wouldn't all the updates have fixed it if it was a hiccup :) Anyway, it's quite easy to write an app that doesn't bind the default to return. In Interface Builder, at least, you need to set the button's key to return. Open it up, throw a button in the nib, and check out the inspector + test the app if you don't believe me. Not sure if it was hard-wired into the ROM, though... Not sure why you thought reinstalling the OS would help...wouldn't all the updates have fixed it if it was a hiccup :)

Anyway, it's quite easy to write an app that doesn't bind the default to return. In Interface Builder, at least, you need to set the button's key to return. Open it up, throw a button in the nib, and check out the inspector + test the app if you don't believe me.

Not sure if it was hard-wired into the ROM, though...

]]> By: Fred http://nslog.com/2003/02/25/bad_ui_the_pulsing_taunt_of_futility#comment-734 Fred Wed, 26 Feb 2003 03:53:51 +0000 http://nslog.com/2003/02/25/bad_ui_the_pulsing_taunt_of_futility/#comment-734 Ooh! I thought it was just me! In fact, I've been grimly contemplating the horror that is reinstalling OS X just so I can continue to save files using the keyboard. I thought it was some hiccup with the Finder, or, or, or... I never thought to inventory the failure by app. I've been so used to it NEVER failing on the Mac (since System 4.1 / Finder 3.2) that I figured it was a failure in the "new" OS X and not in individual apps. D'oh! In fact, how is it even possible to write an app for the Mac that doesn't recognize Enter/Return as an acceptable alternative for the default/highlighted button? Didn't that use to be hardwired into the ROM on older Macs? Ooh! I thought it was just me! In fact, I've been grimly contemplating the horror that is reinstalling OS X just so I can continue to save files using the keyboard. I thought it was some hiccup with the Finder, or, or, or... I never thought to inventory the failure by app. I've been so used to it NEVER failing on the Mac (since System 4.1 / Finder 3.2) that I figured it was a failure in the "new" OS X and not in individual apps. D'oh!

In fact, how is it even possible to write an app for the Mac that doesn't recognize Enter/Return as an acceptable alternative for the default/highlighted button? Didn't that use to be hardwired into the ROM on older Macs?

]]> By: Eric Wang http://nslog.com/2003/02/25/bad_ui_the_pulsing_taunt_of_futility#comment-733 Eric Wang Wed, 26 Feb 2003 00:14:15 +0000 http://nslog.com/2003/02/25/bad_ui_the_pulsing_taunt_of_futility/#comment-733 On a related note, I wish Apple would come up with a way to have nested sheets. For example, when creating a new folder in a document-modal save sheet, an application-modal dialog box will pop up, thus destroying the sheet's document-modality. On a related note, I wish Apple would come up with a way to have nested sheets. For example, when creating a new folder in a document-modal save sheet, an application-modal dialog box will pop up, thus destroying the sheet's document-modality.

]]> By: Irate Scotsman http://nslog.com/2003/02/25/bad_ui_the_pulsing_taunt_of_futility#comment-736 Irate Scotsman Tue, 25 Feb 2003 21:57:03 +0000 http://nslog.com/2003/02/25/bad_ui_the_pulsing_taunt_of_futility/#comment-736 <strong>I thought we'd discussed this...</strong> For annoying default/cancel buttons, you can't beat Netscape. I thought we'd discussed this...

For annoying default/cancel buttons, you can't beat Netscape.

]]> By: Kalle http://nslog.com/2003/02/25/bad_ui_the_pulsing_taunt_of_futility#comment-732 Kalle Tue, 25 Feb 2003 21:22:18 +0000 http://nslog.com/2003/02/25/bad_ui_the_pulsing_taunt_of_futility/#comment-732 Indeed it's irritating, inconsistent, and ridiculous. How should one report (or fix) each instance? Indeed it's irritating, inconsistent, and ridiculous. How should one report (or fix) each instance?

]]> By: Erik J. Barzeski http://nslog.com/2003/02/25/bad_ui_the_pulsing_taunt_of_futility#comment-731 Erik J. Barzeski Tue, 25 Feb 2003 18:36:44 +0000 http://nslog.com/2003/02/25/bad_ui_the_pulsing_taunt_of_futility/#comment-731 It happens in too many applications. Intermittently. Rather, it seems more an issue with the Carbon and Cocoa responder chains. I'd say "careless developers" but this is something they aren't supposed to have to code for: a pulsing blue button should respond to "enter" so long as its window - or any subview - has keyboard focus. It happens in too many applications. Intermittently. Rather, it seems more an issue with the Carbon and Cocoa responder chains. I'd say "careless developers" but this is something they aren't supposed to have to code for: a pulsing blue button should respond to "enter" so long as its window - or any subview - has keyboard focus.

]]> By: Eric http://nslog.com/2003/02/25/bad_ui_the_pulsing_taunt_of_futility#comment-730 Eric Tue, 25 Feb 2003 18:33:38 +0000 http://nslog.com/2003/02/25/bad_ui_the_pulsing_taunt_of_futility/#comment-730 Time for another bug report, eh? :-) Time for another bug report, eh? :-)

]]>