Prev: Module and Function Availability
User Permissions
Permission for certain operations can be granted and denied by the user. Any operation with insufficient permissions will throw ExcNotPermitted. Selecting opens a dialog to edit the permissions.
Each m function presented in the library document lists the permissions it requires, as described in the previous section.
The individual permissions are:
| Name | Bit | Meaning |
| ReadDoc | 1 | Read access to files in system.docdir and its subdirectories. |
| WriteDoc | 2 | Write access to files in system.docdir and its subdirectories. |
| ReadApp | 4 | Read access to other application's data. |
| WriteApp | 8 | Write access to other application's data. |
| FreeComm | 16 | Access to free communication resources (receiving messages, Bluetooth). |
| ReadAll | 32 | Read access to all files. |
| WriteAll | 64 | Write access to all files. Granting write access to all files also allows modifying the permissions. |
| CostComm | 128 | Access to chargeable communication resources (sending messages, TCP/IP). |
| Device | 256 | Write Access to the device state (power, reboot). |
| |
Thus, if a function requires Read(file), then
- If file denotes a file or directory in system.docdir or one of its subdirectories, the ReadDoc permission must be granted for the function to succeed.
- If file denotes a file or directory outside system.docdir or one of its subdirectories, the ReadAll permission must be granted for the function to succeed.
Likewise, if a function requires
Write(file), the
WriteDoc or
WriteAll permissions must be granted.
Next: Path and File Names© 2004-2011 airbit AG, CH-8008 Zürich
Document AB-M-LIB-888