Forum Replies Created
-
We’ll want to update the build files to tell MSVC not to enable warnings for system header files. See: https://learn.microsoft.com/en-us/cpp/build/reference/external-external-headers-diagnostics?view=msvc-170
GCC and CLang handle this better and don’t issue them for system headers by default.
I also need to update the build files to mark some libraries as system headers. Will get there, still trying to get the code-base building. Sorting through more error logs at the moment.
Some of the files are complaining about a lack of forward declarations for classes they use even though we’re including the headers that set up the classes. We’ll definitely need to figure out why these errors are occurring but I’m re-adding the forward declarations for now, temporarily, until we figure it out. I suspect it may have something to do with the over use of macros but I’m not entirely sure.
Thus far, the complaints about the lack of classes being declared are from files where I removed the forward declarations.
Edit:
Looking it over, it looks like it may be due to the classes they need also needing them so more circular dependencies. Not much we can really do about that, I’m afraid, other than forward declarations. At least, I think so. Best I can do is just add them where the compiler complains, I guess.
We can probably ignore the part of the macros messing it up as it doesn’t appear to be case in this instance. Not to say they aren’t problematic, though.
Working on the clean up. Several things are being caught so I’m fixing the stuff I missed. Some of the newer 64-bit functions are different so I’ve updated the variables for those as well. I’ve temporarily used
unsigned long longbut we’ll want to switch tostd::uint64_tonce we update the formatting strings, which will need to be done all at once as they’re different from the older form.I don’t think those functions are used anyways but I’m updating them just in case. I’ll make a tracker note to check for 64-bit compatibility to reduce the likelihood of an out of range issue
Once it starts building again, I can merge it back to the main repository and we can go from there. 🙂
We’re more than likely going to need to run cppcheck multiple times as more stuff will be caught as we fix other things. For example, removing unused functions will cause other functions that were only being used in those to be marked as unused. It should catch most things in the initial pass, though.
Looks like I may have figured out my screen flickering bug that activates on session lock: only happens when the monitor is set to 144 Hz so it looks like a bug in the compositor. Will open a ticket when I get the opportunity now that I know what’s causing it. I set the refresh rate to 60 Hz yesterday (while leaving variable refresh rate enabled) and, today, the flickering never materialized. Will keep monitoring it for a few days before I open the ticket just in case it comes back, though.
Adorable, aren’t they? Haven’t seen too many slugs around here in recent years. I suspect our increase use of pesticides are partly to blame. Used to be a lot more common before we upped the spraying around five years ago.
These days, more and more media is simply parroted and there’s much less original reporting than there used to be. Reporters are greatly preferring quantity over quality which is leaving important context out of news in general. I’ve seen some articles that claim such and such is closing but the article leaves an important point out: the closing is temporary. Just an example. I think the increase of access to reporting platforms is to blame as it lets anyone be a reporter with a large audience so there’s not much incentive to make sure the quality is up to par.
Our drought continues and fires are starting up around the state. People need to learn to be more careful!
In the mood to shop for unique decor, just not sure where to look :/
All sub-records have their data blocks as global scope with the classes having to go back and forth. We may want to change that at some point to having class-based scope. Will need evaluation.
I don’t see a reason for them to be globals as the values will change for each sub-record in play so it all sounds rather inefficient but we’ll get there.
Playing around with the
cppcheckconfiguration some and this is what I’ve currently got for the settings:
cppcheck --enable=all -I . --inconclusive --language=c++ --library=mfc --library=microsoft_atl --output-file=cppcheck.log --platform=win64 --quiet .
I’m currently unsure about--cppcheck-build-dirbut it may be useful as well with--cppcheck-build-dir=.It doesn’t seem as though
cppchecksupports config files, which would be nice as we’ll need to ultimately run it against multiple platform configurations but that can be fixed by adding shell scripts to the repository if we feel that it would be helpful.--enable=allturns on all of the checks, including the ones not turned on by default-I .tells it to look for the include paths relative to the root directory--inconclusivetells it to turn on additional checks that it can’t necessarily confirm (useful for catching functions that use different parameters in the declaration and defintion)--language=c++ensures that headers are being parsed as C++ instead of C, which is important as sometimes very little C++ is used in headers so C is detected instead--library=mfcand--library=microsoft_atltells it to load the configuration files for dealing with MFC and the ATL stuff.--output-file=cppcheck.logsaves the run to a log file to make it easier to sift through--platform=win64tells it to load the configuration for Windows (which, as we know, differs from other, more standard compliant platforms) and to check to make sure everything is 64-bit compliant--quiettells it not to report anything in the terminal
I’ll update the threads soon with a progress update 🙂
I’ve added a note about examining the icons as there seems to be several duplicates.
.icofiles can handle the PNG type but we’ll also want to see what’s supported by Linux and the GUI toolkit. It’s probably something that needs to wait.Still fixing up the circular dependencies and boolean types. Slowly making progress but progress is progress.
I just re-sleeved some old cards the other day. The 30 year old sleeves were pretty rough. 😛
May be a good idea to run Memtestbefore sunsetting it. HDDs are harder to test but the SMART information may help some
For the CPU, you’ll want Prime95
Granted, Prime95 is mostly for stress testing but could let you know if something is going belly up.
For GPU’s, you’ll definitely want FurMark. 🙂
Sorry, I mean the function that simply turns off the display while keeping the rest of the system on
After more experimenting, I’ve found that it’s the act of fully logging out and back in that fixes the flickering that is triggered by the screen locker as opposed to a reboot.
I’m definitely going to need to sit down at some point and do some troubleshooting and possibly open a ticket with the official support team as I’m also using their hardware. That said, I probably should have waited even longer to upgrade as COSMIC is definitely not ready for primetime. Too late to worry about that now, though. If it gets too obnoxious, I’ll probably go back to XFCE or Cinnamon and hope they work better.
Yuck!
While we’re mentioning Chrome, they finally added vertical tabs back to the feature set after removing them fifteen years ago without fanfare. Yay!
Split view can be handy but I do feel that its current design is rather clunky and, as a result, I rarely find myself using it
