This "graphical glitch" existed in older versions too.
viewtopic.php?t=64942

Whoa, cool stuff. Are you open for annotations and possibly even some addition/modification with icons or improvements? Maybe open a Github/GitLab repo, where we can open issues we see with some icons or modify some stuff? - row 1, icon 6 and 7: the dot mark does not aligned to the corner of the pen...

Modernisation is good, but has to be done with some "clear idea" on how FreeCAD is now and probably why some decision were taken and why are retained after some years , usually when a new developer will enter the team, if you read carefully, the discussions between "legacy developers...

And since wmayer is the only one, who can do this... You just described the most pressing issue and a major roadblock for further improvement. Just think of the bus factor ! This needs to be addressed. IMV right next to the famous TNP problem. The code base is too complex and not easily understanda...

Interesting. Haven't tried the software named in the forum post yet, but looks like they shut it down -> see the last blog post . All repos are archived as of December 2021. Graphical visualisation of a legacy and complicated code base helps in exploring and understanding, but it's not a good soluti...

Are there maintenance tasks on the code base that simply cannot be done? - The current codebase is not easily testable (unit test / integration tests). - There are no benchmark tests which would allow to optimise the code. - The code base is not easily understandable, as the is no folder structure ...

You can't easily unit test code with embedded dependencies, which is to say virtually all FreeCAD code! One of the main culprits of this legacy code base. I think we both agree that this is in dire need of modernisation. -> Interfaces, Dependency injection etc. From what I've seen the recommended p...

4. start working on code, in particular the core. - start untangling code by organizing files in subfolders. src/{App,Base,Gui} have way to many files in them - refactor, modernize and make the code modular, but do NOT change the general functionality / architecture yet Totally agree. /src/Base/ al...

andrecaldas : No no, not necessary to delete your comments. They are actually a quite illustrative example. --- The first thing that has to happen is the powers that be need to be supportive. Don't hold your breath and wait for this to happen. Change has to start from oneself. If you want a project...

Yeah, interesting, isn't?! Coming back to the initial question: How does one create an environment to achieve modernisation of a seriously legacy codebase? What do you think? It would be to avoid exactly that like above. Even if you get triggered and someone is (perceived) "wrong on the interne...