 |
What is the purpose for this? |
 |
it can only write to one location, which is always the first data directory do you want to read from multiple locations? |
 |
My personal purpose is because I use save states with an emulated machine, and store everything in RAM for portability of saved states between users. And also want a 2nd copy on DH1: (so I can later sync score files with a webserver). Right now, I use one or the other and convert them when needed. I took the liberty for requesting this feature as it would make sense to me if we could also store to multiple locations as I already know that the ability for reading from multiple locations is already available through comma separated paths. Although I havnt fully tested this, I believe if the contents in one path are lost (for example RAM: after a reset). We can failback to loading data from the 2nd location (for example the DH1:) In real conditions it could be thought of as a secondary repository for safe-keeping of scores and saves. |
|
|
This would make the io operations and error handling much more complex. Sorry, I'm not going to implement this. You could try to use ExecuteCleanup to manually copy changed files to a second location. |
|
|
No problem, I had to ask though and thanks for the suggestion. I am just starting to look into the series of "Execute*" commands. Seems ExecutePostDisk might be useful for my case, so Will be giving it a try. Thanks again! You guys are the best! |
- Anonymous
