The following table lists classes in this documentation.
|
Name |
Description |
![]() |
Directory in a FileSystem. Directory object in a FileSystem. When a directory is initially obtained from a FileSystem it is in a closed state. @ingroup VolumeSystem | |
![]() |
File object in a FileSystem. File object in a FileSystem. When a file is initially obtained from a FileSystem it is in a closed state. @ingroup VolumeSystem | |
![]() |
Base class for all FileIO objects. @ingroup VolumeSystem | |
![]() |
Base class for objects in a FileSystem. This class provides the functionality required by all file system files, which is basically name and attributes. @ingroup VolumeSystem | |
![]() |
Collection of FileNode objects. File systems represent collections of FileNode objects. Functions are provided for manipulating FileNode objects but the internal organization and representation is opaque. Path names must be fully specified relative to the file system root and names cannot contain relative path information. @ingroup VolumeSystem | |
![]() |
This is class Torque::FS::FileSystemChangeNotifier. | |
![]() | ||
![]() |
The VirtualMountSystem extend the mount system by allowing you to mount and access multiple filesystems on a single root. This allows you to mount multiple volume files on a single root without needing to change source paths that reference those volumes to use new roots. For instance, you could mount "missions1.zip" and "missions2.zip", on the same root "", and you could access files from either one. If you need to mount a writeable filesystem on a VMS, you should mount it as the first filesystem on a root. File writes are handled as follows: 1) If you try to open... more |
Copyright (c) 2015. All rights reserved.
|
What do you think about this topic? Send feedback!
|