Illnab1024 Posted October 19, 2009 Share Posted October 19, 2009 Sparked from this and a bit of boredom, I took my first dive into antialiasing. Here's the code, comments are few and far between so if you read this ask and I'll clarify. The algorithm sucks. Why? GDI+ renders the whole string at size*16 onto our surface and completely ignores boundary clipping until it actually goes to write the data, meaning in this case it would be much more resource-efficient (although a memory hog) to make one huge surface for it and sample from that. But this is designed around the assumption that I could find a rendering library that doesn't suck. Anything blatantly obvious to you, point it out. This is more a coding exercise than anything to me--the results aren't worth publishing as it doesn't implement font hinting whatsoever. (Mainly 'cause I can't access those details through GDI+ anyway.) HQFont.zip Quote ~~ Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.