Comments on: Stay Responsive http://www.red-sweater.com/blog/229/stay-responsive Mac & Technology Writings by Daniel Jalkut Sun, 16 Mar 2014 19:39:31 +0000 hourly 1 http://wordpress.org/?v=3.8.1 By: Jon Crosby http://www.red-sweater.com/blog/229/stay-responsive/comment-page-1#comment-31261 Wed, 06 Dec 2006 12:05:47 +0000 http://www.red-sweater.com/blog/229/stay-responsive#comment-31261 Daniel, thank you for the tip! This works like a charm. And for what its worth, this very situation where a user clicks the plus button before “officially” ending their editing task seems to have popped up with a decent number of Actiontasic users. I imagine that some of them get in a routine of typing while leaving the mouse over the plus button for a quick click when entering a series of items.

]]>
By: Mike Abdullah http://www.red-sweater.com/blog/229/stay-responsive/comment-page-1#comment-30498 Sun, 03 Dec 2006 15:08:24 +0000 http://www.red-sweater.com/blog/229/stay-responsive#comment-30498 A very good point. I shall have to look into this :)

]]>
By: Daniel Jalkut http://www.red-sweater.com/blog/229/stay-responsive/comment-page-1#comment-30247 Sat, 02 Dec 2006 16:21:57 +0000 http://www.red-sweater.com/blog/229/stay-responsive#comment-30247 Mike: but when the sheet is then dismissed, your user would probably prefer to have the original focused field remain focused. That’s exactly the situation I’m contending with here.

]]>
By: Mike Abdullah http://www.red-sweater.com/blog/229/stay-responsive/comment-page-1#comment-30206 Sat, 02 Dec 2006 13:01:36 +0000 http://www.red-sweater.com/blog/229/stay-responsive#comment-30206 Ah, I hadn’t realised that -commitEditing messed with the first responder. I guess I think I must of only ever used it in situations where a sheet is about to appear, so the first responder doesn’t matter.

]]>
By: Jim Correia http://www.red-sweater.com/blog/229/stay-responsive/comment-page-1#comment-30017 Fri, 01 Dec 2006 20:00:06 +0000 http://www.red-sweater.com/blog/229/stay-responsive#comment-30017 Mike,

-commitEditing is a the correct way to end editing for views bound to a controller. However, this has the same problem Daniel sought to avoid – after you are finished the window’s first responder is no longer the control the user left keyboard focus in. (And it requires the same sort of treatment.)

]]>
By: Mike Abdullah http://www.red-sweater.com/blog/229/stay-responsive/comment-page-1#comment-29991 Fri, 01 Dec 2006 17:29:07 +0000 http://www.red-sweater.com/blog/229/stay-responsive#comment-29991 Personally, I’ve always found NSObjectController and -commitEditing to work nicely.

]]>
By: Jim Correia http://www.red-sweater.com/blog/229/stay-responsive/comment-page-1#comment-29954 Fri, 01 Dec 2006 14:39:42 +0000 http://www.red-sweater.com/blog/229/stay-responsive#comment-29954 “continuously updates value” has its uses, but it isn’t always the right solution. One time where you don’t want to do this is when setting the value on the model is undoable.

Imagine typing “Fred” for someone’s name, then committing the edit in the field.

Undo should put it back to its previous value, without requiring you to step through

“Fre”
“Fr”
“F”
“Previous Value”

]]>
By: Daniel Jalkut http://www.red-sweater.com/blog/229/stay-responsive/comment-page-1#comment-29947 Fri, 01 Dec 2006 14:18:50 +0000 http://www.red-sweater.com/blog/229/stay-responsive#comment-29947 ssp: I can see that as a sort of ideal user experience – sometimes. Though frankly I think even the ideal behavior of, for instance, a text title simultaneously updating a window’s title as the user types would be so contrary to the ordinary behavior that some users might annoyed or distracted by it.

One problem that comes to mind is that by sending continuously you’d be exercising the formatter and/or validation method for the field, probably before the user has finished typing valid information. This has the potential to cause text fields to behave like those infuriating telephone-entry fields, where you never know whether the computer or the user is responsible for tabbing to the next field.

In general, I’d be wary of violating the traditional “safe, ponderous editing” phase that users now enjoy in most text fields.

]]>
By: ssp http://www.red-sweater.com/blog/229/stay-responsive/comment-page-1#comment-29883 Fri, 01 Dec 2006 10:16:42 +0000 http://www.red-sweater.com/blog/229/stay-responsive#comment-29883 I’m with ken on this… immediate updating is the way to go.

]]>
By: Daniel Jalkut http://www.red-sweater.com/blog/229/stay-responsive/comment-page-1#comment-29822 Fri, 01 Dec 2006 05:13:59 +0000 http://www.red-sweater.com/blog/229/stay-responsive#comment-29822 ken: whoah, I hadn’t considered that the “continuously updates value” option could be applied to a text field. But in this case I think it would be overkill because it’s only in the very specific situation that a user chooses to export that I want to “immediately update.”

]]>