Do you happen to have links to any good documentation/articles on this topic? I'm working on what amounts to a dark theme for Win32 controls and largely making it up as I go along, relying on tidbits and off-hand mentions from defunct blogs.
I have a reasonably complete implementation of dark mode in my open source application, Explorer++. It uses the standard Win32 controls and applies a variety of strategies to get something that looks more-or-less cohesive when dark mode is enabled. ThemeManager.cpp[0] contains the bulk of the functionality. It could be useful as a reference for how you might create a dark version of a standard Win32 control.
Afraid not, had to piece together a lot of it myself. There are lots of examples available for various components of varying quality -- you'll find some code examples that don't work well with high DPI or all of the sub-modes of a control.
Some controls like buttons, list boxes, list views are reasonably well behaved, especially when theming is turned off. Combo boxes and toolbars are more temperamental. Check boxes, scroll bars, menus, and message boxes require a lot of custom painting work.
My experience also. This is particularly bad in the SQL Server space, since Microsoft essentially dropped source control integration in SQL Server Management Studio 2016 and later (there's an official workaround[0], but it's not well received).
Most likely they're happy to offload version control to add-ins. There are a few, but most of them are way out of budget for small businesses or small IT departments. Which means version control usually doesn't happen.
This has been such a problem for me with clients that I started a side project[1] to try to help fill the gap. If anything it's shown me that the problem is more widespread than I originally thought.
In the past, I used the SQL project feature of Visual Studio to great success to manage the DB. Everything except data up/down migrations was well supported, and it enabled us to keep our SQL in source control. I never even knew there was direct integration with SQL server.
That's good to hear. When I started that job, the DB upgrade was a massive, manually curated SQL file that would be run for every upgrade and contained every change from the beginning of time. You can imagine how well that worked. I blew peoples' minds with the idea of "building" a database package
It's something that seemed small and simple to implement, but has filled a not-insignificant portion of nights and weekends for over six years now. Then covid came around and dried up most of my consulting income, so I figured why not really prioritize it and see how far it can go? Still small, but growing nicely now.
Also reluctantly abandoned the flawed "build it and they will come" mentality and started splitting time evenly between development and marketing. This has probably contributed more to the project's recent growth than several thousand hours of dev time. Take heed, o ye ambitious developer-founders! :-) Recommended resources: Product-Led Growth, Developer Marketing Does Not Exist, 80/20 Sales and Marketing, BusinessOfSoftware.org talk videos, Microconf talk videos (on YouTube).
I'm casually experimenting with this too, to improve AQ in my home office. Do you recall the surface area in the 6-inch-deep bioreactor (or total volume)? The only hard numbers I've found are from the Russian BIOS-1,2,3 experiments, which suggest 18L/person of Chlorella will 75-100% compensate for a person's CO2.
I have 18L of Spirulina, which appears to be having some effect, though not anywhere near a complete offset. Though, my setup is quite sub-optimal, and I've seen articles that suggest Chlorella is a couple times more efficient at biofixation than Spirulina. Continuing to tinker :)
Today Google popped up a little survey in the corner of my account page, with questions like "I trust Google to keep my data private", "It's easy to find out what data Google has on me", that sort.
Answers were one-click response buttons: Strongly Agree, Agree, Neither Agree nor Disagree, Disagree, Strongly Disagree (top to bottom, in that order).
The first time I clicked "Strongly Disagree", a few questions in, the next question had the order of the answers reversed so that Strongly Agree was on bottom. Submitted an opposite sentiment before realizing what happened.
Strikes me as manipulative, like the survey really isn't so much for discovering my opinion as it is for collecting favorable ones. I wonder who will get the results, and to what end?
I've noticed that with single-question responses such as Amazon's "why are you returning this" drop-down, and it makes total sense there. A consistently random arrangement means that users picking just the top answer will have no more influence on the overall report than random noise. Makes less sense when available answers are the same for each question, such that the user might have mentally cached them to avoid rereading.
However, n=1. The timing might have been coincidental.
Check out NaNoGenMo [1], a yearly challenge to write computer-generated novels. Each year gets 100-200 entries (see the GitHub Issues tab) using various techniques. The resource links are treasure troves as well.
Other relevant links I've collected, hoping to do this someday:
FWIW I have the 6290 (2016 model) and haven't run into any annoying misfeatures. Crisp and smooth at 60Hz, UHD color mode. Was stuck at 30Hz and perceptibly laggy until I forced it to 4:4:4 in the nVidia control panel.
Everything online tells me the display lag is unacceptable, but I haven't noticed it personally even when FPS gaming. Maybe it's the conditioning from gaming on an underpowered PC growing up :)
Earlier this year (~May) they shut down their API endpoint that rendered handy little stock chart images with a surprising amount of useful features. Any alternatives out there, other than tying together a charting lib and data API?
The only killer use case I've encountered so far is being able to yell "hey Cortana! Next track!" across the room while playing with a toddler, since either walking over to push a button or pulling my smartphone out to advance it remotely would totally disrupt the current interaction with my child.
Or I could just curate my playlists more carefully.
Everything else is either too low information density (this is why I get the weather from an app, not The Weather Channel) or more efficiently handled manually (music control, search queries) in most situations
