SFML community forums
General => General discussions => Topic started by: Khnemu on October 24, 2012, 05:30:48 pm
-
Was it really necessary to change names in 2.0 so that i now have to check every function in my programs ?
I mean..."move" instead of "Move". How is that going to improve anything ?
I know sfml is a lot of work and all but still...sometimes you have to wonder why you make those changes.
-
This post was not really necessary, was it? ;)
Naming conventions were discussed months ago, please refer to the corresponding forum thread if you want to know why it was changed. I have nothing more to say than what's said there.
-
It was not necessary but it helps with the frustration :-\
Problem is it makes 1.6 and older code a pain to update.
-
I know... I'm really sorry.
But now, the good thing is that, starting from SFML 2.0, the API will remain backward compatible. This means that the API will no longer be broken by a minor version, your 2.0 code will still compile and run fine with SFML 2.9.
-
While i'm here is there a complete (and accurate) list of the changes ?
I'm trying to port an old animation system i did around 2 years ago and even after changing names and switching images to textures i'm having some weird behavior (especially with texturerects).
And sorry for the initial post, i was just frustrated a bit. ;)
-
While i'm here is there a complete (and accurate) list of the changes ?
There's a list of changes somewhere on this board, but it may not be complete / accurate. However it should contain most of the important changes, since almost nothing changed during the last months.
especially with texturerects
They are now defined with <width, height> instead of <right, bottom> ;)
And sorry for the initial post, i was just frustrated a bit.
No problem, this kind of reaction is expected and I was prepared for it when I did that modification ;D
-
Here it is:
http://en.sfml-dev.org/forums/index.php?topic=5343.0
-
especially with texturerects
They are now defined with <width, height> instead of <right, bottom> ;)
Aaaah this might be my problem...Thanks ;)
This is a sneaky one since it compiles just fine...
edit: yup, that was it.
Might want to put that in bold red in the changelog ^^
-
There's changelog near downloads, I don't know how accurate(from before case change):
http://www.sfml-dev.org/download/2.0-rc/changelog.txt