On Mar 8, 2007, at 11:04 AM, Brian Stevens wrote: > Even if the app isn't hanging, hold down the option key during this > process and the quit menu option changes to force quit. I find this > useful when testing to prevent the app from writing data files at quit > time. oooh I didn't know that one, thanks! > FWIW: Most of us don't have or use a professional version management > system, so tracking code changes is a chore. One thing I do is make a > new copy of the folder each time I'm about to make a change. Also, I > make sure the folder(i.e. the project in it) I'm copying works > correctly in all functions. This makes it easier to figure out what is > different when my new code breaks and causes some calamity. It is > tempting not to use this discipline (or something like it that version > control would impose) and go in and make multiple changes in many code > files within a project. Sometimes that works but many times I have to > revert to my "method" to figure out where I blundered. I am such a "backyard programmer" I don't even really know what version control is. Does it track each and every code change so you revert them? I use the "copy my project folder before each significant change" method myself.