Is this really the only solution? Rejigger my whole program to use 2.1 instead?
No, you can simply link statically.
If 1.6 has such a major issue, that doesn't fill me with confidence in regards to SFML as a whole.
Although SFML 1.6 was not perfect, this was mostly a driver issue.
Thank you very much for your reply, Laurent! I've decided to switch over to 2.1. I really love your library, so I hope I didn't come across as too negative. Writing my goofy little game is full of enough headaches; I can't imagine how much work would be involved in creating something as massive as SFML. My hat is off to you.
In any case, 2.1 seems to be working nicely on my machine. Now I just need to reword some things in my program and I'll be happy as a clam.
... If 1.6 has such a major issue, that doesn't fill me with confidence in regards to SFML as a whole.
Your going to base your opinion of the current version of the library on an old outdated version that has since changed drastically?
Do you use this same mentality when playing games? And what about the games you are developing, do you want others to treat you the same way? "Vicker's first game kinda sucked, so I don't think I'm gonna touch this brand new one he put out. It may be a completely different thing, but that first one sure didn't fill me with confidence"
Actually speaking with some co-workers as I'm writing this, seems a lot more people then I previously thought think this way... too bad.
There's a difference between, "Vicker's first game sucked, so I won't touch his new one," and, "Vicker's first game sucked, so it makes me hesitant to try his new one." I also didn't say anything about forming any kind of opinion. I simply said it puts a dent in my opinion. My overall opinion of SFML is still overwhelmingly positive.