|
> Yay...congrats! Finally someone finds the time to check the xml mania I've added > 8) Me myself unfortunalety didn't have much time lately due to real life job. It > would be great if I can add your definitions officially later (of course your > author tag will hold your name).
Of course, no problem. I'll keep you posted if any issues arise as well. For anyone building these detectors, heed the advice in the spec about ignoring size when creating the DATs, the rebuilder will not work if a size field is present, since it compares the actual (header-included) file size to the (headerless) file size in the DAT. I'm not sure if checking the 'ignore size' in the rebuilder options fixes this but it may be worth investigating.
> Well..there are some options (match tagdata for example) which work with the > currently loaded profile. You can for example automatically fill in > manufacturer, year, description tags automatically this way.
This sounds very interesting. Does this mean that if there is a 'game' entry with the same name the Dir2DAT will grab the description, etc... from the loaded profile and populate that in the new DAT, allowing all of the manual work of DAT creation to be reused as much as possible? If so, can you tell me the matching criteria? This sounds extremely useful, I can understand why a profile and Dir2DAT would be linked if this is the case.
>I guess for headers > , a header selector box like in settings can be added to dir2dat and that should > be enough for your purposes.
Thanks much, that would be great.
|