##Configuration
The toolbar has a few configuration settings. Settings are passed in the component declaration like normal component configuration.
var $components = array(
'DebugKit.Toolbar' => array(/* array of settings */)
);
### panels
Using the panels key you can specify which panels you want to load, as well as the order in which you want the panels loaded.
var $components = array(
'DebugKit.Toolbar' => array('panels' => array('myCustomPanel', 'timer' => false))
);
Would add your custom panel `myCustomPanel` to the toolbar and exclude the default `Timer` panel. In addition to choosing which panels you want, you can pass options into the `__construct` of the panels. For example the built-in `History` panel uses the `history` key to set the number of historical requests to track.
var $components = array(
'DebugKit.Toolbar' => array('history' => 10)
);
Would load the `History` panel and set its history level to 10. The `panels` key is not passed to the Panel constructor.
### forceEnable
The `forceEnable` setting is new in DebugKit 1.1. It allows you to force the toolbar to display regardless of the value of `Configure::read('debug');`. This is useful when profiling an application with debug kit as you can enable the toolbar even when running the application in production mode.
### autoRun
autoRun is a new configuration setting for DebugKit 1.2. It allows you to control whether or not the toolbar is displayed automatically or whether you would like to use a query string parameter to enable it. Set this configuration key to false to use query string parameter toggling of the toolbar.
{{{
var $components = array(
'DebugKit.Toolbar' => array('autoRun' => false)
);
}}}
When visiting a page you can add `?debug=true` to the url and the toolbar will be visible. Otherwise it will stay hidden and not execute.
