wouldn't it be as simple as adding an additional enum to the blend mode options?
Unfortunately, no.
Many features could be "as simple as adding a line of code". But a good library is not only a sequence of lines of code. It also has a design, a philosophy, a consistency.
When you ask me to add this simple line of code, I have to think about the relevance of the new feature, how it would integrate into the API, would it be simple to use, wouldn't it break anything, is it easy to understand by beginners, ... I have to consider everyone's point of view, not just yours or mine.
And this feature doesn't meet all the requirements:
- You're the first one to require this kind of effect, I've never heard about it before; and I can't add a new feature for one user
- It's not just a new blending mode, it is an effect that requires a special texture to work; setting it on a regular sprite would make no sense at all.
-> In short, I think it's too specific.
I don't see the reason to punish the user into using only pre-defined methods, especially if you want to produce fancier effects.
So far the only one to be punished is you
I know that this is frustrating from your point of view, but trust me, it's really hard to maintain a "simple and fast" library. I have to make choices to keep the API clean and usable for everyone, that include rejecting many requests. If you look at the "feature requests" forum you'll find many fights actually :lol:
But that's what makes SFML as good as it is now.
But what I don't understand is why you would remove the only solution I have ( in the scope of using your libraries ) to my problem and than tell me tough luck? Seems kind of a cold thing to do to someone whos been helping push the use of your library.
Hey, don't take it personally. I'm not cold with you, I'm just answering your request
I hope that you understand my point of view.