Hi Morgh, thanks for not taking my criticism the wrong way. I appreciate your work as I was being bugged a lot to update my editor until your tool came out. It wasn't feasible at the time as my work was really hectic and I didn't have the new game anyways.
I used to code in VB6 quite a bit, but I haven't touched it in years and cannot remember much of it. However, I always thought it was under-rated. I could churn out a lot of code quickly back in the day; especially simple GUI stuff. I even got it to do some data intensive processing for work by incorporating some Windows API calls.
It is nice that you tried to write it in the most compatible way. I'm just really used to .NET now, and most PCs have the framework installed anyways.
By the way, I may try to add an import/export item option now that you mention it; kind of like your 'translate item' function.
VB6 is just "a bit" outdated, but I own a legal copy of it. I used it years ago for a lot of projects, so if you don't want to code fast algorithms, system drivers or something else, its still a solution.
I stopped development of my tool. Everything interesting is already implemented. Also I haven't started Warband since months.
If you want to add a really interesting feature whichs also makes your tool something special, then write code to export the text items to python code. Sometimes people start with text editing, and later they realize that the module system is the only way to make their dreams come true...
Thats nothing impossible because there are no function calls or variables (conditions, consequences) at the items. I was just too lazy to do that, because then I have to do that with all text editors. -> You can ignore triggers, because people can't really edit triggers in text mode. So you can disable export function at items with triggers if you want to safe a lot of your spare time