Operators for IntRect and FloatRect

[Deathbeam]

I am not sure if they are in official version, but in SFML.NET they are missing. Atleast operators == and != should be there. I can make pull request for it.

[Laurent]

They are in C++ version (it's easy to check...).

[Deathbeam]

It is not that easy, becouse I am totally unexperienced in C++ (and also lazy, easier for me is to ask). Okay, made pull request for that missing operators then: https://github.com/SFML/SFML.Net/pull/55

[ChronicRat]

How about shrink/expand methods? It can be useful.

[Laurent]

How about shrink/expand methods? It can be useful.

Useful for what?

[ChronicRat]

If you need increase or decrease size of rectangle, just for code beauty. =) For me - it is useful.

template<typename T>
inline void sf::Rect<T>::shrink(T val)
{
    left += val;
    top += val;
    width -= val;
    height -= val;
}
 

[Deathbeam]

If you need increase or decrease size of rectangle, just for code beauty. =) For me - it is useful.

template<typename T>
inline void sf::Rect<T>::shrink(T val)
{
    left += val;
    top += val;
    width -= val;
    height -= val;
}
 

Usefull? I know tons of usefull Vector and Rectangle functions but I still do not think that they should be implemented to SFML. Like

Union, Inflate, Center
 

for Rectangle and

Clamp, Dot, Direction, Distance, Catmull, Lerp, Hermite
 

etc... for Vector

[Hiura]

For so small functions like this one it's simpler to let everyone implement it on his own way because otherwise we need a lot of different shrink functions to make everybody happy: your function reduce the sides by 2*val toward the center, some people would prefer only 1*val, others might want to reduce it toward the top left corner, ... With all these functions you get a bloated API and everybody get confused. 

[ChronicRat]

Just offered. =) By the way, i'm using GLM as math lib.