View Single Post
Old 12-09-06, 02:21 AM   #43
JScones
Navy Seal
 
Join Date: Apr 2005
Posts: 5,501
Downloads: 19
Uploads: 0
Default

I think there is merit in pursuing this idea. Perhaps a simple wizard or structured sequence of steps would be a good way to go? Something like (thinking on the fly here)...

Step 1 - user selects "source" SH3 folder. Ideally this would be the nice clean and patched "base" install of SH3, but I suppose it doesn't really matter. The player may want to "clone" another installation for some reason.

Step 2 - user enters the destination location and folder name.

Step 3 - user enters savegame folder name (maybe MultiSH3 can derive a "default" set of characters from the name entered at step #2 - user can always overtype).

Step 4 - user selects options like whether they want a new SH3 icon placed on the desktop pointing to the new installation.*

Step 5 - MultiSH3 copies the source to the destination.

Step 6 - MultiSH3 creates desktop icons as requested at step #4.

*MultiSH3 could also attempt to connect SH3Cmdr, but this may be dangerous, or may become quite convoluted. For example, the user may select their NYGM copy of SH3Cmdr to connect to their GWX SH3. Or they may want to "clone" their SH3Cmdr as well - so does MultiSH3 facilitate that? It could do it easy enough - ie user selects an option confirming that they want to clone SH3Cmdr, user then enters location of source SH3Cmdr, MultiSH3 then copies to a destination using "tag" already provided at step 3 and creates a new desktop icon pointing new SH3Cmdr to new SH3 installation. But do you want to get this detailed or specific?

EDIT: Of course, underpinning the above would be some kind of menu asking the user if they want to copy SH3 or just change the save game folder.
JScones is offline   Reply With Quote