Quote:
Originally posted by Adam Betts:
To me, they're meh. Majority of them use or have a similar look to Aqua.
your joking, right?
lasik eye fixerupping is pre…
By and large, windows themes just trash upon most of those for the Mac, IMO. There are some good ones, like Neos, jetblack, etc. but I mean, look at the rest, some really garish lo…
Quote:
Originally posted by SubGeniux:
It;s funny, but the Mac was always associated with designers, but half the themes look like they were done by someone pressing a …
Quote:
Originally posted by fireside:
thats only because there are less themes for Mac than there are for windows. when you compare the crappy themes for mac to the crap…
Quote:
Originally posted by SubGeniux:
Yeah, but at least there's a heck of a lot more good themes on Windows, as well as he options on how much one wants to tweak. True…
Quote:
Originally posted by quandarry:
your joking, right?
Yep, I'm joking. None of them have Aqua look
Quote:
Originally posted by quandarry:
lasik ey…
Quote:
Originally posted by templetalker:
I think that there is a lack of high end GUI themes for OS X because the "Major Designers" have objectives that don't steer tow…
Quote:
Originally posted by SubGenius or something:
By and large, windows themes just trash upon most of those for the Mac, IMO. There are some good ones, like Neos, jet…
Quote:
Originally posted by Holigen:
The limitations in OS X as far as themeing goes are enormous compared to those of Windows.
'nuff said
It's not a question of …
Quote:
Originally posted by SubGeniux:
It's not a question of what can, and can't be done; it's what is done that makes me wonder. The limitations of theming isn't an ex…
Yes Windows can be more easily themed...but I've tried Windowblinds and it sucks. Maybe it's Stardock's fault or maybe it's Microsoft's. All I know is the skins look cheap, for exa…
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…