PyMS and ProTRG developer
Holy shit. Thanks. Do TILE then BIN
As Corbo said, TileEdit needs it a lot.
PyTILE has been updated. Also I assume you meant PyBIN corbo? That is what I'm working on now. Do you actually use it? Is it working well? I still have it marked as a DEV version but I feel like it could be made 1.0, just can't quite remember where its at.
Last path recording for PyMPQ (separate Open, Add, Extract, etc) and PyDAT (for Open/Save As, maybe a different path for each .dat category? Probably a lot of work) would be much appreciated. I don't use PyMPQ at all, so seeing it updated would make me more likely to use it in the future.
Will look into those next.
I haven't checked out PyBIN but I'll probably mess around with that a bit more as opposed to using BinEdit.
I'm pretty happy with it, even if the UI toolkit I use can barely do the job
It has a much bigger focus on displaying and visual editing then the other bin editors, so it's much more convenient. Its a very young program in PyMS (only two years), afaik only me and Corbo have played with it so it could still be unstable, though it should be coded better then the older programs
Generally PyDAT has been more arduous to use than DatEdit. An example of a poor process is that when you attempt to open a file while you have a different category selected, it'll throw and error because the program thinks you're trying to import the file to that category (e.g. I just had portdata selected and tried to open a units.dat file, and it threw an error until I swapped to the units category). DatEdit knows which files are which and all is well.
I agree with pronogo. I still use datedit over pyDAT because it makes things harder to achieve.
These types of usability issues are the ones I need people to report more of. Since I don't usually have the time to work on PyMS AND do real modding, I don't really use the programs like a person really would, so I don't get a lot of these usability issues. I only just started to do some modding again, partly because I wanted to use the programs to get a better feel for them, and I just could not stand the whole lastpath thing, which is why I started to re-write the settings and fix that
This is another great example, I'll look into it, thanks!
Really excited for the update checker. Will make the program really accessible too. Good shit!
Yeah, I should have done this earlier when I first put it up on github. I'm also really hoping to find the patience to update some docs, make the github readme/homepage more accessible with screenshots and instructions, and some details/tutorials in the wiki section. If anyone has some ideas or wants to contribute that would be a big help!
edit: well, just as I was saying I don't use PyDAT often,
this happened upon attempting to open a dat file. I have used DatEdit to open this plenty of times, so maybe there's a compatibility issue?
Odd, will look into.
I will try to get you ICE but have you checked with farty? He made an iscript previewer of sorts... his could give you ideas.
I just need screenshots of ICE (and/or FaRTy's previewer would be awesome). I have ICE, I just don't have access to a windows PC and can't get it running with wine so I can't actually look at it.
Thanks for the feedback guys!