2009-11-20, 12:35 AM
Hah, am I right that your PumpkinPaster tool needs the Map Editor window to be titled SOM_MAP? (note to self, change that back before releasing new translation patch ) 
I had a thought inspired by your utility; it seems that the Map Editor can edit and save maps with Pieces numbered up to 20,000+ but SoM can't 'output' Pieces numbered over 1023. An app that performed a set of procedures similar to those used in your tool could let people have access to more than 1024 Pieces in the Editor by processing the MAP file before it is 'Output'.
Example:
User builds map with 300 different Pieces with ID numbers between #1-2000 (aka more than the 1023 currently allowed by SOM).
When activated, app. scans MAP file and copies any PRT files used in it to a new folder named 'Working Folder'.
App. then renames the copied PRT files to lower numbers in sequence (below 1023) and changes the Piece numbers in the MAP file to match (after making a backup of the MAP file).
App. then renames SoM's 'parts' folder to 'parts.orig' and renames 'Working Folder' to 'parts' and auto pushes SoM's 'Output' button.
Lastly, after Output, app. changes folder names back and restores the backup (original) MAP file.
The user should end up with a functioning 'output' MPX file and their original MAP file.
Another option would be an app that let the user 'scan' the Pieces they want to use on the current map, and then auto-renames those Piece's PRT files to low #s (below 1023). That would let the user choose up to 1024 Pieces they would be using on the current map from a library of thousands of Pieces. The app could save a 'conversion table' for each MAP file that notes all the changed PRT numbers (ie 9536.PRT>0000.PRT, 0126.PRT>0001.PRT etc), thus saving a record of the PRTs that need to be renamed to view the map.
I had a thought inspired by your utility; it seems that the Map Editor can edit and save maps with Pieces numbered up to 20,000+ but SoM can't 'output' Pieces numbered over 1023. An app that performed a set of procedures similar to those used in your tool could let people have access to more than 1024 Pieces in the Editor by processing the MAP file before it is 'Output'.
Example:
User builds map with 300 different Pieces with ID numbers between #1-2000 (aka more than the 1023 currently allowed by SOM).
When activated, app. scans MAP file and copies any PRT files used in it to a new folder named 'Working Folder'.
App. then renames the copied PRT files to lower numbers in sequence (below 1023) and changes the Piece numbers in the MAP file to match (after making a backup of the MAP file).
App. then renames SoM's 'parts' folder to 'parts.orig' and renames 'Working Folder' to 'parts' and auto pushes SoM's 'Output' button.
Lastly, after Output, app. changes folder names back and restores the backup (original) MAP file.
The user should end up with a functioning 'output' MPX file and their original MAP file.
Another option would be an app that let the user 'scan' the Pieces they want to use on the current map, and then auto-renames those Piece's PRT files to low #s (below 1023). That would let the user choose up to 1024 Pieces they would be using on the current map from a library of thousands of Pieces. The app could save a 'conversion table' for each MAP file that notes all the changed PRT numbers (ie 9536.PRT>0000.PRT, 0126.PRT>0001.PRT etc), thus saving a record of the PRTs that need to be renamed to view the map.