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 …

Or half-assed themes like some of these: http://www.resexcellence.com/themes/

I don't see what's so cool about this G-Pod. Pretty standard stuff.

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…

I think I like this one even better - it's like a modern version of NeXT! http://skins4.wincustomize.com/MikeB...thos-wb-ss.jpg

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…

Quote: Originally posted by Dace: <snipped> Couldn't agree more

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…

You could make the box part of the widget itself. Just make the inside sides of the boxes meet each other so they appear to connect.

Quote: Originally posted by TheDisaster: You could make the box part of the widget itself. Just make the inside sides of the boxes meet each other so they appear to conn…

:: Best way to do it is make the box part of the TitleBar Caps. :: Then, make the widgets with a transparent background :: and they will float on top of the box. :: Fluid

If you want to make the box around the widgets, change the metal windows bevel. The first one