A user can be a script. Clearly, you just don't wanna agree man. :laugh: But hey... ice cream. Jeremy Falcon

Try the dish-of-the-day at Milliways for dinner.

Don't use the word "register". It doesn't apply in this case. Search for "BIOS and DOS interrupts" and you'll find what you're looking for. Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles. Dave Kreskowiak

The issue with fixed size is non-monospaced fonts requiring varying glyph sizes, and while I could use the "largest" size for each, rendering the transparency map to the screen requires alpha-blending - non-trivial. So the smaller the glyphs the better. I found in my tests that I had a memory leak. Haven't seen many of those in recent years, but here we are. I fixed that, sorted my cache problem, and wrote a screen full of text in about 17KB of cache, truetype. Heap frag wasn't as big an issue as I thought - the leak was. What I'm currently doing is I allocate a buffer for the first glyph. I render the glyph as an alpha transparency map, and then send that to the draw callback which puts in on the display. If the next glyph is bigger, I realloc() the buffer, and go for it again. None of this happens if I find it in the cache first. The callback never gets called, nor does the glyph copy memory get allocated (if everything is already cached) This takes a small amount of memory for the (uncached) rendering on a glyph per glyph basis and seems to work well. Caching improves the results significantly (a factor of 2 at least) when it doesn't have to expire, and moderately when it does. So I'm ready to move on to the next thing for now. Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix

GCC's warnings are often way too strict (and in some cases, outright wrong). What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???

It’s great that you’re considering the community and the existing work! Since your approach has distinct differences—like wrapping the algorithm in a GIF-rotate program and using two shears to maintain dimensions—there’s enough originality in your implementation to warrant sharing it. You could acknowledge the existing article in your work to show respect for the original author, while highlighting how your method differs. This way, you contribute to the conversation without stepping on toes. Sharing tips and tricks that build on existing knowledge is a valuable part of the community!

honey the codewitch wrote: they can't recursively decode UTF-8 without breaking the spec. I don't see how you arrive at that conclusion. honey the codewitch wrote: not .NET's place to satisfy your requirement I agree. honey the codewitch wrote: would break the spec In what way exactly? Particularly if the caller has control over whether or not it does. But you mentioned something about writing control characters in UTF-8 -- which include carriage-return, line-feed, form-feed, etc. -- so I don't understand what you meant that it would break UTF-8. Whatever situation you are trying to communicate, I am sure .net can do it already, and it doesn't "break UTF-8".

That's an interesting idea. I'll have to read up on the details.

:-O Guilty:~ TTFN - Kent

Fortunately in the latest revision that went away. What's still really ugly is that static template field initialization code. I hate that C++ makes you do it that way instead of putting the initializer inline. At least C++17 - maybe they've changed that since. Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix