Hog Obituary posted:

Ah, thanks, so [self retain] or strongPointer=self is accepted practice for these kinds of things? Because that actually seems considerably more reasonable, but still weird.

Well, B is a long-lived object and A is a short-lived object, and we're talking about A's internal cleanup, so I think it makes more sense for A to clean himself up when the task is done.

I'm actually okay with [self retain], I think I used to have some hangup about it because it feels like you're just creating a retain-loop and it'd be a recipe for memory leaks. I suppose you just need to be vigilant about releasing self.

Doc Block posted:

If memory serves, ARC is only supported on iOS 4.3 and up, not 4.2.


What is an "overlay" sprite? Also, make sure you're only changing this sprite's transparency, not the layer's.

Doc Block posted:

If memory serves, you're using a really old version of Cocos2D, right? Which means you probably started from the really old Cocos2D project template, right? Maybe the old template didn't have any of the multitasking methods in the app delegate.

Make sure you're pausing and unpausing the scheduler in the appropriate multitasking methods in your app delegate.

applicationWillResignActive: should call pause on the director (if the director in your old version of Cocos2D has such a method)

applicationDidBecomeActive: should call resume on the director

applicationDidEnterBackground: should call stopAnimation

applicationWillEnterForeground: should call startAnimation

applicationSignificantTimeChange: should call setNextDeltaTimeZero:YES on the director

Doc Block posted:

This is because RGBA8 means your OpenGL ES framebuffer is 32-bit RGBA, meaning it supports the framebuffer itself being transparent. You'll note that the RGB565 pixel format has no mention of an alpha channel, hence you cannot get a transparent framebuffer when the pixel format is RGB565.

Keep in mind that your app is rendering to an OpenGL ES framebuffer object, which the GPU then composites with whatever else it's supposed to display. If you have stuff in your view hierarchy that sits underneath your OpenGL ES view, and your OGL ES framebuffer has parts that are transparent, the stuff underneath will show through.

What effect are you trying to achieve? edit: nevermind, saw that you're trying to make the background transparent. What is supposed to be showing through?

LP0 ON FIRE posted:

I'm still having the transparency problem if anyone knows what could be up. I'm now suspecting it could have to do with setting CCTexture2D's DefaultAlphaPixelFormat like [CCTexture2D setDefaultAlphaPixelFormat:kCCTexture2DPixelFormat_RGBA8888]; ? Is it the wrong setting for Cocos2D having a transparent background? See my previous post for details.

Carthag posted:

I get an exception in my code:

code:

2012-05-12 16:32:13.787 otest[33892:403] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', 
reason: '*** -[__NSPlaceholderArray initWithObjects:count:]: attempt to insert nil object from objects[8]'
*** First throw call stack:
(
	0   CoreFoundation                      0x00007fff93f8afc6 __exceptionPreprocess + 198
	1   libobjc.A.dylib                     0x00007fff969b6d5e objc_exception_throw + 43
	2   CoreFoundation                      0x00007fff93f33ce1 -[__NSPlaceholderArray initWithObjects:count:] + 113
	3   CoreFoundation                      0x00007fff93f49281 +[NSArray arrayWithObjects:count:] + 49
	4   CoreFoundation                      0x00007fff93f48e50 -[NSDictionary allValues] + 400

So I check out the dictionary in the debugger, and it has a key/value pair of (null) = (null);?!?

code:

(NSMutableDictionary *) $4 = 0x00007fcc6e2f3760 {
    census = ...;
    childInFamily = ...;
    sourceCitation = ...;
    birth = ...;
    noteReference = ...;
    death = ...;
    spouseInFamily = ...;
    christening = ...;
    (null) = (null);
}

Now how the hell did I manage to put that in? As far as I know that shouldn't be possible? The docs say that it'll raise an exception (setObject:forKey:) or attempt to remove the key/value pair (setValue:forKey:) so it can't be those...

Carthag posted:

I wrapped both read & write access to the dictionary in @synchronized() blocks and that seemed to take care of it (I was accessing the dictionary in some concurrent array & set enumerations, so presumably that was the cause. The mutable containers aren't threadsafe). It's been refactored away now though.

Under ARC, too, so no garbage collection.

Ender.uNF posted:

Threads: The Great Heisenbug Simulator.

duck monster posted:

Concurrency is dark magic voodoo sometimes. Sounds like plain old memory corruption. Glad you solved it.

pokeyman posted:

GitHub for Mac uses Chameleon, so if you go the custom route, you can check out their implementation. I doubt it'll be worth outright lifting their classes but it might give you a head start.

If I was reimplementing it, I'd use an attached NSWindow. It's mostly boilerplate from there.

Doc Block posted:

RGBA8888 means you're getting 32-bit textures with full alpha transparency support. This is what you want if you are looking for textures that have smooth gradients and smooth alpha transparency instead of just on/off transparency. It takes up the most memory, though.

It could be a bug in Cocos2D, it could be a bug in iOS, or it could just be weirdness resulting from the combination of the specific blending modes Cocos2D is using, your framebuffer's pixel format, and having UIKit stuff underneath. Newer versions of Cocos2D get along better with UIKit.

Gordon Cole posted:

Martytoof posted:

Ah, fair enough.

I wonder if there is a way to deliver suggestions like this to Apple. It doesn't feel like something that ought to go into the Bug Reporter but I think that's actually exactly where it needs to be suggested.

xgalaxy posted:

I'm still fairly new at the whole thing but couldn't you manipulate the quartz layer size/position or will the popover container clip that?

the talent deficit posted:

I know Apps from the same developer can share certain permissions and capabilities, but if I create an AssetLibrary asset from one app, is it marked editable from another app (from the same developer)?

Martytoof posted:

I might throw the question up on StackOverflow. That place has been pretty good for some obscure questions.

ManicJason posted:

After assuring that my one strong reference was being set to nil, I went to the allocations instrument.