Le 7 déc. 2011 à 06:10, Ken Thomases a écrit :
> On Dec 6, 2011, at 10:05 PM, Don Quixote de la Mancha wrote:
>
>> Contrary to Ken Thomases' assertion, there are all kinds of reasons to
>> use atomic operations as locking primitives. One is that they cannot
>> result in process context switches
Hi guys,
this is my first email to the list. Currently I'm working on an app
that has to do with printing and I haven't really had any experience
with this. I get the basic concept that print and drawing to screen
are the same thing and all was working fine until I wanted to have a
striped backgro
On Dec 6, 2011, at 6:01 PM, Steve Sisak wrote:
> I realize that this is moot in the case of @autorelease, but in the context
> of "best practices" for code that can't depend on ARC
@autoreleasepool does not require ARC.
--
Greg Parker gpar...@apple.com Runtime Wrangler
__
On 7 Dec 2011, at 12:45 AM, Rajendran P wrote:
> My problem is that applicationWillTerminate is not being invoked when my
> launch agent is manually unloaded . My application is uielement with out
> dock entry . I am able to do a signal handling , low level unix signal
> handling like sigk
Hi,
I need to initiate a simple drag & drop operation for a single filename,
but it will not be called within NSView mouseDown, but shortly afterwards
(internal reasons). The mouse button will still be pressed, but the
mouseDown even will already be finished. How to do this?
Regards
Vojtech
_
Dear list,
A question regarding the proper use of dealloc in ARC-environments (under iOS):
I have a need to unregister NSNotification observers during exchange of
UiViewControllers. Is implementing - (void)dealloc considered a proper use for
this purpose? Is it safe to make assumptions regarding
Angry Birds does it so it must be possible. So how can I do this as well? I
need my app to truly take over the entire iPhone screen with no distractions
and no dangerous hit area that can take the user out of my app by accident.
Thanks
___
Cocoa-dev
My understanding is, due to auto release semantics, your object might be auto
released again during current pool draining. So it will be put into outer
Autorelease Pool, that's to say the dealloc are not guaranteed to be executed
at specific timing. ARC still relies on retain/release/autorelease
I have an NSTreeController whose 'content array' is bound to another object's
'content' key.
It appears that the binding mechanism duplicates the array that was returned by
[foo content].
This is bad, because changes that 'foo' makes later to its m_content never show
up in the window. It's
On Dec 7, 2011, at 20:05 , Eric Slosser wrote:
> I have an NSTreeController whose 'content array' is bound to another object's
> 'content' key.
>
> It appears that the binding mechanism duplicates the array that was returned
> by [foo content].
>
> This is bad, because changes that 'foo' mak
10 matches
Mail list logo
