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.

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.

As Corbo said, TileEdit needs it a lot. I haven't checked out PyBIN but I'll probably mess around with that a bit more as opposed to using BinEdit.

Really excited for the update checker. Will make the program really accessible too. Good shit!

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?

I agree with pronogo. I still use datedit over pyDAT because it makes things harder to achieve.

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.

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.


Will look into those next.


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


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!


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!


Odd, will look into.

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!

Send your ICE copy to me so I do not have to google it. I wll get your screenshots ASAP.

I will also get you farty's one. I dont think he will mind of I send it to you.

I'll be doing some very simple modding tutorials after Inconsummate is done, if you want to host the videos there. Depending on program usability and stability I'll use PyMS programs exclusively, alongside firegraft and MPQDraft.

Both are now updated. For PyDAT, since it doesn't know which type of dat file you want to open, it only has specific dat lastpaths for saving.

Fixed the issue you reported Pr0nogo, and if you guys have any more specifics on how to improve PyDAT, i'm all ears!

Fixed.

That would be awesome, I would definitely be interested.

Thanks!

Thanks for the updates, poiuy! Any interest in designing PyGRAFT or PyDRAFT to replace firegraft and MPQDraft?

I have some interest, but I don't think I ever will. Its much more complex than other programs, and would require a lot more of my own investigation and reverse engineering of SC rather then just taking already documented file specs and implementing them. If there were a lot more interest in modding and more issues with the existing graft/draft tools, then I would have more incentive. Also I've always wanted to finish a map editor, so would prefer to spend my time on that rather then start a new project.

http://imgur.com/a/fFQjK

There you go, unfortunately it seems to try to load up a preprogrammed SC path from like camsys era, so who knows which path it is. so I cannot actually test funcionality, I-ll try to figure out how to hack it to load up something. As for now it-s just the interface.

If you would also like it, I am pretty good at designing UIs for modding programs, just ask farty

EDIT: I just realised that you just zipped me your installation copy. I will try to get the installer and install it myself so it does not try to load up sc from a folder called \poiuy qwert\porn\

Post has been edited 1 time(s), last time on Jul 4 2017, 4:38 pm by Corbo.

Thanks! I should have been a little more clear in my last post, I only need screenshots of the GRP preview sections.

Sure, if you want to design an iscript previewer that would fit in PyICE I would be glad to take a look.

Hm, I don't think that should matter, but I have no idea. Thanks for looking into it, i'll reward you with more files from that folder if you can get more screenshots

in PyDAT. Is the red button next to the wav name supposed to play the sound?

It does not. And it would be really sick if it did that.

Crashdump from PyTBL after trying to search 'Commando re' in the search function.

Crashdump from PyGRP after scrolling through a grp with a lot of frames.

Edit: poiuy, is there any chance we can integrate farty's work with DAT expanders into PyDAT? images.dat -> units.dat -> weapons.dat are my priorities at the moment, if it's something you think we can work on.

edit 2: More crashdumps, both for PyGRP.

#1 - Attempting to save a blank file (new -> save as)
#2 - Attempting to add a frame to a blank file (new -> import frame)

Post has been edited 2 time(s), last time on Jul 9 2017, 10:16 pm by Pr0nogo.

It should. It used to work on windows and still works on Mac... Could you edit PyDAT.pyw and insert a "raise" after the "except:" at the top of the file, like this:

And see if that produces an error I can look at?

Hmm looks like it can't log to the console, so you must be running the program outside of the console. Did you change the way you run the programs? If you get an error on a 'print' line you can just ignore it there will be no issue continuing to use the program. For a temporary fix, delete the print lines from the code, or go into Libs\trace.py again and set DEBUG to True (and if you get lag issues again, FSYNC to False) so it goes to Libs\Logs instead. I'll look into a better fix soon.

Yep I would love to, though its a lower priority than fixing existing stuff.

Those were introduced when I did the settings rewrite They should be fixed now.

Thanks!

I did not change the way I run any of the programs, just double-clicking on them as usual.

How do I know if it auto-updated? edit: looks like the update isn't automatic, oops.

Hmm, odd. Hopefully the temp fixes work for you until I put out a proper fix.

Yeah, just an update checker I've been thinking about adding an auto-updater, but its on the back-burner for now.

If I run into any more problems I'll let you know. For the time being, I haven't had any issues. Thanks for your quick updates!

I updated the logging so you shouldn't have any issues anymore. I removed DEBUG and FSYNC options from trace, DEBUG is now always on, and FSYNC is always on but only for errors.

Got this from PyMPQ when trying to create a new MPQ.

Looks like I didn't setup default values for the maxfiles and blocksize settings, and you found the one case (didn't go to settings or open an MPQ before creating a new mpq) where it would be an issue Should be fixed now, thanks!