Started by Ashley, February 15, 2009, 12:12:52 AM
0 Members and 1 Guest are viewing this topic.
Quote from: jamespetts on February 15, 2009, 11:05:17 AMHmm, I'm interested - how would the dat file editor and makeobj integration work? I am wondering how that would end up interoperating with Simutrans-Experimental, which would use additional options in the .dat files and a special version of Makeobj...
Quote from: VS on February 15, 2009, 11:12:34 AMAs long as it is a superset of normal makeobj, it should work. Obviously any additional functionality is unavailable...EDIT: this version no longer has the interface for adding parameters from gui, so it should be irrelevant.EDIT2: Oh wow, it works! First time I was able to use it. Good job!
Quote from: vilvoh on February 15, 2009, 01:04:35 PMGreat!! some quick thoughts from first contact:The new GUI it's more simpler and intuitive. All options are accesible without having to search through the menus. Finally there's support for Frontimages and winter versions. The dat file options menu is more flexible but more difficult to manage. This time, you have to know the specific dat options of the object you want to develop, in case you want to make the pak from Tilecutter. I think I understand why this has been implemented this way. Makeobj development is faster than Tilecutter's, and if you create a static dat files options interface, you'll have to change with every new makeobj release. After all, Tilecutter is a tool for cutting images, not for creating dat files. It's a reasonable choice.To sum up, from my point of view, you've done Tilecutter more simpler and easy to use...two thumbs up!