Hi,
I want to customize the disclosure arrow appearance in my view-based
NSOutlineView.
I overrode the willDisplayOutlineCell delegate method, but it's not called.
The willDisplayCell delegate method - is not called either. Is it known issue
or I'm missing something?
(The isItemExpandable deleg
isItemExpandable and isGroupItem have nothing to do with NSCells. They're
called for the items.
Cell-based table and outlineView reuse the cells for each row; this was a
memory-saving technique 20 years ago, not so useful today. So before they drew
a particular cell it had to be configured for
Thanks for reply.
On Jun 21, 2012, at 11:05 AM, Lee Ann Rucker wrote:
> isItemExpandable and isGroupItem have nothing to do with NSCells. They're
> called for the items.
>
> Cell-based table and outlineView reuse the cells for each row; this was a
> memory-saving technique 20 years ago, not so
On 19.06.2012, at 02:55, Jens Alfke wrote:
> Fundamentally, you'll get errors from file operations that fail due to
> insufficient disk space. The errors depend on the API; e.g. for POSIX calls
> you'll see ENOSPC.
>
> However, running out of disk space is a pretty bad situation for the OS as a
On Jun 21, 2012, at 1:22 AM, Nava Carmon wrote:
>
>
>
> And this is what apple documentation says on this:
>
> outlineView:willDisplayOutlineCell:forTableColumn:item:
>Informs the delegate that an outline view is about to display a cell used
> to draw the expansion symbol.
_There are no
On Jun 20, 2012, at 11:32 PM, Michael de Haan wrote:
> Is the approach therefore to create the bindings to the databases, as well as
> the searchField in code ( as opposed to IB)?
You can do that. It's not hard to set and remove bindings in code.
Another possibility is to create your own clas
On Jun 21, 2012, at 7:45 AM, Kyle Sluder wrote:
> On Jun 21, 2012, at 1:22 AM, Nava Carmon wrote:
>
>>
>>
>>
>> And this is what apple documentation says on this:
>>
>> outlineView:willDisplayOutlineCell:forTableColumn:item:
>> Informs the delegate that an outline view is about to displa
Thank you all for answering.
Corbin, where is the best place to add my own disclosure button?
I believe not in the view itself, since it's indented.
Thanks
On Jun 21, 2012, at 7:25 PM, Corbin Dunn wrote:
>
> On Jun 21, 2012, at 7:45 AM, Kyle Sluder wrote:
>
>> On Jun 21, 2012, at 1:22 AM,
Hi all,
My preferences code strictly uses the CFPreferences api and has worked
reliably since Tiger. On Mountain Lion Preview 4 (with the recent
update), though, preferences writing has been erratic, sometimes my
preferences are updated correctly, sometimes not. Are there any known
issues
On Jun 21, 2012, at 11:17 AM, Michael Domino wrote:
> Hi all,
>
> My preferences code strictly uses the CFPreferences api and has worked
> reliably since Tiger. On Mountain Lion Preview 4 (with the recent update),
> though, preferences writing has been erratic, sometimes my preferences are
> u
On Jun 21, 2012, at 12:17 PM, Michael Domino wrote:
> My preferences code strictly uses the CFPreferences api and has worked
> reliably since Tiger. On Mountain Lion Preview 4 (with the recent update),
> though, preferences writing has been erratic, sometimes my preferences are
> updated correc
On Jun 21, 2012, at 11:33 AM, Scott Ribe wrote:
> On Jun 21, 2012, at 12:17 PM, Michael Domino wrote:
>
>> My preferences code strictly uses the CFPreferences api and has worked
>> reliably since Tiger. On Mountain Lion Preview 4 (with the recent update),
>> though, preferences writing has been
On Jun 21, 2012, at 12:39 PM, Kyle Sluder wrote:
> I guess the question is, why do you care whether the preferences have been
> written to disk? As long as everyone is using the correct API to access
> preferences, it doesn't matter whether CFPreferences is caching them in
> memory before flush
Ditto for me, my prefs are sometimes not getting to disk ever, so I can't rely
on seeing preferences set the way I left them. This only happens for me on
10.8, Lion does not exhibit this problem in my app.
-Original Message-
From: "Scott Ribe"
Sent: Thursday, June 21, 2012 2:44pm
To:
http://kalanikordus.com/wp-content/themes/modern-clix/images/ofnwp.html?kf=kfa.jxveza&hy=yl.eza&xhee=ynip
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators
Sharing preferences between applications is not something you can rely on in
a sandboxed environment. On 10.7, Preview and TextEdit are sandboxed so if
you're seeing this behavior with them, that's why. You can reasonably
expect more applications to be sandboxed in the future.
On 6/21/12 2:44 P
On Jun 21, 2012, at 1:20 PM, michael.dom...@identityfinder.com wrote:
>
> Ditto for me, my prefs are sometimes not getting to disk ever, so I can't
> rely on seeing preferences set the way I left them. This only happens for me
> on 10.8, Lion does not exhibit this problem in my app.
This topic
I'm not sandboxed, and the preferences I'm sharing are between my own apps.
Also it variously works then doesn't work for a while on the same machine, same
OS release, same app build.
On Jun 21, 2012, at 2:13 PM, Chad Hulbert wrote:
> Sharing preferences between applications is not something yo
18 matches
Mail list logo
