Go Back   MacRumors Forums > Apple Systems and Services > Programming > Mac Programming

 
 
Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
Old Dec 25, 2012, 05:14 PM   #1
BadWolf13
macrumors 6502
 
Join Date: Dec 2009
Binding an NSNumber to an NSTableColumn

Hi, not sure what I'm doing wrong, or if this just isn't supposed to be done, but I'm having issues binding the value of an NSTablecolumn to an NSNumber through an Array Controller. When the document loads, it displays the values in the table properly, but whenever I try to select a row in this table, it crashes with EXC_BAD_ACCESS.

Now I tried changing the Key Path in the bindings window of the table column to add ".doubleValue", whereby I can select the row without it crashing, but then it changes all the numbers on that row to 0.

Another table view in the same app has NSUInteger and double values, and that one works ok, it's just when there's an NSNumber involved that it crashes. Are we not supposed to use NSNumbers for binding table columns? It seems like Apple is encouraging us to stop using primitives, so I find that highly unlikely. Anyone got any thoughts?
BadWolf13 is offline   0 Reply With Quote

 
MacRumors Forums > Apple Systems and Services > Programming > Mac Programming

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Similar Threads
thread Thread Starter Forum Replies Last Post
Looking for OD only binding script / need help with binding to OD with DPS dabizkitman Mac OS X Server, Xserve, and Networking 5 Jan 9, 2014 11:29 AM
Need help with binding some keys in windows 7! Zeov Windows, Linux & Others on the Mac 0 Jul 6, 2013 05:29 PM
How to select NSNumber data with NSPredicate?? mikezang iPhone/iPad Programming 0 Oct 17, 2012 10:39 AM
AD Binding Issue dmoore70 MacBook Pro 4 Aug 28, 2012 04:53 PM

Forum Jump

All times are GMT -5. The time now is 10:58 AM.

Mac Rumors | Mac | iPhone | iPhone Game Reviews | iPhone Apps

Mobile Version | Fixed | Fluid | Fluid HD
Copyright 2002-2013, MacRumors.com, LLC