There is a workaround for this bug. See this answer to the same question on
Stack Overflow:
http://stackoverflow.com/questions/2616738/linking-to-libcrypto-for-leopard/2620698#2620698
I haven't tested whether this bug still exists in Lion or not, but if it does,
that workaround will likely
I'm adding some Core Animation to my existing project, and I'm encountering
some differences in the font rendering compared to non-Core Animation code.
Here's the code used to draw my strings:
NSShadow *selectedShadow = [[NSShadow alloc] init];
[selectedShadow
So I'm trying to weak link the SDL_mixer framework (svn source
avaliable here: http://svn.libsdl.org/trunk/SDL_mixer ) to a Cocoa
project, the Mac OS X port of Descent 2 (svn source available here: https://d2x-xl.svn.sourceforge.net/svnroot/d2x-xl
).
I've followed the instructions on
Il giorno Mar 11, 2009, alle ore 6:22 PM, Greg Parker ha scritto:
-weak_framework often doesn't work by itself. If the function
declaration isn't marked weak_import in the header file, then the
compiler may optimize out your `function != NULL` check and call the
weak-linked function
Rick --
I pulled my hair out over this one, but I finally found an acceptable
workaround, although it doesn't solve the fundamental problem of
NSDictionaryController.
What I ended up doing is setting the whole outer dictionary (the one
controlled by the NSDictionaryController) via a
I'm having a problem with NSDictionaryController. I created a class
named EPCustomClass that I want to use as the object class that
NSDictionaryController uses when returning objects from methods such
as -newObject or -arrangedObjects. So on wake from nib, I've sent -
