Running Cubiquity app from read-only folder.

[David Williams]

Cubiquity apps will probably fail when run from a read only folder, for at least the foloowing reasons:

1. The .dll will fail to copy to the project root.
2. Changes to the volume will not be written to the voxel database.

The first can be fixed by having the applications installer copy the .dll, and for the second we will probably need to store the changes in a separate database in a temp folder.

[David Williams]

Some progress has been made here in that the Cubiquity native code library can now load volumes in read-only mode, while still allowing changes by storing the changes to a temporary database table. More work and test is still needed on the Unity3D integration.

[David Williams]

I tried testing this by making a build, copying it to a folder, and setting the read-only flag on the folder. However, it seems this makes the files read-only but new files can still be created so it's not a good test. Probably need a real read-only medium or will play with permissions. Perhaps it's possible to mount a folder as a read-only drive.

Also consider what happens when the log file can't be written.

[David Williams]

Documentation should probably be updated to explain that an application's installer my need to copy the Cubiquity .dll to the correct place, in the case that the application itself does not have the required permissions.