On x64 linux DF 43.05 I've had the best luck with DanFritz's fork, due to a "participants" assertion failure he appears to have fixed: https://github.com/DanFritz/Dwarf-Therapist/commit/ea784aa347c618ce5ef21485f72c7995db6ea9bc
Seems like the wrong way to fix that to me, unless there's some meaning to 0x10 that I'm missing. Does Hello71's fork work?
Ok I tried Hello71's fork now, it works great! Looks like he did more x64 stuff. When I had initially glanced at Hello71's fork on github I didn't see any change there so I assumed only DanFritz's fork had fixed the error I had gotten.
I am not particularly interested in working on DT at this point (mainly because DF is closed source, but good luck convincing toady to open it), but I would be willing to answer questions about DT internals and review (and possibly pull in) patches in #dwarftherapist on freenode.
I know what you mean, but it's probably best DF stays closed source. Far too often on open-source projects I'd get livid non-grateful developers blaming me for their workplace problems... their fault for using a free opensource utility/library in beta stage for their $$$ product in their workplace, then they have the nerve to blame me for their failure to meet deadlines and demand I immediately fix edge-case bugs which show up when it is integrated into *their*, not *my* systems for free!? I was idealistic before then, but I'm permanently turned off after those incredibly disrespectful experiences.
In Toady's case he'd probably just get a bunch of ripoff clones made by developers asking $10-20 on Steam for their rudimentary artwork/theme/style changes. It's happened with other open-sourced games, even when only a fraction of the codebase/art was open-sourced.
I would hope he has made plans for who has stewardship of the game when he passes on.
Also regarding the DT fork, the const function parameters in the DT code are best const for maintainability, as they both make the code clearer and make future accidental logic errors involving those parameters become compiler errors. It is good practice.