SFML community forums
General => General discussions => Topic started by: Laurent on August 04, 2012, 12:10:31 am
-
Hi :)
I finally removed the default font and all its problems in SFML 2.
Its only use was for debugging and prototyping, any serious application loads a custom font anyway.
People that previously used it can just copy the arial.ttf file from their system font folder.
-
Quite a drastic change! This will probably break 80% of the 'applications' developed with SFML 2... ;D
Anyways I like the change (no crashes, problems, errors, etc., smaller library size and no copyright problem regarding Arial)! ;)
What does now happen if you try to run an application without loading a font?
Will you consider an implementation for system fonts?
-
Hi,
I have no idea what this changes since I am just getting started, but as of now it's impossible to compile (out of the box) SFML because of the redundant line 7 in https://github.com/SFML/SFML/blob/master/src/SFML/Graphics/CMakeLists.txt
Just a heads up.
-
Hi,
I have no idea what this changes since I am just getting started, but as of now it's impossible to compile (out of the box) SFML because of the redundant line 7 in https://github.com/SFML/SFML/blob/master/src/SFML/Graphics/CMakeLists.txt
Just a heads up.
Just delete that line yourself until it is updated.
-
Hi,
I have no idea what this changes since I am just getting started, but as of now it's impossible to compile (out of the box) SFML because of the redundant line 7 in https://github.com/SFML/SFML/blob/master/src/SFML/Graphics/CMakeLists.txt
Just a heads up.
Just delete that line yourself until it is updated.
What makes you think I didn't? I was just trying to point it out.
-
What makes you think I didn't? I was just trying to point it out.
I wrote what I wrote for those who are confused.
-
What does now happen if you try to run an application without loading a font?
I assume that you mean "what happens if you try to draw a sf::Text with no font" ;D
The same as a sprite with no texture: nothing shows.
Will you consider an implementation for system fonts?
Maybe in a far future :D
I have no idea what this changes since I am just getting started, but as of now it's impossible to compile (out of the box) SFML because of the redundant line 7 in https://github.com/SFML/SFML/blob/master/src/SFML/Graphics/CMakeLists.txt
Oh, thanks! That's what happens for working after midnight...
-
What makes you think I didn't? I was just trying to point it out.
I wrote what I wrote for those who are confused.
Oh I misinterpreted you. My apologies.
-
You added this in getFont(): “If the text has no font attached, a NULL pointer is returned”.
As far as I can tell, it's impossible to create a text with no font. When does this case apply?
Edit: maybe it would be nice to be able to specify the default font, so you don't have to pass your font every time you create some text.
Edit 2: I'm stupid, I didn't notice the no-parameters constructor.
Edit 3: if it's still possible to create a Text object with no font by calling the no-parameters constructors, why isn't it possible anymore to create one with a string but no font?
-
if it's still possible to create a Text object with no font by calling the no-parameters constructors, why isn't it possible anymore to create one with a string but no font?
Why would such a constructor be needed?
-
if it's still possible to create a Text object with no font by calling the no-parameters constructors, why isn't it possible anymore to create one with a string but no font?
Why would such a constructor be needed?
For consistency. And because it may make sense to delay the font assignment. For example, you create your text objects, add them to a list, then some function or class that manages the fonts assigns the fonts to the texts based on the configuration or the OS.
-
For consistency. And because it may make sense to delay the font assignment. For example, you create your text objects, add them to a list, then some function or class that manages the fonts assigns the fonts to the texts based on the configuration or the OS.
So basically you'd iterate through the texts twice which is bad design and shouldn't be used.
I think it's okay to force people to use a font at creation, because text can't exist without a font and if you just want to pass around strings, then use std::string (or sf::String). ;)
-
What's wrong with using the setString function? In fact the set of available constructors is not that important.
-
I finally removed the default font and all its problems in SFML 2.
Great! ... No more local temp sf::Text objects in my draw methods! .. No more ATI bugs.. 8) 8) 8)
-
Awesome! That means no more font bugs on my old windows :D
-
Please update the documentation to reflect this. It confused me for a few minutes.
-
Please update the documentation to reflect this. It confused me for a few minutes.
Unfortunately the documentation is frozen to the SFML 2 RC release, not sure if Laurent wants to update it or create a second section for SFML 2 (current)...
-
The online documentation matches the latest online release. If you compile SFML yourself, then compile the documentation too.