Is there a way to not have to turn my head sideways to view job names? I'd rather turn my head sideways to view dwarf names.
regarding column headers: I have a plan for those in the coming future which is a graphics based grid layout. Instead of using the default OS tree-view. This will also allow for OpenGL accelerated drawing and a hopefully much more flexible grid system. You'll just have to trust me that this is a good thing
I have experimented a lot in the past with header drawing, and the tools Qt gives me for this are a bit lacking at the moment, hence me looking into a graphics based solution.
Ah... So does this mean the next version will fix that bug?
Or can I do something now... Because its just killing me inside
Yes it will be fixed in the next version, and you have to either wait for the next binary release, or compile yourself from source
One feature request, though, would be to allow us to set initial sort order in options. For instance, to set the default sort to be by (as an example) the five smithing skills in order of importance. My preferred sort is to sort by each column so that the dwarf skills end up making a diagonal line from top left to bottom right. (adding something along the lines of the ORDER BY SQL statement would be perfect)
Oh, and I noticed in the latest version (as opposed to the version I was using in 40d) when I click on a skill it sorts ascending and puts all my skilled dwarfs at the bottom. This is slightly annoying, since I have to click twice to get the skilled dwarfs at the top.(as you can see, using my preferred sort doubles from making about 50 clicks to making about 100 clicks unless I employ more brain cells than I have dwarfs and start from the other end of the screen- and that still leaves skill-less dwarfs at the top)
Sorting needs some real love. It has been a sort of ugly hack since the beginning. It sounds like you're asking for 2 things here.
1) Allow user to set preferred sorting order in options
2) Default to descending sorts on skill/labor columns
If you could enter those as tickets, they would be about 1000 times more likely to be implemented.
http://code.google.com/p/dwarftherapist/issues/entry?template=Feature%20Request