CS CLASS FUN
Apr. 7th, 1998 01:12 amThe cat is eating my cheese. I sliced it to go on these rank crackers. Damn slice of cheese with bites all out of it, all shiny with cat drool. Shoo!! Go lick your butt!
That is not what I want. What I want is a window that displays the blockset, and two squares surrounded by arrows to get specific in choosing a block. Windows can't do that in an actual window, it has to be a dialog box. Modeless, so we can do other stuff while it's open.
So I write code for two hours. I test it. Nothing happens. Wrong window handle? Wrong resource I.D.? I ferret out some tiny bugs. Compile and run. Nothing.
See, these bugs are the worst, because it doesn't crash. It's like they're not even bugs. I just wrote 700 lines of dead code, that's all.
Hey, the 'about' box is a dialog box, though it's not modeless. Maybe if I tested my box as a modal type, to see if it works. ... Nope.
Okay, I know what I'll do, I'll substitute the 'about' box resource script for the 'blockset' modeless one. So it'll call up my modeless dialog when I click on 'about'. Does it? ... Nope.
I think that means the problem is in the resource script.
Half an hour vanishes. Turns out the little arrows in the dialog box cause an error when the box is created. Windows 95 can't draw them because Borland's resource editor didn't set the #defines in my header file right. Sound annoying? It is. Took me about 40 minutes to figure out what that problem was. My life is that much shorter now.
So I run the program and poof, my modeless dialog box shows up. Except it's about 40% larger than it should be, and there's 'about' dialog text plastered all over it. And the arrows are missing.
I'm listening to "I love choco bars" over and over again until you shut it off. How it started dancing though, that was a little trick I never figured out. I was at Armands funeral. It was very small ... et cetera.
Oh my god is it that late already?!