References returning null values?

[FRex]

Shared pointers maybe. But there are simpler ways to deal with that. Manager classes put in well thought locations. See : http://en.sfml-dev.org/forums/index.php?topic=9437.msg64068#msg64068

the "getSprite" function seems completely useless and a waste of code

Yes!

[Flash619]

Shared pointers maybe. But there are simpler ways to deal with that. Manager classes put in well thought locations. See : http://en.sfml-dev.org/forums/index.php?topic=9437.msg64068#msg64068

the "getSprite" function seems completely useless and a waste of code

Yes!

Thanks for the link! It does seem a good idea to just include it in the main game state manager class, then I can just use that to sort of bounce off of to access it. Once I get a few new functions wrote for my window, I may try to take a look at that.

[Flash619]

Hey I was just wondering, whats your input on this?

int* EngineWindow::GetCenter()
{
        int *WindowCenter = new int[1]; //[0=X,1=Y]

        sf::Vector2u FullSize;

        FullSize = this->getSize();

        WindowCenter[0] = FullSize.x/2;
        WindowCenter[1] = FullSize.y/2;

        return WindowCenter;
}
 

I remember you saying not to use *new* but it does work with it, I just don't have a clue about how to delete it. It does work without error though. It returns a int Array.

[FRex]

Does it really? Should cause access violation or stack corruption. It's also (possibly) leaking memory. Why can't you just return sf::Vector? There is no reason not to return sf::Vector or if you really need array : std::vector(which is unleaky, self resizing array).

[Flash619]

Does it really? Should cause access violation or stack corruption. It's also (possibly) leaking memory. Why can't you just return sf::Vector? There is no reason not to return sf::Vector or if you really need array : std::vector(which is unleaky, self resizing array).

Yep it somehow works. XD

I'll just use a sf::vector. Should I just return a copy then since its returning data to an outside class and get rid of the pointers?

[FRex]

Yes! All functions that TAKE vector in SFML take const references or references and all functions that return vectors return a copy.

[Flash619]

TAKE vector in SFML take const references or references

Not sure what you are talking about there...

This is the code I came up with.... am I right?

sf::Vector2u& EngineWindow::GetCenter()
{
        sf::Vector2u WindowCenter;

        sf::Vector2u FullSize;

        FullSize = this->getSize();

        WindowCenter.x = FullSize.x/2;
        WindowCenter.y = FullSize.y/2;

        return WindowCenter;
}
 

[FRex]

Functions are declared like this:

void doShitWithVector(const sf::Vector2f& vector);
sf::Vector2f calculateShitVector();

not like this:

void doShitWithVector(sf::Vector2f vector);//waste of memory passingvector by value
sf::Vector2f& calculateShitVector();//cant return reference to temporary vector from inside fucntion scope

[Flash619]

Functions are declared like this:

void doShitWithVector(const sf::Vector2f& vector);
sf::Vector2f calculateShitVector();

not like this:

void doShitWithVector(sf::Vector2f vector);//waste of memory passingvector by value
sf::Vector2f& calculateShitVector();//cant return reference to temporary vector from inside fucntion scope

But I'm not accepting any vectors in my functions. In fact.... I'm not accepting any input to them. They only create and return a vector.......

[FRex]

Yes. So you return a copy. References are for things that are heavy to copy or for input values to functions.

[Flash619]

Yes. So you return a copy. References are for things that are heavy to copy or for input values to functions.

Oh that makes sense. I just often have difficulty figuring out whats considered a heavy copy. I suppose that would be things like.... sound objects, textures, stuff like that.

[FRex]

Textures, Images, SoundBuffers are Heavy. Sprites, Sounds, Vectors are Light.(this list is not complete..)
Everything is written in SFML documentation usually.