Break out file operations to an overlay


To reserve more space for framework functionality, we need to move the following operations to a single overlay:

1) File Copying
2) File Renaming
3) Folder Creation
4) File/Folder Deleting

This should free up considerable space in the main program and allow us more room in the overlays.


cybernesto wrote Sep 8, 2013 at 9:17 PM

I would not like to make this basic functions depend on the A2Command Disk being in the drive. This could mean a lot of overhead for someone working with a single drive. I have found other places in the code where some ram can be saved. Right now we could go back to 8k overlays again if we needed to. I wanted to wait until some of the features in the issues list were solved before doing this.

plbyrd wrote Sep 8, 2013 at 9:21 PM

I added code to the dispatcher to remember which overlay is in memory, so that the user doesn't have to replace the disk each time they want to perform a function. I could also make it load the file operations overlay at start to that it's already in RAM.

plbyrd wrote Sep 8, 2013 at 10:15 PM

Added code to load the File Operations overlay on startup. This solves the problem of allowing the user to immediately start copying files without the disk in the drive.

cybernesto wrote Sep 9, 2013 at 5:29 PM

Good idea! This way both problems are solved.