Duhh! I have created dictionaries already—there’s a sample one for
testing in my app already—but the syntax of that prototype went right over my
head. I’m accustomed to JSON and Python’s use of braces to declare
dictionaries, and I was so fully convinced the variable was an array that I
OS X app has an NSOutlineView with a data source. Clicking on a disclosure
triangle to expand an item that has 13,000 children causes its data source to
immediately receive -outlineView:child:ofItem: 13,000 times, on the main
thread. The app presents a beachball until it’s over, which is unacc
On Mon, Sep 15, 2014, at 01:52 PM, Jerry Krinock wrote:
>
> It would be nice! Is that correct? If so, how might my outline view be
> abnormal? My data source is backed by Core Data, but I don’t think that
> matters to this issue. Below is a call stack of how my data source gets
> a typical one
On 2014 Sep 15, at 11:56, Kyle Sluder wrote:
> Are you using a view-based outline view?
No. It is cell-based. App currently runs in Mac OS X 10.6.
> Does your outline view have constant row heights, or are you
> implementing -tableView:heightOfRow:?
Constant row heights. I am not implement
On Sep 15, 2014, at 12:31 PM, Jerry Krinock wrote:
>
>
>> On 2014 Sep 15, at 11:56, Kyle Sluder wrote:
>>
>> Are you using a view-based outline view?
>
> No. It is cell-based. App currently runs in Mac OS X 10.6.
Can’t very well keep “only the onscreen views” if the table isn’t view-based
On 2014 Sep 15, at 12:35, Kyle Sluder wrote:
> Can’t very well keep “only the onscreen views” if the table isn’t view-based…
Makes sense! Are you implying that lazy loading is a side benefit of
view-based tables, and hence that this performance bottleneck is a legacy that
I could fix by drop
On Sep 15, 2014, at 1:52 PM, Jerry Krinock wrote:
> OS X app has an NSOutlineView with a data source. Clicking on a disclosure
> triangle to expand an item that has 13,000 children causes its data source to
> immediately receive -outlineView:child:ofItem: 13,000 times, on the main
> thread.
On Sep 15, 2014, at 2:46 PM, Jerry Krinock wrote:
> On 2014 Sep 15, at 12:35, Kyle Sluder wrote:
>
>> Can’t very well keep “only the onscreen views” if the table isn’t view-based…
>
> Makes sense! Are you implying that lazy loading is a side benefit of
> view-based tables, and hence that thi
I have a binding that throws an Objective-C exception but the console displays
no output and the application does not crash but rather the application runs
fine. Enabling NSBindingDebugLogLevel 1 does not help, the console still
displays nothing. I am using Xcode 5.1.1 with the All Exceptions br
On Sep 15, 2014, at 2:42 PM, Richard Charles wrote:
> I have a binding that throws an Objective-C exception but the console
> displays no output and the application does not crash but rather the
> application runs fine. Enabling NSBindingDebugLogLevel 1 does not help, the
> console still disp
On 15 Sep 2014, at 21:42, Richard Charles wrote:
> I have a binding that throws an Objective-C exception but the console
> displays no output and the application does not crash but rather the
> application runs fine. Enabling NSBindingDebugLogLevel 1 does not help, the
> console still display
On 2014 Sep 15, at 12:47, Ken Thomases wrote:
> Check the places where you can control how the outline view sizes the columns.
It seems that I only set column widths during -awakeFromNib. Definitely not
upon expanding an item.
> In particular, from the docs for -[NSOutlineViewDelegate
> out
On Sep 15, 2014, at 2:52 PM, Keary Suska wrote:
> Yes, The exception will leave your app in an invalid state.
Thank you, I was not aware of that.
> The breakpoint catches before the exception would be logged to console.
> Simply keep clicking the "continue" button in the debugger until it outp
On Sep 15, 2014, at 3:54 PM, Jerry Krinock wrote:
> On 2014 Sep 15, at 12:47, Ken Thomases wrote:
>
>> In particular, from the docs for -[NSOutlineViewDelegate
>> outlineView:sizeToFitWidthOfColumn:]:
>>
>> "By default, NSOutlineView iterates every row in the table, accesses a cell
>> via pr
I am using a NIB template, loading the same nib repetitively with a different
owner each time (a non NSViewController subclass).
In the nib there is an NSValueBinding binding to the owner say: self.itemValue.
This all works fine.
However, nib owner items are not being dealloc’d.
This behaviour on
On Sep 15, 2014, at 5:00 PM, Jonathan Mitchell wrote:
> I am using a NIB template, loading the same nib repetitively with a different
> owner each time (a non NSViewController subclass).
> In the nib there is an NSValueBinding binding to the owner say:
> self.itemValue.
> This all works fine.
>
My app’s document consists of a tree of individual word processing files to be
saved as separate files within an NSFileWrapper.
Apple’s documentation suggests you can make the process of saving to a file
wrapper more efficient if you only write out new or changed files. I’d like to
do that and
On Sep 15, 2014, at 19:12 , Charles Jenkins wrote:
>// What the heck do I do here? How to I update fw's contents?
You do the “obvious” thing — remove the existing file wrapper and create a new
one.
The clearest logic for this would be:
If this file’s content is modified, remov
Well, I made a little demo project containing an NSOutlineView, cell-based with
two text cell/columns, connected data source to app delegate, and in there
implemented data source methods to supply 1000 items to the root.
Result: Behaves lazily as desired. Initially, it asks for about 100 more i
19 matches
Mail list logo
