The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
That's neat, but they're just retro font files. I guess maybe some of the formats they have are easier to use than TTF but id I went that route I'd be forced to use say, .fon files or whatever, and I'd really like the end user of my library to be able to choose their own fonts. So .ttf is pretty much what's for dinner.
I've got code to do the TTF rasterization now, I just need to modify it for my own nefarious purposes.
It will be nice to have the drawing primitives of GFX sewn up, and this is the last of it, unless i decide to add things like bilinear resampling and antialiasing.
Those are all pre-rasterized fonts. Yes, they are old but so what? For this purpose, that is exactly what I would use. This is for an Arduino right? Do you really want to pursue much beyond bitmap fonts? I certainly wouldn't. Anti-aliasing? Nope. I would not go beyond allowing the option for a transparent background or opaque. That is, for highest performance and that should be the highest priority in my opinion. If cosmetics are that high a priority then you are on the wrong platform as far as I am concerned.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
I was intending to render to a monochrome bitmap. I did manage to get it to render without anti-aliasing, and with single-bit-per-pixel position.
That was not the problem. I could render any monospace font regardless of whether or not it was BMP based. Because I was rendering the font, and saving the result of the render as a bitmap.
The only problem I ran into - THE ONLY problem, was positioning. .NET has no facility to accurately position fonts to a pixel perfect grid. That's the only problem.
And yes, cosmetics are an issue, because sometimes, I'm being called on to write professional looking software, and professional looking software shouldn't look like elephant crap, even on an embedded device. They aren't always an issue in all circumstances, but they are when it comes to larger font renderings.
If I need anti-aliasing i can bump from monochrome to grayscale and then treat the grayscale like an inverted alpha channel
The ESP32 can handle displaying a small rendering of Lucida Console (for example) or I wouldn't be doing this.
Yeah, I want to go the free tool route if possible, or otherwise whip this up quick and dirty. I just need to make a tool that's not standalone - it's just meant as a utility to generate font files my code needs.
We used it back in the day under Windows 3.1 to render TrueType fonts into bitmaps for use in our commercial ink-jet printers. There are other calls in that same area that give you character metrics and other useful information for your application.
I thought about that, but it doesn't seem like it, because the padding is consistent (in terms of physical proportions) as you increase the size. There seems to be some internal box layout (similar to CSS margins/padding) but I can't control it.
I could be wrong of course. Being on the outside looking in when it comes to the implementation of this there's always the possibility, but I'm more confident than not about this.
Shouldn't this be in the Bugs and Sugs forum?.....just kidding.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle