|Subject:||NSTextField setStringValue nil value|
|Date:||Fri, 20 Apr 2012 20:09:03 +0200|
|User-agent:||Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120324 Firefox/11.0 SeaMonkey/2.8|
Hi,while porting an application from GNUstep to Cocoa, I noticed that while Cocoa rises an exception if you send nil with setStringValue to a textfield, GNUstep silently accepts it.
I think we should match Apple's behaviour which appears to be this since a long time  (note the commentof setStringValue vs. setObjectValue)
I couldn't find an explicit reference of this in NSCOntrol's documentation though.
|[Prev in Thread]||Current Thread||[Next in Thread]|