Inconsistent param positions? about csfml HOT 5 CLOSED

That's the overload of sfMouse_setPosition that takes a RenderWindow. It is part of sfMouse, not sfRenderWindow.

from csfml.

The thing though is that the RenderWindow overloads are in RenderWindow.h, while the Window overloads are in Mouse.h. I would place the Window overloads in Window.h to make it look consistent.

Edit: and once you do that the parameter order switching becomes natural.

from csfml.

It belongs to sfMouse, so it has to be in Mouse.h.

The overload in RenderWindow.h is a hack, because C doesn't support polymorphism and sfRenderWindow doesn't belong to the module where the function is supposed to be defined. In the C++ version there's just one function, which is Mouse::setPosition(Vector2i, Window&) so there's no problem at all.

Things should be seen as "there's a function in sfMouse that takes a window", and the sfRenderWindow overload is just a kind of hidden extension that makes this function work for the sfRenderWindow type too.

from csfml.

Ok, in that case I'll mimic the C++ API instead of the C one. I'm trying to make the bindings as close as possible to the original code.

from csfml.

One should always mimic the C++ API, the C API has to use many ugly hacks because of its lack of object-oriented features.

from csfml.