If you preparing for the next release, maybe it's time to fix #107?
Not really... I just want to take out some of the persistent issues that are beginning to piss me off. Jobs are in a good place but we're still missing a couple of those. I also want SE to work before next release, although writing logic to fill Gismo's new interface might prove really, really time consuming (ALT is to just fall back to old, working design).
#107 is a good candidate for taking out as well, gonna take a look at that after the ND thing is done. I think that the way to do that is presort the data using a dedicated function and then use that data in the ND screen.
The reason I dropped jobs for a while and started hacking at other things is that there are too many distraction all over the game and the code and there is a constant need to study/circumvent that. We changed the
main concept from a simple SimBro design to WM and then to something a lot more complicated than even that. Traces off older logic are left all over the code and a lot of that is not compatible with the new design. To make it worse, there are still older coding approaches left all over the place that would have served SimBro and sometimes even WM concepts perfectly but are no longer acceptable because it plainly requires more complex and confusing code to do simple stuff.
Codebase is getting a lot,
lot better and easier to work with, but we're not there yet
![Sad :(](https://www.pinkpetal.org/Smileys/DarkB/sad.gif)
We will not be there for the next release either but after all the bugs in the release are fixed and I do the next major refactoring effort, that's where I believe the code base really become "PyTFall" instead of that merged with "SimBro"/"WM2" designs.