VB6: Graphics
-
Being young and foolish, I tried to make a game to keep my fingers busy. Me knowing nothing, I used a workable idea, ruined it with no campaign-ish structure and mistakes like that. The real problem was the graphics. Nothing fancy, the graphics consisted of (no fewer than) 700 Imageboxes on the form, layered for textures, objects, people, etc. Also, rather than hide them, they were filled with a blank transparent GIF if it was to display nothing. All but the textures were transparent GIFs, and all the images were loaded from the hard drive every time. Also, rather than update a few boxes, I had the whole thing re-calculated and re-drawn when the unit moved. I had added a counter Typical values to draw the screen (23x17 grid or so and each had 4 boxes) would be: 0.23 seconds. Per draw. And because the loop was so slow, it would take the best part of 5 seconds to move painfully and flickerously across the screen. Oh, and I nearly tried to write my own DirectX-style code. In VB6. I'd need a bloomin Double to store the framerate (for the minute value). Thank God I'm not paid to program...
Yet another spam post on yet another forum! I am the lazy one, who sleeps as it suits him, codes what he wishes, and has many years to look forward to. I love being a student.
-
Being young and foolish, I tried to make a game to keep my fingers busy. Me knowing nothing, I used a workable idea, ruined it with no campaign-ish structure and mistakes like that. The real problem was the graphics. Nothing fancy, the graphics consisted of (no fewer than) 700 Imageboxes on the form, layered for textures, objects, people, etc. Also, rather than hide them, they were filled with a blank transparent GIF if it was to display nothing. All but the textures were transparent GIFs, and all the images were loaded from the hard drive every time. Also, rather than update a few boxes, I had the whole thing re-calculated and re-drawn when the unit moved. I had added a counter Typical values to draw the screen (23x17 grid or so and each had 4 boxes) would be: 0.23 seconds. Per draw. And because the loop was so slow, it would take the best part of 5 seconds to move painfully and flickerously across the screen. Oh, and I nearly tried to write my own DirectX-style code. In VB6. I'd need a bloomin Double to store the framerate (for the minute value). Thank God I'm not paid to program...
Yet another spam post on yet another forum! I am the lazy one, who sleeps as it suits him, codes what he wishes, and has many years to look forward to. I love being a student.
Ouch. Are you the guy who wrote the copy folder algorithm for Vista?:laugh:
Deja View - the feeling that you've seen this post before.
-
Being young and foolish, I tried to make a game to keep my fingers busy. Me knowing nothing, I used a workable idea, ruined it with no campaign-ish structure and mistakes like that. The real problem was the graphics. Nothing fancy, the graphics consisted of (no fewer than) 700 Imageboxes on the form, layered for textures, objects, people, etc. Also, rather than hide them, they were filled with a blank transparent GIF if it was to display nothing. All but the textures were transparent GIFs, and all the images were loaded from the hard drive every time. Also, rather than update a few boxes, I had the whole thing re-calculated and re-drawn when the unit moved. I had added a counter Typical values to draw the screen (23x17 grid or so and each had 4 boxes) would be: 0.23 seconds. Per draw. And because the loop was so slow, it would take the best part of 5 seconds to move painfully and flickerously across the screen. Oh, and I nearly tried to write my own DirectX-style code. In VB6. I'd need a bloomin Double to store the framerate (for the minute value). Thank God I'm not paid to program...
Yet another spam post on yet another forum! I am the lazy one, who sleeps as it suits him, codes what he wishes, and has many years to look forward to. I love being a student.
-
Ninja-the-Nerd wrote:
VB6
I think Chris could as well redirect all Visual Basic posts to the coding horror forum ;P
Constantly "Saving the day" should be taken as a sign of organizational dysfunction rather than individual skill - Ryan Roberts[^]
And all VB articles to Purgatory, pending portation to C#? It's not that bad. It's simple enough for people like me to use it, and there's so many inefficient C based programs it's becoming hard to tell the difference :-P. I'll have another one soon, I'm porting and completing the VB6 version to VB .NET which should be a right laugh. At least I intend to use GDI for it this time, and use some optimised methods of dropping images. If any of my future employers see this...[crosses fingers] "Yes boss, I learned from my mistake" "No boss, I haven't learned C++"
Yet another spam post on yet another forum! I am the lazy one, who sleeps as it suits him, codes what he wishes, and has many years to look forward to. I love being a student.
-
Being young and foolish, I tried to make a game to keep my fingers busy. Me knowing nothing, I used a workable idea, ruined it with no campaign-ish structure and mistakes like that. The real problem was the graphics. Nothing fancy, the graphics consisted of (no fewer than) 700 Imageboxes on the form, layered for textures, objects, people, etc. Also, rather than hide them, they were filled with a blank transparent GIF if it was to display nothing. All but the textures were transparent GIFs, and all the images were loaded from the hard drive every time. Also, rather than update a few boxes, I had the whole thing re-calculated and re-drawn when the unit moved. I had added a counter Typical values to draw the screen (23x17 grid or so and each had 4 boxes) would be: 0.23 seconds. Per draw. And because the loop was so slow, it would take the best part of 5 seconds to move painfully and flickerously across the screen. Oh, and I nearly tried to write my own DirectX-style code. In VB6. I'd need a bloomin Double to store the framerate (for the minute value). Thank God I'm not paid to program...
Yet another spam post on yet another forum! I am the lazy one, who sleeps as it suits him, codes what he wishes, and has many years to look forward to. I love being a student.
-
Ninja-the-Nerd wrote:
VB6
I think Chris could as well redirect all Visual Basic posts to the coding horror forum ;P
Constantly "Saving the day" should be taken as a sign of organizational dysfunction rather than individual skill - Ryan Roberts[^]
C# ones, often, aren't that better. :-D -- modified at 10:18 Thursday 24th May, 2007
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
-
Being young and foolish, I tried to make a game to keep my fingers busy. Me knowing nothing, I used a workable idea, ruined it with no campaign-ish structure and mistakes like that. The real problem was the graphics. Nothing fancy, the graphics consisted of (no fewer than) 700 Imageboxes on the form, layered for textures, objects, people, etc. Also, rather than hide them, they were filled with a blank transparent GIF if it was to display nothing. All but the textures were transparent GIFs, and all the images were loaded from the hard drive every time. Also, rather than update a few boxes, I had the whole thing re-calculated and re-drawn when the unit moved. I had added a counter Typical values to draw the screen (23x17 grid or so and each had 4 boxes) would be: 0.23 seconds. Per draw. And because the loop was so slow, it would take the best part of 5 seconds to move painfully and flickerously across the screen. Oh, and I nearly tried to write my own DirectX-style code. In VB6. I'd need a bloomin Double to store the framerate (for the minute value). Thank God I'm not paid to program...
Yet another spam post on yet another forum! I am the lazy one, who sleeps as it suits him, codes what he wishes, and has many years to look forward to. I love being a student.
-
Being young and foolish, I tried to make a game to keep my fingers busy. Me knowing nothing, I used a workable idea, ruined it with no campaign-ish structure and mistakes like that. The real problem was the graphics. Nothing fancy, the graphics consisted of (no fewer than) 700 Imageboxes on the form, layered for textures, objects, people, etc. Also, rather than hide them, they were filled with a blank transparent GIF if it was to display nothing. All but the textures were transparent GIFs, and all the images were loaded from the hard drive every time. Also, rather than update a few boxes, I had the whole thing re-calculated and re-drawn when the unit moved. I had added a counter Typical values to draw the screen (23x17 grid or so and each had 4 boxes) would be: 0.23 seconds. Per draw. And because the loop was so slow, it would take the best part of 5 seconds to move painfully and flickerously across the screen. Oh, and I nearly tried to write my own DirectX-style code. In VB6. I'd need a bloomin Double to store the framerate (for the minute value). Thank God I'm not paid to program...
Yet another spam post on yet another forum! I am the lazy one, who sleeps as it suits him, codes what he wishes, and has many years to look forward to. I love being a student.
That is just the learning process. If we did not make mistakes then we would not learn anything or for that matter – get anything done. Programmers point of view: 1) Think. 2) Write something based on ideas. 3) Note possible problems – Think. 4) Rewrite – based on what you learned. 5) Think – are you satisfied (learned enough). 6) Make notes – consider improvements. Management point of view: 1) Think. 2) Write something based on ideas. 3) Does it work? 4) If yes! You are finished – because it works. 5) Stop thinking – for self preservation of sanity. 6) Recommendation – make personal notes – and go on to next subject. Note: If you do not inform management until step 4 in “Programmers point of view" is complete then you will have a better (more reliable) product. But if you must show progress based on the “Management point of view” then expect to be cut off at the knees, and learn to live with it.
INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra