Posted 26 May 2004 - 02:03
OK, just to add to my earlier Qbasic to C++ saga...
The one thing I miss the most about QBasic is, the graphics could be done:
screen 12
line(x1,y1)-(x2,y2),col
...just THAT easily! Instant raster graphics, and I used them so extansively that I even developed my own work-around for QB not using bitmaps...involving using an "etch-a-sketch"- type program I wrote which would save the pixels as numeric data in a text file, for later recall by other programs!
I really, REALLY miss raster graphics. The simple act of being able to turn the numeric data into pictures makes a programming language come alive for me, and it seems that this is the one thing that's going to be denied to me in C++...*sniff, whimper!* Though I have read ahead and compiled downloaded sample code enough to know that someday, I'll be able to do graphics in C++, too. From the looks of things, this appears to be the hardest thing to do in C++!
Yes, I know that old-style C has the "lineto" function, that's just the problem: old style, raster graphics seem to have become extinct in C (if I'm wrong about that, somebady, anybody tell me? Give a poor noob some hope?). Instead, I'm going to have to deal with graphics on a much more complex level with OpenGL or all that "device context class" stuff.
As <insert your favorite Diety> is my witness, if I do master C++ graphics, I'll write a function that translates all that complex stuff back into the simple "line" statement again, stuff it in a header file, and give it to the world!
Peace and Love and Granola,
Hosiah