|
vs2022 is irritating the heck out of me. Why is VSCode so liked - simplicity. VS2022 has so many dang options, features, etc it's ridiculous. The default installation should have 10% of what they are showing.
Under file: 19 options
Edit: 23
View: 33
etc.
Even help is out of control. I watched a few tutorials on Resharper and said no way...
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.
|
|
|
|
|
A neopixel is an RGB LED with a 1 wire daisy chainable interface. You can string many together into panels or single strands, or whatever.
Some of them however, have a strange color model. They have R, G, B, and W(hite) channels.
That caused me some grief because representing colors on these is a bit tricky.
Well, I finally, after looking at some python code someone dreamed up by hand fiddling came up with an RGBW "color model" in my graphics library.
The upshot is I can now for example, pretty faithfully represent a JPG or a GIF (the latter would be fun!) given a large enough panel.
Kinda proud of this. It's an elegant solution.
#include <gfx.hpp>
using namespace gfx;
...
auto bmp = create_bitmap<rgbw_pixel<32>>({64,64});
if(bmp.begin()) {
file_stream fs("./test.jpg");
draw::image(bmp,bmp.bounds(),&fs);
fs.close();
free(bmp.begin());
}
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Nice! We use a good number of the RGB type, and they are straight forward to use.
"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
|
|
|
|
|
Trying to get them to color match is tricky, even with straight RGB because the behavior is far different than an LCD screen.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
On that I agree, I normally do several passes before I get the color how I want.
"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
|
|
|
|
|
Fun indeed - we recently used some high density pixel addressable tape in our amateur theatre production of treasure island, where the parrot was named, not Captain Flint, but Alexa, and had a pulsating necklace which mimicked the effects of the earlier Alexa units when you spoke to the "parrot".
Alexa (there were two of them, depending on which side of the stage it was to come from) was a children's stuffed parrot toy, wearing a loop of pixel tape, connected to an Arduino nano IOT which was receiving artnet over WIFI from the lighting desk, all powered by a small USB power bank and the electronics stuffed inside the toy. This meant the toy could be carried around with no trailing cables, and the lighting desk could sent it commands to run patterns and effects on its "necklace".
The patterns were programmed into the Arduino rather than sending them directly from the desk so saving on channels in the desk. The necklace had enough pixels tightly packed that the two parrots together would have used up almost half a universe of addresses, whereas the technique used only required two addresses per parrot - intensity and pattern number.
|
|
|
|
|
|
This is my latest
Neopixel panel + htcw_gfx - YouTube[^]
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
The idea of an RGBW color model boggles my mind . I work in the printing industry so we use CMYK and RGB.
If we still had a color scientist (they were a thing for us at one time), I'd ask them about RGBW just to watch their brain asplode.
Software Zen: delete this;
|
|
|
|
|
I agree. It's maddening, and my library doesn't fully support it because conversions are not symmetric - IOW, translating to the RGBW model and back to something else again yields a different result than the initial value.
It supports it well enough though, but unfortunately you can't do like rgbw32_colors::antique_white without causing a compile error due to how the color system works.
You can however, either manually construct such a color, or convert it from another color model.
It makes no sense. Basically what I did is used someone's hand tuned algorithm for approximating the colors based on an initial Hue/Saturation/Lightness value. It works well enough, but it's not very quick as it actually involves things like cosine computations.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Translating between color models is always problematic... sometimes they don't even agree on what white is .
A fair amount of the time you can do conversions with precomputed tables. Of course I don't know how well that would work for you in your constrained IoT environment.
Software Zen: delete this;
|
|
|
|
|
Wordle 984 3/6
⬜⬜🟨⬜🟨
⬜🟨⬜🟨🟨
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 984 2/6
⬜🟨🟨🟨⬜
🟩🟩🟩🟩🟩
Such a word as this came in my very second attempt 😅
|
|
|
|
|
Wordle 984 4/6*
⬜⬜⬜⬜🟨
⬜🟩⬜⬜⬜
⬜🟩⬜🟨⬜
🟩🟩🟩🟩🟩
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Wordle 984 3/6*
⬜⬜🟨⬜🟨
🟩🟩🟨⬜⬜
🟩🟩🟩🟩🟩
Happiness will never come to those who fail to appreciate what they already have. -Anon
And those who were seen dancing were thought to be insane by those who could not hear the music. -Frederick Nietzsche
|
|
|
|
|
Wordle 984 5/6
⬜🟨⬜⬜🟨
⬜⬜⬜⬜⬜
🟨🟨⬜🟨⬜
⬜🟨🟨🟨🟨
🟩🟩🟩🟩🟩
|
|
|
|
|
⬜⬜⬜⬜🟨
⬜🟨⬜⬜⬜
🟩🟩🟩🟩🟩
good but lucky guess
In a closed society where everybody's guilty, the only crime is getting caught. In a world of thieves, the only final sin is stupidity. - Hunter S Thompson - RIP
|
|
|
|
|
Wordle 984 6/6
⬜⬜🟨⬜⬜
⬜⬜🟨⬜⬜
⬜🟨⬜⬜🟨
⬜🟨🟨⬜🟨
🟩⬜🟨⬜🟩
🟩🟩🟩🟩🟩
Phew, close one!
|
|
|
|
|
984 5/6
⬛⬛⬛🟨⬛
🟨⬛🟨⬛⬛
🟩🟨🟨⬛⬛
🟩🟩🟩⬛⬛
🟩🟩🟩🟩🟩
wordle.at
Rules for the FOSW ![ ^]
MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");
|
|
|
|
|
Wordle 984 5/6
⬛⬛⬛⬛⬛
⬛⬛⬛🟨⬛
⬛🟨🟨⬛🟨
⬛🟨🟨🟨🟨
🟩🟩🟩🟩🟩
Ok, I have had my coffee, so you can all come out now!
|
|
|
|
|
Wordle 984 5/6*
⬛⬛⬛⬛🟨
⬛⬛🟨⬛🟨
⬛🟨⬛🟨🟨
⬛🟩🟨🟩⬛
🟩🟩🟩🟩🟩
|
|
|
|
|
I've noticed a trend here on the site where authors/developers are still writing GUI applications in MFC (for C++) and/or WinForms. What's noticeably absent is WPF in either Framework or .NET Core.
So I pose the question (this is not snark, I genuinely want to know) why authors/developers are still choosing old(er) technology?
I used to think it was the learning curve, but I suspect there's more to this story.
Bonus Question: What's also noticeably absent is VB6 and VB.NET. Have those platforms truly bitten the dust (for good)?
modified 27-Feb-24 21:56pm.
|
|
|
|
|
Maybe because none of the new technologies really survive for more than a few years (months) and are replaced by the next hype?
[Edit]
It now seems to be extremely time-consuming to switch from one VS/C# V xyz to the next.
In other words, we are mainly busy migrating from a VS/c#/xyz version to the current version (with all the inconveniences that this entails) without achieving any real benefit for our applications.
[Edit 1]
Btw. forgot to mention, your question is a good question
modified 27-Feb-24 14:46pm.
|
|
|
|
|
There's no modern Windows UI toolkit for NATIVE C++ from Microsoft.
I think the last thing they introduced was the ribbon and it barely worked, (that was in 2008 ?))
They've abandonned us.
Previous job was on MFC and some Win32. (20+ years of development/history) and in a previous job, they switched to QT after I left.
Current job is on pure Win32. (30+ years of development/history). Switching to another toolkit like QT would be wildly prohibitive (time and money) and we'd loose a crap ton of features.
At home, if I want to quickly put up a mockup in C++ , I'll do it with MFC.
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
Another theory is (please note just one thought from an older man):
a.) The young programmers master all of these new tools. But they are not able to solve a practical task with it.
b.) This means that the older programmers who cannot/will not use the new tools have to solve the practical requirements with the tools they know.
If this thesis were to be true, it would be truly tragic
modified 27-Feb-24 15:05pm.
|
|
|
|