Quote:
Originally posted by k.mo:
Binary's looks way too much like XP/Classic for my taste, and the port from Jag (by Susumu) is fugly (fugly fonts)
Watercolor is…
Quote:
Originally posted by kmkkid:
Watercolor is meant to be classic feeling, it is a windows theme remember .
Chris
But...mac emualtion...Aqua-Soft...doh!...
Quote:
Originally posted by kmkkid:
Watercolor is meant to be classic feeling, it is a windows theme remember . I actually disliked what carbon did to it, but to each th…
Quote:
Originally posted by kmkkid:
...I actually disliked what carbon did to it, but to each their own...
Quote:
Originally posted by NetworkShadow:
..…
Quote:
Originally posted by CarbonG4:
What I did to it? It's a pretty straight forward port... maybe you are referring to the Brushed Metal teaser up on my site, I'm no…
Quote:
Originally posted by CarbonG4:
I will be maintaining both a Classic version of the theme and a Remix version. The Classic version will be the one closest to the …
Hey everyone. I'm having rather odd issues with the NSAutoRelease pool. My program is crashing when the NSAutoRelease pool releases an NSString that I have neither retained nor r…
My guess is that NSString's -substringWithRange: returns an autoreleased NSString, so if you autorelease that, it's on the autorelease pool twice, and thus gets sent -release twice…
Quote:
Originally posted by oVeRmInD911:
My guess is that NSString's -substringWithRange: returns an autoreleased NSString, so if you autorelease that, it's on the autor…
Quote:
Originally posted by Detrius:
Is it possible that I am releasing an object elsewhere that is already on the autorelease pool, and then this object just inadverte…
Don't autorelease the object. Whenever you get an object without using an alloc] init... statmeent, it's assuemd the the object has already been autoreleased.
Matt Fahrenbacher
The thing that is absolutely bizarre is that according to Apple's ObjectAlloc utility, the NSString object has been neither retained nor released, yet it is crashing in the autorel…
Quote:
Originally posted by Detrius:
If I autorelease the object returned from this function, the program crashes at the the NSString object. If I do not autorelease th…
wait, now that I actually read the part I quoted I'm less sure I ever knew what you were talking about. Did you mean you were autoreleasing the NSString you were talking about, or…
Quote:
Originally posted by Uncle Skeleton:
wait, now that I actually read the part I quoted I'm less sure I ever knew what you were talking about. Did you mean you wer…
First thing, you shouldn't start your classes with lower case letters - it's bad style
laExpression => LAExpression
Second, I'm betting then something really weird is happeni…
Quote:
Originally posted by Detrius:
I realized that I hadn't been following proper procedure, so I went back through all of my code and changed it as seemed appropriate…
Quote:
Originally posted by Uncle Skeleton:
my first instinct is to say you probably had a release on one of those once and now it's being auto-released and the stray re…
New information:
Elsewhere in this laExpression class, I have been using the NSNotification center to pass messages to whomever needs to know when the object has changed. On a wh…
Maybe you should take a look at the stuff in NSDebug.h and search Apple's developer site for MallocDebug. These are both helpful in tracking down these types of issues.
Some closure here... apparently, ObjectAlloc isn't a program you can rely on to give you details about why your program crashed. The thing that I finally had to do is print out a…
Hi guys,
I need to find a certain image, I have a feeling its in Extras.rsrc but I'm not sure. You know when you drag an app into your dock, then delete the app that corresponds t…
Quote:
Originally posted by iOliverC:
Hi guys,
I need to find a certain image, I have a feeling its in Extras.rsrc but I'm not sure. You know when you drag an app into …