Alexander
Alexander
What do you mean? Many .version files have all "KSP_VERSION", "KSP_VERSION_MIN", "KSP_VERSION_MAX"
the big map already can be updated manually and often by manual clicking. Instead of manual clicking 4 times in timewarp in active scanning, I want just 1 checkbox click...
Also you can take some ideas for names there: [CommunityPartsTitles/localization/en-us_patch_kfoundries.cfg](https://github.com/yalov/CommunityPartsTitles/blob/master/GameData/002_CommunityPartsTitles/localization/en-us_patch_kfoundries.cfg)
or make them DIRECT
Probably, I should ask @JuanjoSalvador
@JuanjoSalvador, any luck with it?
UPD. ok, clean-css approach is `flex`. ``` .sidebar{ display: flex; flex-direction: column; height: 100%; } .container{ flex: 1 0 auto; } .sidebar-sticky{ flex: 0 0 auto; } ``` ----------- OLD....
@mmabluesky it's your turn now, just 2 years :) @easylogging I think in this issue, we want to configure several loggers (even without levels), that log to different files ```...
I found: https://github.com/abumq/easyloggingpp/blob/master/README.md#global-configurations it isn't the el::Configurations, but ``` el::Loggers::addFlag(el::LoggingFlag::MultiLoggerSupport); // Enables support for multiple loggers el::Loggers::configureFromGlobal("./easylogging++.conf"); CLOG(INFO, "default", "output")
The cmake VS2022 projects have the cmd arguments in `PROJECT\.vs\launch.vs.json`, as "args" value per project target: ``` { "version": "0.2.1", "defaults": {}, "configurations": [ { "type": "default", "project": "CMakeLists.txt", "projectTarget":...