...
Here you can see/change the path to the “RealFlowCommands.xml” file. This file contains paths and icons for your custom scripts/graphs/plugins and is used with RealFlow’s "Commands Manager" menu. Again, “…” is used to edit the path and “Default” loads the standard settings.
The "
...
RealFlowCommands Environment Variable"
If you are working in a network then it is usually necessary to provide the information from the “RealFlowCommands.xml” file globally for all RealFlow installations. This way, all users will have access to the same collection of scripts and plugins. Of course, it is possible to store the file anywhere and point to it with the “File” button described above. But, for multiple RealFlow licenses this can be a very tedious task. A much more fashionable way is to define an environment variable:
RF_COMMANDS_ORGANIZER_FILE_PATH
For example:
RF_COMMANDS_ORGANIZER_FILE_PATH=/mnt/file_server/realflow/RealFlowCommands.xml
When this variable is defined, all RealFlow installations will look for the “commandsOrganizer“RealFlowCommands.dat” xml” file under the path specified there.
...
If you have worked with previous RealFlow versions then there will be the “commandsOrganizer.dat” file. This file contains information about scripts and plugins attached to the GUI. This file still exists in RealFlow 2014, but has been replaced by a two XML files (RealFlowCommands.xml and RealFlowShelves.xml). When RealFlow 2014 detects the DAT file, a dialogue appears and you will be asked if you want to convert your previous settings and import them.
...