(2016-04-11, 07:27)Martijn Wrote: If you don't like it use something else.
You don't find it worth your time fixing something then devs shouldn't even been bothered fixing your edge case or whatever issue you have. Not worth the reading time.
If you are going to bitch towards developers who put in a shitload of their free time then I suggest you leave immediately.
Not worth my time because I'm not an active developer with working knowledge of the inner working of the program. I have other responsibilities and have better things to do with my free time. Even now, I'm wasting time that should be spent on other tasks by answering your condescending post.
My "edge case"? I would like to suggest that you use the search function for these forums, just so you could find out that I'm not all that unique on finding issues in Jarvis. I'm not unique on finding a font rendering issue (I linked the Android thread into this one). Should I point to the DX11 test thread which, as I recall, has another post by someone else stating there are other issues going on with Jarvis since the DX11 update? Is it "my job" to take developers by the hand and point out every thread they don't notice? Funny. Users are scorned for their failure to use the search function. I used it before making my own thread. No Windows thread had been created or showed up when I checked for "font render", so I provided more than what was requested of the Android "victims" (I provided a debug log, still image, and even a video).
Still, the very first team member in this thread is what you posted. No developer asked me to try a certain setting. No test version offered. Nothing was said by any team member until I pointed out that it wasn't required of me to fix what I didn't write. I was already considering the roll back to 15.2 when I started this thread. Thanks to "-p", I have both 15.2 and 16.1 RC2 currently installed. I'd like to see an RC3 with some UI fixes, at least one of which isn't unique to one platform. Because of your post, coupled with the comment from someone else stating the same thing, I suspect certain issues to go "as-is" into 17.0, even though at least one of them may be older than 15.x and is still around.
There is an old saying:
if you can't stand the heat, get out of the kitchen. If you can't take criticism of the project you work on, maybe
you should "leave immediately."
Just as an FYI, there was no need to use foul language.
