I only wrote this piece of code following one rule:
No jumping around. (That means no function calling at the minimum).
This rule enables me to learn about the orders of execution, and doesn’t put focus on programming design paradigms. Why did I focus on orders of execution? By programming with a very linear path down, I can be able to learn a bit more about OpenGL function executions and things like loading textures to the screen, and etc.
However, I have stumbled across a dead end: I can’t find the reason why my mesh isn’t showing up. And I’m exhausted (after a long session) from finding the error myself. I request for help; I need someone who can tell me what I did wrong and what I must do to change. Please be welcomed, thank you.
Below are the only 2 class objects I had created in my project. Because they are large, I used the pastebin to keep things small and nonintrusive. Why it’s huge? Codes don’t branch off to someplace else, so they are easy to read in a linear fashion. However, my “No jumping around” rule makes them very anesthetic after reading the code many times over. Hence my exhaustion.
Something class: It holds the mesh data and texture data.
http://pastebin.java-gaming.org/5303c53937b
Game class: It acts like a container for setting up the OpenGL context to a thread.
http://pastebin.java-gaming.org/303c3639b79