Except iOS and Android ports, nothing is decided yet.
Are there specific plans for SFML 2.2?Yes, LaurentScript, it'll be AWESOME, it'll be garbage collected, dynamically strongly duck typed, imperative, iterative, nooberative, structural, functional scripting language for use with Irrlicht(finally bringing 3D into SFML!!), totally foolproof, with syntax mix of C#, Perl, COBOL and Brainfuck with most important sigil being euro sign, I can't wait! :D
Just a question : for minor versions you don't want any modification in the API right ? Or things can be added/altered ?Things can be added, but I want to keep API compatibility. In other words, a SFML 2.x code should compile and run with any older SFML 2 version.
On a more serious note: I'm glad it didn't take another few years like jump from 'official but unattended and obsolete'1.6 to 'stable, better, faster, easier but still RC' 2.0 did, why weren't there 1.7 through 1.9 thought? Did old rendering and transformation path got too cumbersome compared to light everything-as-array-of-vertices + states we have now and there has to be major version number up for something like that (and/or API) to change?Between 1.6 and 2.0, API compatibility was not preserved, so 2.0 was a new major version.
I'm very new to SFML(downloaded 2.0 yesterday and still working on getting everything setup correctly), but I noticed 2.1 doesn't come with a CMakeLists.txt file like 2.0 does. Can I just use the 2.0 CMakeLists.txt file in it's place or am I missing something entirely?Not sure what you were looking at. There are binary packages, where SFML was already built and thus doesn't include the source, which also means there isn't a CMakeLists.txt.
sf::Text just doesn't work unless you set the fontYes, this is the expected behaviour. There's no more default font (already in 2.0).
Quotesf::Text just doesn't work unless you set the fontYes, this is the expected behaviour. There's no more default font (already in 2.0).
I was able to use sf::Text without set a font in 2.0, lol, nvm.No, really, there's no default font in SFML 2.0 final (maybe you got an old revision).
What about the sf::Event::Closed issue? will be fixed soon?I just tested it, and I can confirm that there is a new bug. Damn... whenever you fix one bug, a new one pops up to replace it >:(
sf::RenderWindow doesn't gain focus unless you click the titlebar, clicking inside the sf::RenderWindow doesn't work :/Ok, this is also related to the first bug. So this is worse: you fix one bug, two new bugs appear.
I will just wait to 2.2 to download it since my ISP counts every mega byte being downloaded >:(That will take a while. SFML 2.1 was only released so fast, since it only contains bug fixes. SFML 2.2 will be in the works for a bit longer, since iOS and Android ports will take a bit more time to finalize.
Not after the Telecommunication ministry stops the monopoly in the name of capitalism.I will just wait to 2.2 to download it since my ISP counts every mega byte being downloaded >:(That will take a while. SFML 2.1 was only released so fast, since it only contains bug fixes. SFML 2.2 will be in the works for a bit longer, since iOS and Android ports will take a bit more time to finalize.
So if you ever get a better ISP, make sure to grab the bugfix update. ;)
SFML 2.2 will be in the works for a bit longer, since iOS and Android ports will take a bit more time to finalize.Any ideas when will be Android port? Halfyear, year or more?
How does for example SDL or Qt handle window input on Windows? Is there imperfect mouse left tracking as well?Can you please add a bit more context to your statement? Seems a bit taken out of no where and I'm not sure, if everyone can follow. :D
Maybe it's just bug in winapi and reverting to bug #225 is the only real solution.
Sadly, it seems there are some bugs in version 2.1 under OS X.You should rather open a new forum topic in the help section. This thread should not be about fixing the issue at hand. ;)
When I resize the window my code to keep the correct Aspect ratio seems to go crazy. It worked before in version 2.0 so I'm not sure my code is to blame. Also it seems to do nothing under Linux (SFML 2.1, Ubuntu).
I have attached a minimum example based on my main loop that reproduces the problem reliably.
Do you think it is possible to devise a work around until the issue is fixed?