Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

NSTextField Bug? Can't be!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

NSTextField Bug? Can't be!

Subject: NSTextField Bug? Can't be!
From: Seth Willits <email@hidden>
Date: Mon, 11 Aug 2008 22:31:25 -0700

If a text field has focus, you type "blah blah blah" into it, and then click a button which asks for its string value and disables the text field, you get "blah blah blah" back.

If a text field has focus, you type "blah blah blah" into it, and then click a button which disables the text field first and then asks for its string value, you get an empty string...

I can make up some reasoning in my head for why that'd make sense, but it just doesn't sit well with me. If the text is *IN THE FIELD* before the field is disabled, then clearly it should be considered its string value. I can't imagine this being a bug simply because *somebody* would have noticed and fixed it by now, but I can't understand why this would be desirable behavior.

--
Seth Willits


_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


Follow-Ups:

Re: NSTextField Bug? Can't be!
From: Graham Cox <email@hidden>


Prev by Date:
Re: Copying id

Next by Date:
Re: Delayed termination to allow release

Previous by thread:
Re: applicationShouldOpenUntitledFile question

Next by thread:
Re: NSTextField Bug? Can't be!

Index(es):

Date
Thread