I thought apps were limited to 600 or 650 MB by iOS, regardless of how much
memory was actually available. But I just noticed our little debugging memory
display showing some 850 MB available. I don't remember if it showed that much
prior to iOS 7.1.
So, has iOS 7.1 increased that limit?
--
R
On Apr 2, 2014, at 4:34 PM, Roland King wrote:
> That sent me into the documentation to find that indeed there *is* a selected
> object property on NSArrayController, but it's a *property* not a binding.
Note that the selection property value is a proxy which can represent a single
object, mul
On Apr 2, 2014, at 7:34 PM, Roland King wrote:
>
> On 3 Apr, 2014, at 12:22 am, Seth Willits wrote:
>
>> On Apr 2, 2014, at 6:54 AM, Roland King wrote:
>>
>>> At this point I realized the NSArrayController was doing nothing. ... I
>>> took it out and bound direct to the equivalent properties
On 3 Apr, 2014, at 12:22 am, Seth Willits wrote:
> On Apr 2, 2014, at 6:54 AM, Roland King wrote:
>
>> At this point I realized the NSArrayController was doing nothing. ... I took
>> it out and bound direct to the equivalent properties on the model
>
> It's not doing nothing.
>
> The NS
Some good answers have already been posted. Just one more general comment.
Ideally, an API is designed based on the API contract. However, Cocoa Bindings
are deep and complex, and its API has been difficult to describe in words.
Compared to other OS X technologies, Cocoa Bindings may therefor
On Apr 2, 2014, at 6:54 AM, Roland King wrote:
> At this point I realized the NSArrayController was doing nothing. ... I took
> it out and bound direct to the equivalent properties on the model
It's not doing nothing.
The NSArrayController doesn't simply "forward" objects from the model to
On Apr 2, 2014, at 7:54 AM, Roland King wrote:
> I have an array property in my model which is a list of serial devices, I
> want to display it in a table view and let the user select one. So I
> instantiated a tableView, an NSArrayController, bound the contents of the
> NSArraycontroller to th
I'm not great with bindings, but I'm trying to learn.
I have an array property in my model which is a list of serial devices, I want
to display it in a table view and let the user select one. So I instantiated a
tableView, an NSArrayController, bound the contents of the NSArraycontroller to
th
Thanks to all for your responses. A scene got presented and removed later on.
The app delegate had a currentScene property, and after I had activated all
debug features I saw that my scene class was being sent some message it didn't
respond to, but in fact was actually not even supposed to do so
On 01 Apr 2014, at 23:19, Alexander Reichstadt wrote:
> Is there a way to find the root cause of such a crash?
Vague idea: Set breakpoints on anything that can terminate an application (e.g.
exit() and abort()) and if one is triggered, see if the stack backtrace gives
any hints on what might be
10 matches
Mail list logo
