PyMS and ProTRG developer
Commit dbcb4c3 broke PyDAT on my pc. It seems to get stuck somewhere as the python process uses a lot of cpu and has to be killed manually. No GUI or any kind of error appears ._.
Nothing in that commit looks like it could cause an infinite loop. Are you on that commit or the latest commit but dbcb4c3 is the earliest commit with this problem? If you are not on the latest commit please update and tell me if its still happening?
So, something hit me while facing some more issues with editing the tileset. To understand me you first have to see this picture:
The selected megatile group should look like the one below. Why doesn't it do that? Because some mini tiles use the same mini tile image. But, why?
I mean, the program, at the moment does NOT, replace megatile groups. It just adds new ones, so why doesn't it just export whatever image "as is" and instead it needs to use the old megatile group configuration, thus, creating problems like the one I face.
I'd understand if it was a replacement for the megatile group, in which case, yeah, they'd have to use the same flags (even then I'd still argue if it is completely necesary) But it is now that case... so yeah. I should be able to just import whatever mini tile image information I want without these issues if it's just added at the bottom so I can reference the actual real image I am importing and not something scrambled up.
I think you are doing something wrong. Here are some detailed instructions on how you would change the graphical portion of an existing MegaTile Group without effecting that groups settings, for the current way the program works (which will hopefully be changing to something better):
1) Click the button with the magnifying glass next to the MegaTile Group at the top to open the Group Palette
2) Select the MegaTile Group you want to change
3) Export the group to its BMP and TXT components
4) Modify or replace the BMP with your own tiles
5) Since all the MiniTile Images in our BMP are not be flipped, but some of the original ones may have been, we need to edit the TXT file to make sure all the FlippedStates are 0 (so like "FlippedStates: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0")
6) Import the BMP and TXT, which will create new entries for everything. You can ignore the new MegaTile Group, we'll just use the MegaTile's that are created
7) Close the Group Palette, the original MegaTile Group you wanted to change should still be selected for editing in the main window
8) Click on the first MegaTile in the group
9) Click the button with the magnifying glass next to the MegaTile field in the middle to open the MegaTile Palette
10) Go to the bottom of the palette and choose the corresponding newly created MegaTile that you just imported. It has the original settings (from the TXT file) and the newly created MiniTile Images (from the BMP)
11) Repeat steps 8-10 with the rest of the MegaTiles in the group
If this does not clear things up you'll need to give me more details on what you are doing, step by step instructions to replicate the issue.
When editing a minitile image with that particulary small editor, both, OK and Cancel buttons do the same. If I make changes and don't want them applied in the end, Cancel is no option
The Cancel button is fixed, and I definitely want to look into making it resizable.
Post has been edited 2 time(s), last time on Mar 21 2015, 7:23 pm by poiuy_qwert. Reason: Added step about flipped states