Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In my situation,
glutInitWindowSize(w_walker*8, h_walker);
glutCreateWindow("walker");
loadTexture("./fighter512.png");
worked, but
loadTexture("./fighter512.png");
glutInitWindowSize(w_walker*8, h_walker);
glutCreateWindow("walker");
did not. Why?
Often, with some drivers/OpenGL implementations, the act of creating the window has the side effect of determining where the memory for textures, off-screen buffers and the window itself will actually live and consequently how big it will be too.
Without creating the window (or more precisely the rendering context) it’s hard (i.e. impossible) to determine where to put the texture once loaded.