Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualServant of the Lord

Posted 15 August 2013 - 10:54 PM

That's still not enough code to solve your problem. I need to see the Sprite Manager class, and the part of the code (the entire function) where you create the Sprite Manager class, and the part of the code (the entire function) where you are using the Sprite Manager class to retrieve the the sprite and set it. I don't mind if it's too messy - I can read through the mess - but if you cut out pieces of your actual code before posting then it makes it harder for us to find the problem, and instead we have to guess what the problem is.
 
For example, I need to see the entire function that contains this line: (in addition to the entire Sprite Manager class).

sPaddle.setPosition(0, SCREENHEIGHT/2 - (PADDLEHEIGHT/2));

This forum's post editor has a button near the type that says 'code', and you can copy+paste your code into the box that it pops up. Just paste everything into it, even multiple files worth of text, and I'll sort it out and find the problem.

htk0.jpg

 

I have not taken and official programming language courses so my terminoligy is unsurprisingly poor, all my knowledge comes from free online help all over the web. Good to know though!

Same here! I'm entirely internet and book taught. I'm not trying to nitpick your terminology, just pointing out that if you are getting a 'not declared in that scope' message, than you can't truly be running/executing or debugging the code, because that's a compiler error not a runtime error - which is an important clue in solving the problem.

Terminology is something learned over time, piece by piece. Whether you say method or function doesn't bother me, because it's not related to the problem you are having. I get terminology wrong all the time. happy.png


#3Servant of the Lord

Posted 15 August 2013 - 10:54 PM

That's still not enough code to solve your problem. I need to see the Sprite Manager class, and the part of the code (the entire function) where you create the Sprite Manager class, and the part of the code (the entire function) where you are using the Sprite Manager class to retrieve the the sprite and set it. I don't mind if it's too messy - I can read through the mess - but if you cut out pieces of your actual code before posting then it makes it harder for us to find the problem, and instead we have to guess what the problem is.
 
For example, I need to see the entire function that contains this line: (in addition to the entire Sprite Manager class).

sPaddle.setPosition(0, SCREENHEIGHT/2 - (PADDLEHEIGHT/2));

This forum's post editor has a button near the type that says 'code', and you can copy+paste your code into the box that it pops up. Just paste everything into it, even multiple files worth of text, and I'll sort it out mentally and find the problem.

htk0.jpg

 

I have not taken and official programming language courses so my terminoligy is unsurprisingly poor, all my knowledge comes from free online help all over the web. Good to know though!

Same here! I'm entirely internet and book taught. I'm not trying to nitpick your terminology, just pointing out that if you are getting a 'not declared in that scope' message, than you can't truly be running/executing or debugging the code, because that's a compiler error not a runtime error - which is an important clue in solving the problem.

Terminology is something learned over time, piece by piece. Whether you say method or function doesn't bother me, because it's not related to the problem you are having. I get terminology wrong all the time. happy.png


#2Servant of the Lord

Posted 15 August 2013 - 10:52 PM

That's still not enough code to solve your problem. I need to see the Sprite Manager class, and the part of the code (the entire function) where you create the Sprite Manager class, and the part of the code (the entire function) where you are using the Sprite Manager class to retrieve the the sprite and set it. I don't mind if it's too messy - I can read through the mess - but if you cut out pieces of your actual code before posting then it makes it harder for us to find the problem, and instead we have to guess what the problem is.
 
For example, I need to see the entire function that contains this line: (in addition to the entire Sprite Manager class).

sPaddle.setPosition(0, SCREENHEIGHT/2 - (PADDLEHEIGHT/2));

I have not taken and official programming language courses so my terminoligy is unsurprisingly poor, all my knowledge comes from free online help all over the web. Good to know though!

Same here! I'm entirely internet and book taught. I'm not trying to nitpick your terminology, just pointing out that if you are getting a 'not declared in that scope' message, than you can't truly be running/executing or debugging the code, because that's a compiler error not a runtime error - which is an important clue in solving the problem.

Terminology is something learned over time, piece by piece. Whether you say method or function doesn't bother me, because it's not related to the problem you are having. I get terminology wrong all the time. happy.png


#1Servant of the Lord

Posted 15 August 2013 - 10:50 PM

That's still not enough code to solve your problem. I need to see the Sprite Manager class, and the part of the code (the entire function) where you create the Sprite Manager class, and the part of the code (the entire function) where you are using the Sprite Manager class to retrieve the the sprite and set it.
 
For example, I need to see the entire function that contains this line: (in addition to the entire Sprite Manager class).

sPaddle.setPosition(0, SCREENHEIGHT/2 - (PADDLEHEIGHT/2));

I have not taken and official programming language courses so my terminoligy is unsurprisingly poor, all my knowledge comes from free online help all over the web. Good to know though!

Same here! I'm entirely internet and book taught. I'm not trying to nitpick your terminology, just pointing out that if you are getting a 'not declared in that scope' message, than you can't truly be running/executing or debugging the code, because that's a compiler error not a runtime error - which is an important clue in solving the problem.

Terminology is something learned over time, piece by piece. Whether you say method or function doesn't bother me, because it's not related to the problem you are having. I get terminology wrong all the time. happy.png


PARTNERS