sf::Text::setTracking(int)

[SuperV1234]

It would be really helpful if we could specify a `tracking` int value in `sf::Text`.
All glyphs would be moved apart from each other by `tracking`.

[Hapax]

I think you mean kerning and SFML already allows you to get the kerning from a font.
You can't set it though, so if you want to display fonts more flexibly, you can make your own text class, unless someone has already made one. Try looking on the wiki.

EDIT: Maybe this could help.

[Laurent]

I don't think he means kerning, but rather a fixed additional spacing between letters. This would be trivial to implement. The question is: is it really useful?

[SuperV1234]

Laurent is correct. Tracking is not kerning and it is trivial to implement.

I find it useful because it looks really good when used properly.
A simple example would be a level introduction white screen with a black serif font and an high tracking value.
It just looks nicer.

Another idea that just came in my mind is using tracking to make text expand/shrink in animations.

[Laurent]

You're right, it can be used to create some nice effects.

Let's wait for more opinions before creating a task on the tracker (if nobody replies, don't hesitate to bump the thread in a few days).

[Hapax]

You're right; I had mixed up the two terms as they refer to very similar areas. Still, it could be implemented on top of SFML if required, but it would be useful for SFML to include things such as this 

[Laurent]

Still, it could be implemented on top of SFML if required

Hmm... with one sf::Text instance per letter?

[SuperV1234]

Still, it could be implemented on top of SFML if required

Hmm... with one sf::Text instance per letter?

Yeah, that's the issue, unless your reinvent 'sf::Text'.
I propose that the addition of a 'tracking' field would be good enough.

If you wanted SFML users to have more control, though, for the future version you should consider allowing users to pass a functor/lambda during text draw/update that is called on every single glyph, or something like that.

[Hapax]

I was under the impression that it could be achieved by accessing the glyphs directly, the way sf::Text would, which would end up being a single object. Is that not actually possible?

[Laurent]

If you wanted SFML users to have more control, though, for the future version you should consider allowing users to pass a functor/lambda during text draw/update that is called on every single glyph, or something like that.

Yes, we already have something in our todo-list that would allow more flexibility.

I was under the impression that it could be achieved by accessing the glyphs directly, the way sf::Text would, which would end up being a single object. Is that not actually possible?

So you have to rewrite sf::Text, which is not exactly trivial.

[Hapax]

you have to rewrite sf::Text, which is not exactly trivial.

It certainly is not but it's nice to know that it's exposed enough to access it if required 

...functor/lambda...on every single glyph...

Yes, we already have something in our todo-list that would allow more flexibility.

This is good to know. I wastn't suggesting we should be all "re-writing sf::Text"; I think it's much better for SFML to include this stuff. I said this already 

[Phanoo]

of course it's really useful. Why do you think all serious font libraries and languages (like CSS) or programs like GIMP or Photoshop does implement it?. same for a line-spacing function (line height). A pity that it's not already implemented. Same as text-formatting tags (italic, bold, underline, color...)

[FRex]

I'm very YES about this feature, it's nice, simple and very powerful and useful.

It certainly is not but it's nice to know that it's exposed enough to access it if required 

If it's urgent for you to use that kind of spread out text then it's really straightforward to implement it for yourself.
Just copy Text.hpp and Text.cpp, rename them and slap the modification notice (to comply with point 2. of zlib) and then modify the code (mainly ensureGeometryUpdate function) and there - done.
Or - if feeling adventurous - modify and rebuild SFML-Graphics directly.

[MarkusFL]

Yes, it's basic typography thing so I think it should be in.
The function could probably be named setLetterSpacing as in CSS (which makes it more familiar to people who have used that).

[Lo-X]

I think that could be useful but I don't think setTracking() is a good name. As proposed setLetterSpacing tells more about what it does (need to check what Qt uses).