AWESOME! Finally, something to make it less of a pain in the ass.
I did just have a glitch though. Tried to open it for the first time, said rsbe01 found, I said look for another name, but decided just to close it and try to drag and drop my gct. It wouldn't let me close it though. It kept popping back up regardless of what i clicked. I had to go into task manager and end the process.
Also could you explain the deal with having 4 different stage drop-downs? Which does each do? I assume they are for rel to use, icon, tracklist, and... not sure what else, but that's just my guess.
Anyway I will try it out for real this weekend. Thanks.
I've fixed that and other glitches in the program, I suppose I released it too late in the night (over 5am, I should sleep more...).
Now you should be able to switch flawlessly between gct files.
Also, added the option of changing the used gct file while using the program already, just by doubleclicking on the name of the file on the top.
Also, by trying the outdated program in the university a few minutes ago, I've had some strange error by opening a gct file of mine, used in my STGCUSTOM PACK 2. I've investigated a little, and it seems like that code was wrong. I forgot to include the last icon/stage in the counter for that part, and the program just tried to open something beyond its possibilities because of this. I've added a error handler for this, so if you open a gct file with errors in that part, the program warns you. Once warned, you can keep using the program normally, and edit the problematic parts, if any.
About the 4 different drop-downs, maybe one of them wasn't necessary, but it's interesting to see it all. I'll explain quickly.
There are 2 parts in the code. One of them manages which stages will be possibly loaded, and which icons will they be using. That's the part of the left. The top one is just the stages loaded, while the bottom one is the icon used for the stage. They will move together so you always see which icon is used for a stage. In most cases, they will say the same. But, when you reach the custom stages (the added ones), then you won't find a custom x icon, but a number of icon. Those numbers are the used ones in the common5.pac file, in the system folder. So, you can manage which of them are you gonna use for your stage. There's an edit button for this. When you click the edit button, a new window is open, and you can change both loaded stage and loaded icon for a certain slot. You can repeat them, there's no problem with that. I mean, you can load the same stage from 2 different icons. That has not much sense, but it's possible to do.
The other part of the code manages which of those stage/icon pairs are loaded for each of the 2 pages in the game, the brawl and melee ones. The top one is brawl, and the other is melee. If you watch the list, you will see stage names. If I wanted to be exact, I should have included both stage and icon in the list, but as I'm supposing nobody is using a stage twice, I'm only listing the stage name.
Well, those stages used per page can be changed, added and removed. Don't add too many, as there's some limit of stages per page, I guess 39. Maybe I should have placed a limit in the program so you can't have more than 39 stages per page, but I've not done it. I suppose people will just be intelligent and won't try to force the code.
To add or remove, you have to select one of the stages, check one of the boxes with the proper option, and click either 'to brawl' or 'to melee'. The stage counter will automatically change to reflect the number of stages per page you have now.
Using those buttons without checking the options below just changes the stage/icon used in that slot in the page. If the adding option is selected, the added stage will come from the selected item in the left drop-downs too.
I guess that's it. I think that nothing else is needed to run the program and manage to easily edit the roster. With this, you can even change the order of your stages, and not necessarily add more.
Also, unlike the ASL Tool, this program can write the code into your gct if it's not found in it.
Please, keep always a copy of your previous gct, just in case.
