I hate to be the bearer of bad news as I read that this was already solved, but well, I guess not quite. Release Candidate 4 crashes on startup for me. I read somewhere about holding shift when you load it up, which did the trick. So, holding shift works, without it, crash on startup.
I'm running vista home premium. Anything you need to know about my system? It's a laptop, core 2 due, 2gig ram, the graphics card is nvidia. If you need to know anything just ask.
Oh hooold on a second here! I have news lol. After loading it with shift and mucking around a bit in the program, I seem to be able to restart it without problems. Funny thing is it was consistent before. kept trying, kept crashing. Kept using shift, kept loading, and I kept closing it right after it loaded to try again. The problem was persistent and consistent, but the moment I gave up and started pressing buttons and leaving stackz open for a while... problem gone, startup doesn't crash anymore.
Are there any initial setup files stackz deals with? Maybe the problem occures with some kind of primary action? It really was consistent, and I had the exact same problem with one of the earlier betas. After the first time I actually played around with the program, the problem was solved. Strange eh? Might cause a prob for first time users though.
It's dependent on the menu actions you used the last time. Some (one!?) menu commands seem not to be registered correctly in the framework that does the folding/unfolding of menu items, so the app throws an exception on the next launch. Pressing Shift ignores loading the previous state, so thereafter you're safe again - until you use that menu action again. I thought I got them all by now, but it seems that there is one left - I just can't find out which one it is!
But a couple of days ago I did find out how to catch the exceptions correctly. In fact, the technique I was using got replaced silently by microsoft in the meantime, so my exception handler seems to have had had no effect at all... But now it will detect this incorrect initialization and no longer crash, but simply ignore the previous folding state and start in the default folding state.
Ah that makes sense! It stopped crashing because I disabled all the fancy menu options and opted for the basic simple menus. After that was when it loaded fine. But now I reactivated them to test and I tried a couple of different animations with menu shadows enabled and there was no problem. So, I really can't confirm anything, but so long as you know what you're doing then all's well. Still though, I couldn't open it without shift until I went around in the program and turned those menus off (I presume that was the action that fixed it, surely it's not a conincidence...?). Well, all's well now for me, just for new users I hope it's well too.
"as long as you know what you are doing"... hehehe well I think I do. Unfortunately, these things are next to impossible to test, so I can't tell absolutely sure. We'll see after the next release :)