Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[vintermann]

Thanks for this! There was someone asking about it recently, and I recently needed this info myself, so I take the liberty of doing some thread necromancy.

[jdstauffer]

And I'm the one he was helping, so add my thanks to the list.  I had given up and was running under Wine, now I can go back to running it native.

[breadman]

Well, there would be one way: parent processes can access the memory of their children under the restrictive set of memory-access rules. So if Dwarf Therapist, Stonesense, etc., came with a feature to launch Dwarf Fortress for you, they would be counted as the "parent process" and could access DF's memory. This would only work for one tool at a time (you couldn't run both Stonesense and Dwarf Therapist and have them both be the "parent" of the DF process, for instance), and would require rewriting each tool's code. Not really worth the effort, IMHO, when a single settings change will restore the working status quo ante.

I'm having success with a simple script that launches Dwarf Fortress in the background, then execs Dwarf Therapist:

Code: [Select]

#!/bin/bash
cd $(dirname "$0")/df_linux
./df &

sleep 10
cd ../dwarftherapist/
exec ./bin/release/DwarfTherapist
That lets Dwarf Therapist become the parent process without changing its own code at all.  In theory, such scripts could even be daisy-chained to launch more than one tool, but I haven't managed to get Stonesense working yet.