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!

I ended up going with is_color_model<> which makes perfect sense in my library's vernacular where a color model is a composition of color channels with particular names. Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix

The make -> cmake transition marks (at least in my mind) the 'bare metal' to 'higher level, more complex stuff' and I don't like it. "In testa che avete, Signor di Ceprano?" -- Rigoletto

It depends on what they are pointing to …(?) I had just switched companies. I was about a year and a half out of school with pretty solid C skills. A senior programmer at the new company who was new to C asked me to review a C module he was implementing. All of the code looked pretty solid. The module used a fairly large struct for tracking its data. Every method in the module accepted a pointer to the struct type or else used a global pointer (too long ago). After reviewing the code, I asked him “Where is the memory allocated to actually hold the struct data?”. Huh? We added a global variable declaration of his struct type and initialized the global pointer with its address and everything worked fine. My tenets when dealing with pointers: 1. When declaring the pointer, the * is part of the type. int* justAPlainOldVariableOfTypeIntPointer; int** justAPlainOldVariableOfTypeIntPointerPointer; 2. A pointer is a leash 3. A pointer is NOT the dog!(or cat but who leashes their cat, it is undignified) 4. When writing or reading code with the dereference operator *, say “dereference “ out loud. 4a. Understand the difference between * as declaration, * as dereference unary operator and * as multiple binary operator or do not try to use them! 5. Same for addressOf & operator. (as well as assignment operator, comparison operator, etc) 6. The compiler enforces type safety. Let it do its job! Unless you are dealing directly with hardware or doing low level memory tricks, you should not need to recast something.

etechX2 wrote: Maybe the AfxRegisterWndClass is set to release class automatically at the end when library exits. ? 1. Please read the Microsoft documentation about AfxRegisterWndClass; 2. Why are you trying to unregister and then reregister already registered Class? just save its name and then use it again!

retirement... for at least 3 months, we'll see how it goes. Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.

If I wasn't working on a system with a very primitive scheduler and a miserly amount of RAM I would have seriously considered it. It *did* cross my mind. But in the end I got it to work without doing so, and it was actually a bit easier than the documentation seemed to suggest. Helped that I found example code. Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix

Try std::multimap. It does exactly what you want. Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.

honey the codewitch wrote: hardware mapping of a C++ based device controller. Sounds good. But I don't want some mid-level developer that just discovered templates and databases to decide that he/she is going to improve the world by creating templates that encapsulate everything in the database layer.

OK

Kent Sharkey wrote: For building, all that is required to build DuckDB is a working C++11 compiler." Aye, I think I would have problems setting up a working C++11 compiler. :laugh: Latest Articles: A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity Framework

MarkTJohnson wrote: how long were you "puckered"? I would have been puckered if I had truly needed those backups. As it was, I went through a few emotions: 0: Surprise! Your false sense of security has just been shattered...You are not as clever as you thought you were, and your backups are shite! :omg: 1: Doubt...Hmmm what about the other 20 daily backups? Are they all shite? :confused: 2: Relief...Whew! The other backups are fine. Just these two from this server are crap. 3: Annoyance. I just want to get on with work. Now I have to log on Azure, allow myself to RDP into that box, get raw unzipped backups, and start troubleshooting the problem. 4: Sleuth Mode...the problem seems to be with the zip lib...maybe a bug...maybe fixed? Go get the latest version to find that it's being deprecated, and the last version is 6 y/o. Whatever, I'll try it. 5: Disappointment. :sigh: Nope that didn't work, time to open the project and debug with one of the dbs having the issues. 6: Excitement. :-D Yay! I was able to replicate the issue...now on to understanding. 7: Discovery: A well-phrased search put me on the right track...a known issue with an easy fix. 8: Humility: I'm sure I would have discovered this eventually, but I put a lot of faith in an automated process without actually verifying the outputs, which was the only way to detect the problem. Lesson learned! :laugh: "Go forth into the source" - Neal Morse "Hope is contagious"

One little, two little, three little Indians, Six little, five little, four little endians...

ya everyone says they know everything... Caveat Emptor. "Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long

Thank you for your constructive contribution to this discussion. Appreciate your input and now I have a better understanding of the process.

Thanks for my morning smile :)