C++ Problem

[Mokka]

After I fixed my linker problems, I stumbled upon another error.

I wrote a code for a small game and I created like a request if-loop to read out the keyboard inputs (Up, Down, Left, Right), and now, to clean up my code I want to put the loop in a seperate function, or even a seperate header file/class.

But I am not able to succeed

First of all: here is my code:

(click to show/hide)

#include <SFML/Audio.hpp>
#include <SFML/Graphics.hpp>
int main()
{
// Create the main window
sf::RenderWindow window(sf::VideoMode(800, 600), "MTGame");
// Load a sprite to display
sf::Texture texture;
if (!texture.loadFromFile("./data/test.jpg"))
return EXIT_FAILURE;
sf::Sprite sprite(texture);

// Load a music to play
sf::Music music;
if (!music.openFromFile("./data/background.wav"))
return EXIT_FAILURE;
// Play the music
music.play();


// Start the game loop
while (window.isOpen())
{
// Process events
sf::Event event;
while (window.pollEvent(event))
{
// Close window -> exit
if (event.type == sf::Event::Closed)

window.close();
}
//Move-Loop
if (sf::Keyboard::isKeyPressed(sf::Keyboard::Left))
{
    sprite.move(-1, 0);
} else if (sf::Keyboard::isKeyPressed(sf::Keyboard::Right))
{
    sprite.move(1, 0);
} else if (sf::Keyboard::isKeyPressed(sf::Keyboard::Down))
{
    sprite.move(0, 1);
} else if (sf::Keyboard::isKeyPressed(sf::Keyboard::Up))
{
    sprite.move(0, -1);
}
//End-Loop

// Clear screen
window.clear();

// Draw the sprite
window.draw(sprite);

// Update the window
window.display();
}
return EXIT_SUCCESS;
}
 

The section //Move-Loop is the part I want to put in a seperate function.

So basically I just have to declare a function with a sf::Sprite as parameter which then represents the sprite that is supposed to get moved...

(click to show/hide)

. . .
void mover(sf::Sprite temp) {
       if (sf::Keyboard::isKeyPressed(sf::Keyboard::Left))
       {
           temp.move(-1, 0);
       } else if (sf::Keyboard::isKeyPressed(sf::Keyboard::Right))
       {
           temp.move(1, 0);
       } else if (sf::Keyboard::isKeyPressed(sf::Keyboard::Down))
       {
           temp.move(0, 1);
       } else if (sf::Keyboard::isKeyPressed(sf::Keyboard::Up))
       {
          temp.move(0, -1);
       }
 

But that does not work...
I am kinda new to C++ (as you can see ) but was pretty stable with coding until this point.

So could anyone please help me.
Best with a working solution with outsourced classes (in a header file).


Thank you for your help in advance...

(I don't know if this is the right place to post this stuff. If not please tell me where to put it and I will copy it there and delete this post)

[eXpl0it3r]

To properly work with SFML you need a good understanding of C++. Thus you should really get a good C++ book and work through it. C++ is not a language you can learn with the trial-and-error approach, because you end up wasting a lot of time, learn a lot of bad things and miss out on various important topics.

As for you problem: You're passing the sprite by value, thus all the changes happen to a local instance and not the original sprite. Use references instead.

[Mokka]

Thanks

[Red-XIII]

To be more specific, you should look into pointers. That should help you figure out your problem, and you can continue to experience software engineering with SFML.

[Rosme]

@Red-XIII: No. Just no. There is no need for pointers. References is the way to go. That was specific enough. Don't suggest pointers to a beginner. Don't talk about raw pointers. Talk about smart pointers instead. But again, no pointers here.

[Red-XIII]

No, references will not help with his problem, he needs to use pointers, otherwise hes just copying the value, and not accessing the direct value.

[Nexus]

No, references will not help with his problem, he needs to use pointers, otherwise hes just copying the value, and not accessing the direct value.

It seems like you should read up a bit on C++ too, as this is totally wrong

As an indirection mechanism, both pointers or references can be used, none of them leads to a copy. Which one you use depends on various semantical criteria (can it be nullptr, do I need to change it after initialization, do I need pointer arithmetics...).

[Red-XIII]

Oh I see, interesting, I thought pointers were the only way. My apologies.