Crystal Space 2.0.0: 4.22.1 Using BugPlug

[ < ] | [ > ] |  | [ << ] | [ Up ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 4.22.1 Using BugPlug

There are several ways to load BugPlug in memory:

- `‘Load it manually’`: You can load BugPlug manually in code by adding an entry to your `RequestPlugins()` call (using the `CS_REQUEST_PLUGIN("crystalspace.utilities.bugplug", iBugPlug)` macro) or using `csLoadPlugin<iBugPlug> (plugin_mgr, "crystalspace.utilities.bugplug")`.
- `‘Load it via commandline’`: If you only need to use BugPlug occasionally then the best way may be to just put it on the commandline of your application whenever you need it: `‘app -plugin=bugplug:iBugPlug’`.
- `‘bugplug console command’`: In walktest there is a `‘bugplug’` console command that loads BugPlug.
- `‘Load it via config file’`: You can also add a line to the configuration file of your application like this: `‘System.Plugins.iBugPlug = crystalspace.utilities.bugplug’`.
- `‘Load it all the time’`: If you want BugPlug to be in memory all the time for all Crystal Space applications then you can modify the system wide Crystal Space configuration file. On Windows this is usually `‘c:\Documents and Settings\<username>\Application Data\CrystalSpace\Global.cfg’`. On GNU/Linux this is usually `‘$HOME/.crystalspace/CrystalSpace.Global.cfg’`. To that file you add `‘System.Plugins.iBugPlug = crystalspace.utilities.bugplug’`.

This document was generated using texi2html 1.76.