A 2D Versus Shmup made in Unity
Doxygen documentation
+6349
-351
+1
.gitignore
+1
.gitignore
+1
-2
Assets/Editor.meta
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/LightTheme/doxygen.css.meta
+1
-2
Assets/Editor.meta
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/LightTheme/doxygen.css.meta
+1
-1
Assets/External Libraries/DanmakuUnity2D/Controllers/PlayerControllers/DanmakuPlayerCharacter.cs
Assets/External Libraries/DanmakuUnity2D/Controllers/PlayerControllers/DanmakuPlayer.cs
+1
-1
Assets/External Libraries/DanmakuUnity2D/Controllers/PlayerControllers/DanmakuPlayerCharacter.cs
Assets/External Libraries/DanmakuUnity2D/Controllers/PlayerControllers/DanmakuPlayer.cs
Assets/External Libraries/DanmakuUnity2D/Controllers/PlayerControllers/DanmakuPlayerCharacter.cs.meta
Assets/External Libraries/DanmakuUnity2D/Controllers/PlayerControllers/DanmakuPlayer.cs.meta
Assets/External Libraries/DanmakuUnity2D/Controllers/PlayerControllers/DanmakuPlayerCharacter.cs.meta
Assets/External Libraries/DanmakuUnity2D/Controllers/PlayerControllers/DanmakuPlayer.cs.meta
+2
-2
Assets/External Libraries/DanmakuUnity2D/Controllers/PlayerControllers/Player Hitboxes/PlayerDeathHitbox.cs
+2
-2
Assets/External Libraries/DanmakuUnity2D/Controllers/PlayerControllers/Player Hitboxes/PlayerDeathHitbox.cs
···
5
5
namespace Danmaku2D {
6
6
public class PlayerDeathHitbox : CachedObject {
7
7
8
-
private DanmakuPlayerCharacter player;
8
+
private DanmakuPlayer player;
9
9
10
10
void Start() {
11
-
player = GetComponentInParent<DanmakuPlayerCharacter> ();
11
+
player = GetComponentInParent<DanmakuPlayer> ();
12
12
if (player == null) {
13
13
Debug.LogError("PlayerDeathHitbox should be on a child object of a GameObject with an Avatar sublcass script");
14
14
}
+2
-2
Assets/External Libraries/DanmakuUnity2D/Controllers/PlayerControllers/Player Hitboxes/PlayerGrazeHitbox.cs
+2
-2
Assets/External Libraries/DanmakuUnity2D/Controllers/PlayerControllers/Player Hitboxes/PlayerGrazeHitbox.cs
···
5
5
namespace Danmaku2D {
6
6
public class PlayerGrazeHitbox : MonoBehaviour {
7
7
8
-
private DanmakuPlayerCharacter player;
8
+
private DanmakuPlayer player;
9
9
10
10
void Start() {
11
-
player = GetComponentInParent<DanmakuPlayerCharacter> ();
11
+
player = GetComponentInParent<DanmakuPlayer> ();
12
12
if (player == null) {
13
13
Debug.LogError("PlayerGrazeHitbox should be on a child object of a GameObject with an Avatar sublcass script");
14
14
}
+2
-2
Assets/External Libraries/DanmakuUnity2D/Controllers/PlayerControllers/PlayerAgent.cs
+2
-2
Assets/External Libraries/DanmakuUnity2D/Controllers/PlayerControllers/PlayerAgent.cs
+22
-20
Assets/External Libraries/DanmakuUnity2D/Controllers/Projectile Cotnrollers/ColorFadeProjectile.cs
+22
-20
Assets/External Libraries/DanmakuUnity2D/Controllers/Projectile Cotnrollers/ColorFadeProjectile.cs
···
1
1
using UnityEngine;
2
2
using System.Collections;
3
-
using Danmaku2D;
4
3
5
-
public class ColorFadeProjectile : ProjectileControlBehavior {
4
+
namespace Danmaku2D.ProjectileControllers {
6
5
7
-
[SerializeField]
8
-
private Color endColor;
6
+
public class ColorFadeProjectile : ProjectileControlBehavior {
9
7
10
-
[SerializeField]
11
-
private float startTime;
8
+
[SerializeField]
9
+
private Color endColor;
12
10
13
-
[SerializeField]
14
-
private float endTime;
11
+
[SerializeField]
12
+
private float startTime;
15
13
16
-
public override Vector2 UpdateProjectile (Projectile projectile, float dt) {
17
-
float bulletTime = projectile.Time;
18
-
Color startColor = SpriteRenderer.color;
19
-
if (bulletTime < startTime)
20
-
projectile.Color = startColor;
21
-
else if (bulletTime > endTime)
22
-
projectile.Color = endColor;
23
-
else
24
-
projectile.Color = Color.Lerp (startColor, endColor, (bulletTime - startTime) / (endTime - startTime));
25
-
return Vector2.zero;
26
-
}
14
+
[SerializeField]
15
+
private float endTime;
16
+
17
+
public override Vector2 UpdateProjectile (Projectile projectile, float dt) {
18
+
float bulletTime = projectile.Time;
19
+
Color startColor = SpriteRenderer.color;
20
+
if (bulletTime < startTime)
21
+
projectile.Color = startColor;
22
+
else if (bulletTime > endTime)
23
+
projectile.Color = endColor;
24
+
else
25
+
projectile.Color = Color.Lerp (startColor, endColor, (bulletTime - startTime) / (endTime - startTime));
26
+
return Vector2.zero;
27
+
}
27
28
28
-
}
29
+
}
30
+
}
+4
-4
Assets/External Libraries/DanmakuUnity2D/Core/DanmakuField.cs
+4
-4
Assets/External Libraries/DanmakuUnity2D/Core/DanmakuField.cs
···
13
13
14
14
public abstract DanmakuField TargetField { get; }
15
15
16
-
private DanmakuPlayerCharacter player;
17
-
public DanmakuPlayerCharacter Player {
16
+
private DanmakuPlayer player;
17
+
public DanmakuPlayer Player {
18
18
get {
19
19
return player;
20
20
}
···
155
155
/// </summary>
156
156
/// <param name="character">Character prefab, defines character behavior and attack patterns.</param>
157
157
/// <param name="controller">Controller for the player, allows for a user to manually control it or let an AI take over.</param>
158
-
public DanmakuPlayerCharacter SpawnPlayer(DanmakuPlayerCharacter playerCharacter, CoordinateSystem coordSys = CoordinateSystem.View) {
158
+
public DanmakuPlayer SpawnPlayer(DanmakuPlayer playerCharacter, CoordinateSystem coordSys = CoordinateSystem.View) {
159
159
Vector3 spawnPos = WorldPoint((Vector3)playerSpawnLocation, coordSys);
160
-
player = (DanmakuPlayerCharacter) Instantiate(playerCharacter, spawnPos, Quaternion.identity);
160
+
player = (DanmakuPlayer) Instantiate(playerCharacter, spawnPos, Quaternion.identity);
161
161
if(player != null) {
162
162
player.Reset (5);
163
163
player.Transform.parent = Transform;
+1
Assets/External Libraries/DanmakuUnity2D/Core/Projectile.cs
+1
Assets/External Libraries/DanmakuUnity2D/Core/Projectile.cs
+1
Assets/External Libraries/DanmakuUnity2D/Core/ProjectileManager.cs
+1
Assets/External Libraries/DanmakuUnity2D/Core/ProjectileManager.cs
+76
-75
Assets/External Libraries/DanmakuUnity2D/Editor/DanmakuAssets.cs
+76
-75
Assets/External Libraries/DanmakuUnity2D/Editor/DanmakuAssets.cs
···
1
1
using UnityEngine;
2
2
using UnityEditor;
3
3
using UnityUtilLib;
4
-
using Danmaku2D;
5
4
using Danmaku2D.Phantasmagoria;
6
5
using System.IO;
7
6
8
-
public class DanmakuAssets {
7
+
namespace Danmaku2D.Editor {
9
8
10
-
[MenuItem("Assets/Create/Danmaku 2D/Projectile Prefab", false, 51)]
11
-
public static void AddProjectilePrefab() {
12
-
GameObject temp = new GameObject ("Projectile Prefab");
13
-
temp.AddComponent<SpriteRenderer> ();
14
-
temp.AddComponent<CircleCollider2D> ();
15
-
temp.AddComponent<ProjectilePrefab> ();
16
-
PrefabUtility.CreatePrefab ("Assets/Projectile Prefab.prefab", temp);
17
-
Object.DestroyImmediate (temp);
18
-
}
9
+
public static class DanmakuAssets {
19
10
20
-
[MenuItem("GameObject/Create/Danmaku 2D/Phantasmagoria/Game Controller")]
21
-
public static void CreatePhantasmagoriaGame() {
22
-
GameObject temp = new GameObject ("Game Controller");
23
-
temp.AddComponent<StaticGameObject> ();
24
-
PhantasmagoriaGameController pcg = temp.AddComponent<PhantasmagoriaGameController> ();
25
-
PhantasmagoriaField playerField1 = CreatePhantasmagoriaField ();
26
-
PhantasmagoriaField playerField2 = CreatePhantasmagoriaField ();
27
-
playerField1.gameObject.name = "Player 1 " + playerField1.gameObject.name;
28
-
playerField2.gameObject.name = "Player 2 " + playerField2.gameObject.name;
29
-
SerializedObject pcgS = new SerializedObject (pcg);
30
-
pcgS.FindProperty ("player1.field").objectReferenceValue = playerField1;
31
-
pcgS.FindProperty ("player2.field").objectReferenceValue = playerField2;
32
-
pcgS.ApplyModifiedProperties ();
33
-
playerField1.transform.position = new Vector3 (-100f, 0f, 0f);
34
-
playerField2.transform.position = new Vector3 (100f, 0f, 0f);
35
-
temp.AddComponent<TestSpawnPlayer> ();
36
-
temp.AddComponent<AudioListener> ();
37
-
temp.AddComponent<AudioSource>();
38
-
temp.AddComponent<MusicManager> ();
39
-
}
11
+
[MenuItem("Assets/Create/Danmaku 2D/Projectile Prefab", false, 51)]
12
+
public static void AddProjectilePrefab() {
13
+
GameObject temp = new GameObject ("Projectile Prefab");
14
+
temp.AddComponent<SpriteRenderer> ();
15
+
temp.AddComponent<CircleCollider2D> ();
16
+
temp.AddComponent<ProjectilePrefab> ();
17
+
PrefabUtility.CreatePrefab ("Assets/Projectile Prefab.prefab", temp);
18
+
Object.DestroyImmediate (temp);
19
+
}
20
+
21
+
[MenuItem("GameObject/Create/Danmaku 2D/Phantasmagoria/Game Controller")]
22
+
public static void CreatePhantasmagoriaGame() {
23
+
GameObject temp = new GameObject ("Game Controller");
24
+
temp.AddComponent<StaticGameObject> ();
25
+
PhantasmagoriaGameController pcg = temp.AddComponent<PhantasmagoriaGameController> ();
26
+
PhantasmagoriaField playerField1 = CreatePhantasmagoriaField ();
27
+
PhantasmagoriaField playerField2 = CreatePhantasmagoriaField ();
28
+
playerField1.gameObject.name = "Player 1 " + playerField1.gameObject.name;
29
+
playerField2.gameObject.name = "Player 2 " + playerField2.gameObject.name;
30
+
SerializedObject pcgS = new SerializedObject (pcg);
31
+
pcgS.FindProperty ("player1.field").objectReferenceValue = playerField1;
32
+
pcgS.FindProperty ("player2.field").objectReferenceValue = playerField2;
33
+
pcgS.ApplyModifiedProperties ();
34
+
playerField1.transform.position = new Vector3 (-100f, 0f, 0f);
35
+
playerField2.transform.position = new Vector3 (100f, 0f, 0f);
36
+
temp.AddComponent<TestSpawnPlayer> ();
37
+
temp.AddComponent<AudioListener> ();
38
+
temp.AddComponent<AudioSource>();
39
+
temp.AddComponent<MusicManager> ();
40
+
}
41
+
42
+
[MenuItem("GameObject/Create/Danmaku 2D/Phantasmagoria/Field")]
43
+
public static PhantasmagoriaField CreatePhantasmagoriaField() {
44
+
GameObject temp = new GameObject ("Field");
45
+
PhantasmagoriaField field = temp.AddComponent<PhantasmagoriaField> ();
46
+
GameObject background = GameObject.CreatePrimitive (PrimitiveType.Quad);
47
+
background.name = "Background";
48
+
background.transform.parent = field.transform;
49
+
background.transform.localPosition = new Vector3 (0f, 0f, field.GamePlaneDistance);
50
+
Object.DestroyImmediate(background.GetComponent<MeshCollider> ());
51
+
background.transform.localScale = new Vector3 (48.125f, 48.125f, 1f);
52
+
GameObject cam = new GameObject ("Camera");
53
+
cam.transform.parent = temp.transform;
54
+
cam.transform.localScale = new Vector3 (0f, 0f, -field.GamePlaneDistance);
55
+
Camera camera = cam.AddComponent<Camera> ();
56
+
SerializedObject camS = new SerializedObject (field);
57
+
camS.FindProperty ("fieldCamera").objectReferenceValue = camera;
58
+
camS.ApplyModifiedProperties ();
59
+
camera.orthographic = true;
60
+
camera.orthographicSize = 20;
61
+
camera.farClipPlane = 2 * field.GamePlaneDistance;
62
+
return field;
63
+
}
40
64
41
-
[MenuItem("GameObject/Create/Danmaku 2D/Phantasmagoria/Field")]
42
-
public static PhantasmagoriaField CreatePhantasmagoriaField() {
43
-
GameObject temp = new GameObject ("Field");
44
-
PhantasmagoriaField field = temp.AddComponent<PhantasmagoriaField> ();
45
-
GameObject background = GameObject.CreatePrimitive (PrimitiveType.Quad);
46
-
background.name = "Background";
47
-
background.transform.parent = field.transform;
48
-
background.transform.localPosition = new Vector3 (0f, 0f, field.GamePlaneDistance);
49
-
Object.DestroyImmediate(background.GetComponent<MeshCollider> ());
50
-
background.transform.localScale = new Vector3 (48.125f, 48.125f, 1f);
51
-
GameObject cam = new GameObject ("Camera");
52
-
cam.transform.parent = temp.transform;
53
-
cam.transform.localScale = new Vector3 (0f, 0f, -field.GamePlaneDistance);
54
-
Camera camera = cam.AddComponent<Camera> ();
55
-
SerializedObject camS = new SerializedObject (field);
56
-
camS.FindProperty ("fieldCamera").objectReferenceValue = camera;
57
-
camS.ApplyModifiedProperties ();
58
-
camera.orthographic = true;
59
-
camera.orthographicSize = 20;
60
-
camera.farClipPlane = 2 * field.GamePlaneDistance;
61
-
return field;
65
+
// [MenuItem("Assets/Create/Danmaku 2D/Custom Attack Pattern")]
66
+
// public static void CreateAttackPattern() {
67
+
// string text = "using UnityEngine;\nusing System.Collections;\nusing Danmaku2D;\n" +
68
+
// "\npublic class NewAttackPattern : AttackPattern {\n" +
69
+
// "\t//Used to determine when the attack pattern is finished and can terminate" +
70
+
// "\n\tprotected override bool IsFinished {\n" +
71
+
// "\t\tget {\n" +
72
+
// "\t\t\treturn false;\n" +
73
+
// "\t\t}\n" +
74
+
// "\t}\n" +
75
+
// "\n\t//The main loop of the attack pattern, executed every frame" +
76
+
// "\tprotected override void MainLoop() {\n" +
77
+
// "\n\n\t}\n" +
78
+
// "}";
79
+
// CreateScript (text, "NewAttackPattern");
80
+
// }
81
+
//
82
+
// private static void CreateScript(string scriptText, string name) {
83
+
// File.WriteAllText (Application.dataPath + "/ " + name + ".cs", scriptText);
84
+
// AssetDatabase.ImportAsset ("Assets/" + name + ".cs");
85
+
// }
62
86
}
63
-
64
-
// [MenuItem("Assets/Create/Danmaku 2D/Custom Attack Pattern")]
65
-
// public static void CreateAttackPattern() {
66
-
// string text = "using UnityEngine;\nusing System.Collections;\nusing Danmaku2D;\n" +
67
-
// "\npublic class NewAttackPattern : AttackPattern {\n" +
68
-
// "\t//Used to determine when the attack pattern is finished and can terminate" +
69
-
// "\n\tprotected override bool IsFinished {\n" +
70
-
// "\t\tget {\n" +
71
-
// "\t\t\treturn false;\n" +
72
-
// "\t\t}\n" +
73
-
// "\t}\n" +
74
-
// "\n\t//The main loop of the attack pattern, executed every frame" +
75
-
// "\tprotected override void MainLoop() {\n" +
76
-
// "\n\n\t}\n" +
77
-
// "}";
78
-
// CreateScript (text, "NewAttackPattern");
79
-
// }
80
-
//
81
-
// private static void CreateScript(string scriptText, string name) {
82
-
// File.WriteAllText (Application.dataPath + "/ " + name + ".cs", scriptText);
83
-
// AssetDatabase.ImportAsset ("Assets/" + name + ".cs");
84
-
// }
85
87
}
86
-
+31
Assets/External Libraries/DanmakuUnity2D/Editor/ProjectileManagerEditor.cs
+31
Assets/External Libraries/DanmakuUnity2D/Editor/ProjectileManagerEditor.cs
···
1
+
using UnityEngine;
2
+
using System.Collections;
3
+
using UnityEditor;
4
+
using Danmaku2D;
5
+
6
+
namespace Danmaku2D.Editor {
7
+
8
+
[CustomEditor(typeof(ProjectileManager))]
9
+
public class ProjectileManagerEditor : UnityEditor.Editor {
10
+
11
+
void OnSceneGUI() {
12
+
ProjectileManager pool = target as ProjectileManager;
13
+
GUISkin skin = GUI.skin;
14
+
Handles.BeginGUI ();
15
+
GUILayout.BeginArea (new Rect(0,0,150,60), skin.box);
16
+
GUILayout.BeginVertical ();
17
+
GUILayout.BeginHorizontal ();
18
+
GUILayout.FlexibleSpace ();
19
+
GUILayout.Label ("Projectile Pool");
20
+
GUILayout.FlexibleSpace ();
21
+
GUILayout.EndHorizontal();
22
+
GUILayout.Label ("Total Count: " + pool.TotalCount);
23
+
GUILayout.Label ("Active Count: " + pool.ActiveCount);
24
+
GUILayout.EndVertical ();
25
+
GUILayout.EndArea ();
26
+
if(GUI.changed)
27
+
EditorUtility.SetDirty(target);
28
+
Handles.EndGUI ();
29
+
}
30
+
}
31
+
}
+12
Assets/External Libraries/DanmakuUnity2D/Editor/ProjectileManagerEditor.cs.meta
+12
Assets/External Libraries/DanmakuUnity2D/Editor/ProjectileManagerEditor.cs.meta
···
1
+
fileFormatVersion: 2
2
+
guid: cbaa688195770fc47ab549d0928be3a4
3
+
timeCreated: 1426131832
4
+
licenseType: Free
5
+
MonoImporter:
6
+
serializedVersion: 2
7
+
defaultReferences: []
8
+
executionOrder: 0
9
+
icon: {instanceID: 0}
10
+
userData:
11
+
assetBundleName:
12
+
assetBundleVariant:
-28
Assets/External Libraries/DanmakuUnity2D/Editor/ProjectilePoolEditor.cs
-28
Assets/External Libraries/DanmakuUnity2D/Editor/ProjectilePoolEditor.cs
···
1
-
using UnityEngine;
2
-
using System.Collections;
3
-
using UnityEditor;
4
-
using Danmaku2D;
5
-
6
-
[CustomEditor(typeof(ProjectileManager))]
7
-
public class ProjectilePoolEditor : Editor {
8
-
9
-
void OnSceneGUI() {
10
-
ProjectileManager pool = target as ProjectileManager;
11
-
GUISkin skin = GUI.skin;
12
-
Handles.BeginGUI ();
13
-
GUILayout.BeginArea (new Rect(0,0,150,60), skin.box);
14
-
GUILayout.BeginVertical ();
15
-
GUILayout.BeginHorizontal ();
16
-
GUILayout.FlexibleSpace ();
17
-
GUILayout.Label ("Projectile Pool");
18
-
GUILayout.FlexibleSpace ();
19
-
GUILayout.EndHorizontal();
20
-
GUILayout.Label ("Total Count: " + pool.TotalCount);
21
-
GUILayout.Label ("Active Count: " + pool.ActiveCount);
22
-
GUILayout.EndVertical ();
23
-
GUILayout.EndArea ();
24
-
if(GUI.changed)
25
-
EditorUtility.SetDirty(target);
26
-
Handles.EndGUI ();
27
-
}
28
-
}
-8
Assets/External Libraries/DanmakuUnity2D/Editor/ProjectilePoolEditor.cs.meta
-8
Assets/External Libraries/DanmakuUnity2D/Editor/ProjectilePoolEditor.cs.meta
+20
-17
Assets/External Libraries/DanmakuUnity2D/Editor/ProjectilePrefabEditor.cs
+20
-17
Assets/External Libraries/DanmakuUnity2D/Editor/ProjectilePrefabEditor.cs
···
3
3
using System.Collections;
4
4
using Danmaku2D;
5
5
6
-
[CustomEditor(typeof(ProjectilePrefab))]
7
-
public class ProjectilePrefabEditor : Editor {
6
+
namespace Danmaku2D.Editor {
8
7
9
-
public override void OnInspectorGUI () {
10
-
base.OnInspectorGUI ();
11
-
ProjectilePrefab prefab = target as ProjectilePrefab;
12
-
if(GUILayout.Button("Reinitialize")) {
13
-
SerializedProperty collider = serializedObject.FindProperty("circleCollider");
14
-
SerializedProperty renderer = serializedObject.FindProperty("spriteRenderer");
15
-
SerializedProperty controllers = serializedObject.FindProperty("extraControllers");
16
-
collider.objectReferenceValue = prefab.GetComponent<CircleCollider2D>();
17
-
renderer.objectReferenceValue = prefab.GetComponent<SpriteRenderer>();
18
-
ProjectileControlBehavior[] controllerScripts = prefab.GetComponents<ProjectileControlBehavior>();
19
-
controllers.arraySize = controllerScripts.Length;
20
-
for(int i = 0; i < controllerScripts.Length; i++) {
21
-
controllers.GetArrayElementAtIndex(i).objectReferenceValue = controllerScripts[i];
8
+
[CustomEditor(typeof(ProjectilePrefab))]
9
+
public class ProjectilePrefabEditor : UnityEditor.Editor {
10
+
11
+
public override void OnInspectorGUI () {
12
+
base.OnInspectorGUI ();
13
+
ProjectilePrefab prefab = target as ProjectilePrefab;
14
+
if(GUILayout.Button("Reinitialize")) {
15
+
SerializedProperty collider = serializedObject.FindProperty("circleCollider");
16
+
SerializedProperty renderer = serializedObject.FindProperty("spriteRenderer");
17
+
SerializedProperty controllers = serializedObject.FindProperty("extraControllers");
18
+
collider.objectReferenceValue = prefab.GetComponent<CircleCollider2D>();
19
+
renderer.objectReferenceValue = prefab.GetComponent<SpriteRenderer>();
20
+
ProjectileControlBehavior[] controllerScripts = prefab.GetComponents<ProjectileControlBehavior>();
21
+
controllers.arraySize = controllerScripts.Length;
22
+
for(int i = 0; i < controllerScripts.Length; i++) {
23
+
controllers.GetArrayElementAtIndex(i).objectReferenceValue = controllerScripts[i];
24
+
}
25
+
serializedObject.ApplyModifiedProperties();
22
26
}
23
-
serializedObject.ApplyModifiedProperties();
24
27
}
25
28
}
26
-
}
29
+
}
-44
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/ChargeBarGUI.cs
-44
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/ChargeBarGUI.cs
···
1
-
using UnityEngine;
2
-
using System.Collections;
3
-
using Danmaku2D.Phantasmagoria;
4
-
using UnityUtilLib;
5
-
6
-
public class ChargeBarGUI : PausableGameObject {
7
-
8
-
[SerializeField]
9
-
private PhantasmagoriaField field;
10
-
private PhantasmagoriaPlayableCharacter player;
11
-
12
-
[SerializeField]
13
-
private Transform chargeCapacity;
14
-
15
-
[SerializeField]
16
-
private Transform chargeLevel;
17
-
18
-
[SerializeField]
19
-
private GameObject indicator;
20
-
21
-
void Start() {
22
-
player = (PhantasmagoriaPlayableCharacter)field.Player;
23
-
int maxIndicatorLevel = player.MaxChargeLevel - 1;
24
-
float inc = 0.5f / (float)player.MaxChargeLevel;
25
-
Vector3 ls = indicator.transform.localScale;
26
-
for(int i = -maxIndicatorLevel; i <= maxIndicatorLevel; i++) {
27
-
if(i != 0) {
28
-
GameObject newIndicator = (GameObject)Instantiate(indicator);
29
-
newIndicator.transform.parent = transform;
30
-
newIndicator.transform.localPosition = Vector3.right * inc * i + Vector3.forward * indicator.transform.localPosition.z;
31
-
newIndicator.transform.localScale = new Vector3(ls.x / 2f, ls.y, ls.z);
32
-
}
33
-
}
34
-
}
35
-
36
-
public override void NormalUpdate () {
37
-
Vector3 capacityScale = chargeCapacity.localScale;
38
-
Vector3 levelScale = chargeCapacity.localScale;
39
-
capacityScale.x = player.CurrentChargeCapacity / (float)player.MaxChargeLevel;
40
-
levelScale.x = player.CurrentChargeLevel / (float)player.MaxChargeLevel;
41
-
chargeCapacity.localScale = capacityScale;
42
-
chargeLevel.localScale = levelScale;
43
-
}
44
-
}
-8
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/ChargeBarGUI.cs.meta
-8
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/ChargeBarGUI.cs.meta
+9
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/GUI.meta
+9
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/GUI.meta
+47
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/GUI/ChargeBarGUI.cs
+47
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/GUI/ChargeBarGUI.cs
···
1
+
using UnityEngine;
2
+
using System.Collections;
3
+
using Danmaku2D.Phantasmagoria;
4
+
using UnityUtilLib;
5
+
6
+
namespace Danmaku2D.Phantasmagoria.GUI {
7
+
8
+
public class ChargeBarGUI : PausableGameObject {
9
+
10
+
[SerializeField]
11
+
private PhantasmagoriaField field;
12
+
private PhantasmagoriaPlayableCharacter player;
13
+
14
+
[SerializeField]
15
+
private Transform chargeCapacity;
16
+
17
+
[SerializeField]
18
+
private Transform chargeLevel;
19
+
20
+
[SerializeField]
21
+
private GameObject indicator;
22
+
23
+
void Start() {
24
+
player = (PhantasmagoriaPlayableCharacter)field.Player;
25
+
int maxIndicatorLevel = player.MaxChargeLevel - 1;
26
+
float inc = 0.5f / (float)player.MaxChargeLevel;
27
+
Vector3 ls = indicator.transform.localScale;
28
+
for(int i = -maxIndicatorLevel; i <= maxIndicatorLevel; i++) {
29
+
if(i != 0) {
30
+
GameObject newIndicator = (GameObject)Instantiate(indicator);
31
+
newIndicator.transform.parent = transform;
32
+
newIndicator.transform.localPosition = Vector3.right * inc * i + Vector3.forward * indicator.transform.localPosition.z;
33
+
newIndicator.transform.localScale = new Vector3(ls.x / 2f, ls.y, ls.z);
34
+
}
35
+
}
36
+
}
37
+
38
+
public override void NormalUpdate () {
39
+
Vector3 capacityScale = chargeCapacity.localScale;
40
+
Vector3 levelScale = chargeCapacity.localScale;
41
+
capacityScale.x = player.CurrentChargeCapacity / (float)player.MaxChargeLevel;
42
+
levelScale.x = player.CurrentChargeLevel / (float)player.MaxChargeLevel;
43
+
chargeCapacity.localScale = capacityScale;
44
+
chargeLevel.localScale = levelScale;
45
+
}
46
+
}
47
+
}
+12
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/GUI/ChargeBarGUI.cs.meta
+12
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/GUI/ChargeBarGUI.cs.meta
···
1
+
fileFormatVersion: 2
2
+
guid: 1caa3cd050dcf534dbf0568021c0c20d
3
+
timeCreated: 1426132678
4
+
licenseType: Free
5
+
MonoImporter:
6
+
serializedVersion: 2
7
+
defaultReferences: []
8
+
executionOrder: 0
9
+
icon: {instanceID: 0}
10
+
userData:
11
+
assetBundleName:
12
+
assetBundleVariant:
+24
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/GUI/PlayerLifeIndicator.cs
+24
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/GUI/PlayerLifeIndicator.cs
···
1
+
using UnityEngine;
2
+
using System.Collections;
3
+
using UnityUtilLib.GUI;
4
+
using Danmaku2D.Phantasmagoria;
5
+
6
+
namespace Danmaku2D.Phantasmagoria.GUI {
7
+
8
+
public class PlayerLifeIndicator : MultiObjectValueIndicator {
9
+
10
+
private PhantasmagoriaGameController gameControl;
11
+
12
+
void Awake() {
13
+
gameControl = (PhantasmagoriaGameController)GameController;
14
+
}
15
+
16
+
protected override int GetMaxValue () {
17
+
return gameControl.MaximumLives;
18
+
}
19
+
20
+
protected override int GetValue () {
21
+
return ((player) ? gameControl.player1 : gameControl.player2).Field.Player.LivesRemaining;
22
+
}
23
+
}
24
+
}
+22
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/GUI/PlayerScoreIndicator.cs
+22
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/GUI/PlayerScoreIndicator.cs
···
1
+
using UnityEngine;
2
+
using System.Collections;
3
+
using UnityUtilLib.GUI;
4
+
5
+
namespace Danmaku2D.Phantasmagoria.GUI {
6
+
public class PlayerScoreIndicator : MultiObjectValueIndicator {
7
+
8
+
private PhantasmagoriaGameController gameControl;
9
+
10
+
void Awake() {
11
+
gameControl = (PhantasmagoriaGameController)GameController;
12
+
}
13
+
14
+
protected override int GetMaxValue () {
15
+
return gameControl.WinningScore;
16
+
}
17
+
18
+
protected override int GetValue() {
19
+
return ((player) ? gameControl.player1 : gameControl.player2).score;
20
+
}
21
+
}
22
+
}
+12
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/GUI/PlayerScoreIndicator.cs.meta
+12
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/GUI/PlayerScoreIndicator.cs.meta
···
1
+
fileFormatVersion: 2
2
+
guid: 9fd7c15c8bef28b4cbe718ddf624796c
3
+
timeCreated: 1426132678
4
+
licenseType: Free
5
+
MonoImporter:
6
+
serializedVersion: 2
7
+
defaultReferences: []
8
+
executionOrder: 0
9
+
icon: {instanceID: 0}
10
+
userData:
11
+
assetBundleName:
12
+
assetBundleVariant:
+49
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/GUI/RoundTimer.cs
+49
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/GUI/RoundTimer.cs
···
1
+
using UnityEngine;
2
+
using System.Collections;
3
+
using UnityUtilLib;
4
+
5
+
namespace Danmaku2D.Phantasmagoria.GUI {
6
+
7
+
[RequireComponent(typeof(GUIText))]
8
+
public class RoundTimer : MonoBehaviour {
9
+
10
+
[SerializeField]
11
+
private PhantasmagoriaGameController gameController;
12
+
13
+
[SerializeField]
14
+
private Color flashColor;
15
+
16
+
[SerializeField]
17
+
private FrameCounter flashInterval;
18
+
19
+
[SerializeField]
20
+
private float flashThreshold;
21
+
22
+
private Color normalColor;
23
+
private bool flashState;
24
+
private GUIText label;
25
+
26
+
void Start() {
27
+
label = GetComponent<GUIText>();
28
+
normalColor = label.color;
29
+
flashState = false;
30
+
}
31
+
32
+
void Update() {
33
+
int timeSec = Mathf.FloorToInt (gameController.RemainingRoundTime);
34
+
int seconds = timeSec % 60;
35
+
int minutes = timeSec / 60;
36
+
label.text = minutes.ToString ("D2") + ":" + seconds.ToString ("D2");;
37
+
if (timeSec < flashThreshold) {
38
+
if(flashInterval.Tick()) {
39
+
label.color = (flashState) ? flashColor : normalColor;
40
+
flashState = !flashState;
41
+
}
42
+
} else {
43
+
label.color = normalColor;
44
+
flashState = false;
45
+
flashInterval.ForceReady();
46
+
}
47
+
}
48
+
}
49
+
}
+1
-1
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/PhantasmagoriaPlayableCharacter.cs
+1
-1
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/PhantasmagoriaPlayableCharacter.cs
+13
-11
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/TestSpawnPlayer.cs
+13
-11
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/TestSpawnPlayer.cs
···
1
1
using UnityEngine;
2
2
using UnityUtilLib;
3
3
using System.Collections;
4
-
using Danmaku2D.Phantasmagoria;
5
4
6
-
[RequireComponent(typeof(PhantasmagoriaGameController))]
7
-
public class TestSpawnPlayer : TestScript {
8
-
public PhantasmagoriaPlayableCharacter character1;
9
-
public PhantasmagoriaPlayableCharacter character2;
5
+
namespace Danmaku2D.Phantasmagoria {
10
6
11
-
void Start() {
12
-
PhantasmagoriaGameController controller = GetComponent<PhantasmagoriaGameController> ();
13
-
PhantasmagoriaPlayableCharacter player1 = (PhantasmagoriaPlayableCharacter) controller.player1.Field.SpawnPlayer (character1);
14
-
PhantasmagoriaPlayableCharacter player2 = (PhantasmagoriaPlayableCharacter) controller.player2.Field.SpawnPlayer (character2);
15
-
player1.Initialize(new PhantasmagoriaControlledAgent(1));
16
-
player2.Initialize(new PhantasmagoriaControlledAgent(2));
7
+
[RequireComponent(typeof(PhantasmagoriaGameController))]
8
+
public class TestSpawnPlayer : TestScript {
9
+
public PhantasmagoriaPlayableCharacter character1;
10
+
public PhantasmagoriaPlayableCharacter character2;
11
+
12
+
void Start() {
13
+
PhantasmagoriaGameController controller = GetComponent<PhantasmagoriaGameController> ();
14
+
PhantasmagoriaPlayableCharacter player1 = (PhantasmagoriaPlayableCharacter) controller.player1.Field.SpawnPlayer (character1);
15
+
PhantasmagoriaPlayableCharacter player2 = (PhantasmagoriaPlayableCharacter) controller.player2.Field.SpawnPlayer (character2);
16
+
player1.Initialize(new PhantasmagoriaControlledAgent(1));
17
+
player2.Initialize(new PhantasmagoriaControlledAgent(2));
18
+
}
17
19
}
18
20
}
+2
-2
Assets/External Libraries/DanmakuUnity2D/PlayerMovementLimit.cs
+2
-2
Assets/External Libraries/DanmakuUnity2D/PlayerMovementLimit.cs
···
13
13
14
14
void OnTriggerEnter2D(Collider2D other) {
15
15
if(other.CompareTag(tagCheck)) {
16
-
DanmakuPlayerCharacter player = other.gameObject.GetComponent<DanmakuPlayerCharacter> ();
16
+
DanmakuPlayer player = other.gameObject.GetComponent<DanmakuPlayer> ();
17
17
if(player != null) {
18
18
player.ForbidMovement(lockedMovementVector);
19
19
}
···
22
22
23
23
void OnTriggerExit2D(Collider2D other) {
24
24
if(other.CompareTag(tagCheck)) {
25
-
DanmakuPlayerCharacter player = other.gameObject.GetComponent<DanmakuPlayerCharacter> ();
25
+
DanmakuPlayer player = other.gameObject.GetComponent<DanmakuPlayer> ();
26
26
if(player != null) {
27
27
player.AllowMovement(lockedMovementVector);
28
28
}
+9
Assets/External Libraries/UnityUtilLib/Editor/Doxygen.meta
+9
Assets/External Libraries/UnityUtilLib/Editor/Doxygen.meta
+732
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/DoxygenWindow.cs
+732
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/DoxygenWindow.cs
···
1
+
/*
2
+
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
3
+
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
4
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
5
+
*/
6
+
using UnityEngine;
7
+
using UnityEditor;
8
+
using System;
9
+
using System.Collections;
10
+
using System.Collections.Generic;
11
+
using System.Diagnostics;
12
+
using System.IO;
13
+
using System.Threading;
14
+
using System.Text;
15
+
using System.Text.RegularExpressions;
16
+
17
+
/// <summary>
18
+
/// <para>A small data structure class hold values for making Doxygen config files </para>
19
+
/// </summary>
20
+
public class DoxygenConfig
21
+
{
22
+
public string Project = PlayerSettings.productName;
23
+
public string Synopsis = "";
24
+
public string Version = "";
25
+
public string ScriptsDirectory = Application.dataPath;
26
+
public string DocDirectory = Application.dataPath.Replace("Assets", "Docs");
27
+
public string PathtoDoxygen = "";
28
+
29
+
}
30
+
31
+
/// <summary>
32
+
/// <para> A Editor Plugin for automatic doc generation through Doxygen</para>
33
+
/// <para> Author: Jacob Pennock (http://Jacobpennock.com)</para>
34
+
/// <para> Version: 1.0</para>
35
+
/// </summary>
36
+
public class DoxygenWindow : EditorWindow
37
+
{
38
+
public static DoxygenWindow Instance;
39
+
public enum WindowModes{Generate,Configuration,About}
40
+
public string UnityProjectID = PlayerSettings.productName+":";
41
+
public string AssestsFolder = Application.dataPath;
42
+
public string[] Themes = new string[3] {"Default", "Dark and Colorful", "Light and Clean"};
43
+
public int SelectedTheme = 1;
44
+
WindowModes DisplayMode = WindowModes.Generate;
45
+
static DoxygenConfig Config;
46
+
static bool DoxyFileExists = false;
47
+
StringReader reader;
48
+
TextAsset basefile;
49
+
float DoxyfileCreateProgress = -1.0f;
50
+
float DoxyoutputProgress = -1.0f;
51
+
string CreateProgressString = "Creating Doxyfile..";
52
+
public string BaseFileString = null;
53
+
public string DoxygenOutputString = null;
54
+
public string CurentOutput = null;
55
+
DoxyThreadSafeOutput DoxygenOutput = null;
56
+
List<string> DoxygenLog = null;
57
+
bool ViewLog = false;
58
+
Vector2 scroll;
59
+
bool DocsGenerated = false;
60
+
61
+
[MenuItem( "Window/Documentation with Doxygen" )]
62
+
public static void Init()
63
+
{
64
+
Instance = (DoxygenWindow)EditorWindow.GetWindow( typeof( DoxygenWindow ), false, "Documentation" );
65
+
Instance.minSize = new Vector2( 420, 245 );
66
+
Instance.maxSize = new Vector2( 420, 720 );
67
+
68
+
}
69
+
70
+
void OnEnable()
71
+
{
72
+
LoadConfig();
73
+
DoxyoutputProgress = 0;
74
+
}
75
+
76
+
void OnDisable()
77
+
{
78
+
DoxyoutputProgress = 0;
79
+
DoxygenLog = null;
80
+
}
81
+
82
+
void OnGUI()
83
+
{
84
+
DisplayHeadingToolbar();
85
+
switch(DisplayMode)
86
+
{
87
+
case WindowModes.Generate:
88
+
GenerateGUI();
89
+
break;
90
+
91
+
case WindowModes.Configuration:
92
+
ConfigGUI();
93
+
break;
94
+
95
+
case WindowModes.About:
96
+
AboutGUI();
97
+
break;
98
+
}
99
+
}
100
+
101
+
void DisplayHeadingToolbar()
102
+
{
103
+
GUIStyle normalButton = new GUIStyle( EditorStyles.toolbarButton );
104
+
normalButton.fixedWidth = 140;
105
+
GUILayout.Space (5);
106
+
EditorGUILayout.BeginHorizontal( EditorStyles.toolbar );
107
+
{
108
+
if( GUILayout.Toggle( DisplayMode == WindowModes.Generate, "Generate Documentation", normalButton ) )
109
+
{
110
+
DoxyfileCreateProgress = -1;
111
+
DisplayMode = WindowModes.Generate;
112
+
}
113
+
if( GUILayout.Toggle( DisplayMode == WindowModes.Configuration, "Settings/Configuration", normalButton ) )
114
+
{
115
+
DisplayMode = WindowModes.Configuration;
116
+
}
117
+
if( GUILayout.Toggle( DisplayMode == WindowModes.About, "About", normalButton ) )
118
+
{
119
+
DoxyfileCreateProgress = -1;
120
+
DisplayMode = WindowModes.About;
121
+
}
122
+
}
123
+
EditorGUILayout.EndHorizontal();
124
+
}
125
+
126
+
void ConfigGUI()
127
+
{
128
+
GUILayout.Space (10);
129
+
if(Config.Project == "Enter your Project name (Required)" || Config.Project == "" || Config.PathtoDoxygen == "" )
130
+
GUI.enabled = false;
131
+
if(GUILayout.Button ("Save Configuration and Build new DoxyFile", GUILayout.Height(40)))
132
+
{
133
+
MakeNewDoxyFile(Config);
134
+
}
135
+
if(DoxyfileCreateProgress >= 0)
136
+
{
137
+
Rect r = EditorGUILayout.BeginVertical();
138
+
EditorGUI.ProgressBar(r, DoxyfileCreateProgress, CreateProgressString);
139
+
GUILayout.Space(16);
140
+
EditorGUILayout.EndVertical();
141
+
}
142
+
GUI.enabled = true;
143
+
144
+
GUILayout.Space (20);
145
+
GUILayout.Label("Set Path to Doxygen Install",EditorStyles.boldLabel);
146
+
GUILayout.Space (5);
147
+
EditorGUILayout.BeginHorizontal();
148
+
Config.PathtoDoxygen = EditorGUILayout.TextField("Doxygen.exe : ",Config.PathtoDoxygen);
149
+
if(GUILayout.Button ("...",EditorStyles.miniButtonRight, GUILayout.Width(22)))
150
+
Config.PathtoDoxygen = EditorUtility.OpenFilePanel ("Where is doxygen.exe installed?","", "");
151
+
EditorGUILayout.EndHorizontal();
152
+
153
+
154
+
GUILayout.Space (20);
155
+
GUILayout.Label("Provide some details about the project",EditorStyles.boldLabel);
156
+
GUILayout.Space (5);
157
+
Config.Project = EditorGUILayout.TextField("Project Name: ",Config.Project);
158
+
Config.Synopsis = EditorGUILayout.TextField("Project Brief: ",Config.Synopsis);
159
+
Config.Version = EditorGUILayout.TextField("Project Version: ",Config.Version);
160
+
161
+
GUILayout.Space (15);
162
+
GUILayout.Label("Select Theme",EditorStyles.boldLabel);
163
+
GUILayout.Space (5);
164
+
SelectedTheme = EditorGUILayout.Popup(SelectedTheme,Themes) ;
165
+
166
+
GUILayout.Space (20);
167
+
GUILayout.Label("Setup the Directories",EditorStyles.boldLabel);
168
+
GUILayout.Space (5);
169
+
EditorGUILayout.BeginHorizontal();
170
+
Config.ScriptsDirectory = EditorGUILayout.TextField("Scripts folder: ",Config.ScriptsDirectory);
171
+
if(GUILayout.Button ("...",EditorStyles.miniButtonRight, GUILayout.Width(22)))
172
+
Config.ScriptsDirectory = EditorUtility.OpenFolderPanel("Select your scripts folder", Config.ScriptsDirectory, "");
173
+
EditorGUILayout.EndHorizontal();
174
+
GUILayout.Space (5);
175
+
EditorGUILayout.BeginHorizontal();
176
+
Config.DocDirectory = EditorGUILayout.TextField("Output folder: ",Config.DocDirectory);
177
+
if(GUILayout.Button ("...",EditorStyles.miniButtonRight, GUILayout.Width(22)))
178
+
Config.DocDirectory = EditorUtility.OpenFolderPanel("Select your ouput Docs folder", Config.DocDirectory, "");
179
+
EditorGUILayout.EndHorizontal();
180
+
GUILayout.Space (5);
181
+
EditorGUILayout.BeginHorizontal();
182
+
GUILayout.Space (5);
183
+
GUILayout.Space (30);
184
+
GUILayout.Label("By default Doxygen will search through your whole Assets folder for C# script files to document. Then it will output the documentation it generates into a folder called \"Docs\" that is placed in your project folder next to the Assets folder. If you would like to set a specific script or output folder you can do so above. ",EditorStyles.wordWrappedMiniLabel);
185
+
GUILayout.Space (30);
186
+
EditorGUILayout.EndHorizontal();
187
+
}
188
+
189
+
void AboutGUI()
190
+
{
191
+
GUIStyle CenterLable = new GUIStyle(EditorStyles.largeLabel);
192
+
GUIStyle littletext = new GUIStyle(EditorStyles.miniLabel) ;
193
+
CenterLable.alignment = TextAnchor.MiddleCenter;
194
+
GUILayout.Space (20);
195
+
GUILayout.Label( "Automatic C# Documentation Generation through Doxygen",CenterLable);
196
+
GUILayout.Label( "Version: 1.0",CenterLable);
197
+
GUILayout.Label( "By: Jacob Pennock",CenterLable);
198
+
199
+
GUILayout.Space (20);
200
+
EditorGUILayout.BeginHorizontal();
201
+
GUILayout.Space (20);
202
+
GUILayout.Label( "Follow me for more Unity tips and tricks",littletext);
203
+
GUILayout.Space (15);
204
+
if(GUILayout.Button( "twitter"))
205
+
Application.OpenURL("http://twitter.com/@JacobPennock");
206
+
GUILayout.Space (20);
207
+
EditorGUILayout.EndHorizontal();
208
+
209
+
GUILayout.Space (10);
210
+
EditorGUILayout.BeginHorizontal();
211
+
GUILayout.Space (20);
212
+
GUILayout.Label( "Visit my site for more plugins and tutorials",littletext);
213
+
if(GUILayout.Button( "JacobPennock.com"))
214
+
Application.OpenURL("http://www.jacobpennock.com/Blog/?cat=19");
215
+
GUILayout.Space (20);
216
+
EditorGUILayout.EndHorizontal();
217
+
}
218
+
219
+
void GenerateGUI()
220
+
{
221
+
if(DoxyFileExists)
222
+
{
223
+
//UnityEngine.Debug.Log(DoxyoutputProgress);
224
+
GUILayout.Space (10);
225
+
if(!DocsGenerated)
226
+
GUI.enabled = false;
227
+
if(GUILayout.Button ("Browse Documentation", GUILayout.Height(40)))
228
+
Application.OpenURL("File://"+Config.DocDirectory+"/html/annotated.html");
229
+
GUI.enabled = true;
230
+
231
+
if(DoxygenOutput == null)
232
+
{
233
+
if(GUILayout.Button ("Run Doxygen", GUILayout.Height(40)))
234
+
{
235
+
DocsGenerated = false;
236
+
RunDoxygen();
237
+
}
238
+
239
+
if(DocsGenerated && DoxygenLog != null)
240
+
{
241
+
if(GUILayout.Button( "View Doxygen Log",EditorStyles.toolbarDropDown))
242
+
ViewLog = !ViewLog;
243
+
if(ViewLog)
244
+
{
245
+
scroll = EditorGUILayout.BeginScrollView(scroll, GUILayout.ExpandHeight(true));
246
+
foreach(string logitem in DoxygenLog)
247
+
{
248
+
EditorGUILayout.SelectableLabel(logitem,EditorStyles.miniLabel,GUILayout.ExpandWidth(true));
249
+
}
250
+
EditorGUILayout.EndScrollView();
251
+
}
252
+
}
253
+
}
254
+
else
255
+
{
256
+
if(DoxygenOutput.isStarted() && !DoxygenOutput.isFinished())
257
+
{
258
+
string currentline = DoxygenOutput.ReadLine();
259
+
DoxyoutputProgress = DoxyoutputProgress + 0.1f;
260
+
if(DoxyoutputProgress >= 0.9f)
261
+
DoxyoutputProgress = 0.75f;
262
+
Rect r = EditorGUILayout.BeginVertical();
263
+
EditorGUI.ProgressBar(r, DoxyoutputProgress,currentline );
264
+
GUILayout.Space(40);
265
+
EditorGUILayout.EndVertical();
266
+
}
267
+
if(DoxygenOutput.isFinished())
268
+
{
269
+
if (Event.current.type == EventType.Repaint)
270
+
{
271
+
/*
272
+
If you look at what SetTheme is doing, I know, it seems a little scary to be
273
+
calling file moving operations from inside a an OnGUI call like this. And
274
+
maybe it would be a better choice to call SetTheme and update these other vars
275
+
from inside of the OnDoxygenFinished callback. But since the callback is static
276
+
that would require a little bit of messy singleton instance checking to make sure
277
+
the call back was calling into the right functions. I did try to do it that way
278
+
but for some reason the file operations failed every time. I'm not sure why.
279
+
This is what I was getting from the debugger:
280
+
281
+
Error in file: C:/BuildAgent/work/842f9551727e852/Runtime/Mono/MonoManager.cpp at line 2212
282
+
UnityEditor.FileUtil:DeleteFileOrDirectory(String)
283
+
UnityEditor.FileUtil:ReplaceFile(String, String) (at C:\BuildAgent\work\842f9557127e852\Editor\MonoGenerated\Editor\FileUtil.cs:42)
284
+
285
+
Doing them here seems to work every time and the Repaint event check ensures that they will only be done once.
286
+
*/
287
+
SetTheme(SelectedTheme);
288
+
DoxygenLog = DoxygenOutput.ReadFullLog();
289
+
DoxyoutputProgress = -1.0f;
290
+
DoxygenOutput = null;
291
+
DocsGenerated = true;
292
+
EditorPrefs.SetBool(UnityProjectID+"DocsGenerated",DocsGenerated);
293
+
}
294
+
}
295
+
}
296
+
}
297
+
else
298
+
{
299
+
GUIStyle ErrorLabel = new GUIStyle(EditorStyles.largeLabel);
300
+
ErrorLabel.alignment = TextAnchor.MiddleCenter;
301
+
GUILayout.Space(20);
302
+
GUI.contentColor = Color.red;
303
+
GUILayout.Label("You must set the path to your Doxygen install and \nbuild a new Doxyfile before you can generate documentation",ErrorLabel);
304
+
}
305
+
}
306
+
307
+
public void readBaseConfig()
308
+
{
309
+
basefile = (TextAsset)Resources.Load("BaseDoxyfile", typeof(TextAsset));
310
+
reader = new StringReader(basefile.text);
311
+
if ( reader == null )
312
+
UnityEngine.Debug.LogError("BaseDoxyfile not found or not readable");
313
+
else
314
+
BaseFileString = reader.ReadToEnd();
315
+
}
316
+
317
+
public void MakeNewDoxyFile(DoxygenConfig config)
318
+
{
319
+
SaveConfigtoEditor(config);
320
+
CreateProgressString = "Creating Output Folder";
321
+
DoxyfileCreateProgress = 0.1f;
322
+
System.IO.Directory.CreateDirectory(config.DocDirectory);
323
+
324
+
DoxyfileCreateProgress = 0.1f;
325
+
string newfile = BaseFileString.Replace("PROJECT_NAME =", "PROJECT_NAME = "+"\""+config.Project+"\"");
326
+
DoxyfileCreateProgress = 0.2f;
327
+
newfile = newfile.Replace("PROJECT_NUMBER =", "PROJECT_NUMBER = "+config.Version);
328
+
DoxyfileCreateProgress = 0.3f;
329
+
newfile = newfile.Replace("PROJECT_BRIEF =", "PROJECT_BRIEF = "+"\""+config.Synopsis+"\"");
330
+
DoxyfileCreateProgress = 0.4f;
331
+
newfile = newfile.Replace("OUTPUT_DIRECTORY =", "OUTPUT_DIRECTORY = "+"\""+config.DocDirectory+"\"");
332
+
DoxyfileCreateProgress = 0.5f;
333
+
newfile = newfile.Replace("INPUT =", "INPUT = "+"\""+config.ScriptsDirectory+"\"");
334
+
DoxyfileCreateProgress = 0.6f;
335
+
336
+
switch(SelectedTheme)
337
+
{
338
+
case 0:
339
+
newfile = newfile.Replace("GENERATE_TREEVIEW = NO", "GENERATE_TREEVIEW = YES");
340
+
break;
341
+
case 1:
342
+
newfile = newfile.Replace("SEARCHENGINE = YES", "SEARCHENGINE = NO");
343
+
newfile = newfile.Replace("CLASS_DIAGRAMS = YES", "CLASS_DIAGRAMS = NO");
344
+
break;
345
+
}
346
+
347
+
CreateProgressString = "New Options Set";
348
+
349
+
StringBuilder sb = new StringBuilder();
350
+
sb.Append(newfile);
351
+
StreamWriter NewDoxyfile = new StreamWriter(config.DocDirectory + @"\Doxyfile");
352
+
353
+
NewDoxyfile.Write(sb.ToString());
354
+
NewDoxyfile.Close();
355
+
DoxyfileCreateProgress = 1.0f;
356
+
CreateProgressString = "New Doxyfile Created!";
357
+
DoxyFileExists = true;
358
+
EditorPrefs.SetBool(UnityProjectID+"DoxyFileExists",DoxyFileExists);
359
+
}
360
+
361
+
void SaveConfigtoEditor(DoxygenConfig config)
362
+
{
363
+
EditorPrefs.SetString(UnityProjectID+"DoxyProjectName",config.Project);
364
+
EditorPrefs.SetString(UnityProjectID+"DoxyProjectNumber",config.Version);
365
+
EditorPrefs.SetString(UnityProjectID+"DoxyProjectBrief",config.Synopsis);
366
+
EditorPrefs.SetString(UnityProjectID+"DoxyProjectFolder",config.ScriptsDirectory);
367
+
EditorPrefs.SetString(UnityProjectID+"DoxyProjectOutput",config.DocDirectory);
368
+
EditorPrefs.SetString("DoxyEXE", config.PathtoDoxygen);
369
+
EditorPrefs.SetInt(UnityProjectID+"DoxyTheme", SelectedTheme);
370
+
}
371
+
372
+
void LoadConfig()
373
+
{
374
+
if(BaseFileString == null)
375
+
readBaseConfig();
376
+
if(Config == null)
377
+
{
378
+
if(!LoadSavedConfig())
379
+
Config = new DoxygenConfig();
380
+
}
381
+
if(EditorPrefs.HasKey(UnityProjectID+"DoxyFileExists"))
382
+
DoxyFileExists = EditorPrefs.GetBool(UnityProjectID+"DoxyFileExists");
383
+
if(EditorPrefs.HasKey(UnityProjectID+"DocsGenerated"))
384
+
DocsGenerated = EditorPrefs.GetBool(UnityProjectID+"DocsGenerated");
385
+
if(EditorPrefs.HasKey(UnityProjectID+"DoxyTheme"))
386
+
SelectedTheme = EditorPrefs.GetInt(UnityProjectID+"DoxyTheme");
387
+
if(EditorPrefs.HasKey("DoxyEXE"))
388
+
Config.PathtoDoxygen = EditorPrefs.GetString("DoxyEXE");
389
+
}
390
+
391
+
bool LoadSavedConfig()
392
+
{
393
+
if( EditorPrefs.HasKey (UnityProjectID+"DoxyProjectName"))
394
+
{
395
+
Config = new DoxygenConfig();
396
+
Config.Project = EditorPrefs.GetString(UnityProjectID+"DoxyProjectName");
397
+
Config.Version = EditorPrefs.GetString(UnityProjectID+"DoxyProjectNumber");
398
+
Config.Synopsis = EditorPrefs.GetString(UnityProjectID+"DoxyProjectBrief");
399
+
Config.DocDirectory = EditorPrefs.GetString(UnityProjectID+"DoxyProjectOutput");
400
+
Config.ScriptsDirectory = EditorPrefs.GetString(UnityProjectID+"DoxyProjectFolder");
401
+
return true;
402
+
}
403
+
return false;
404
+
}
405
+
406
+
public static void OnDoxygenFinished(int code)
407
+
{
408
+
if(code != 0)
409
+
{
410
+
UnityEngine.Debug.LogError("Doxygen finsished with Error: return code " + code +"\nCheck the Doxgen Log for Errors.\nAlso try regenerating your Doxyfile,\nyou will new to close and reopen the\ndocumentation window before regenerating.");
411
+
}
412
+
}
413
+
414
+
void SetTheme(int theme)
415
+
{
416
+
switch(theme)
417
+
{
418
+
case 1:
419
+
FileUtil.ReplaceFile(AssestsFolder + "/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/DarkTheme/doxygen.css", Config.DocDirectory+"/html/doxygen.css");
420
+
FileUtil.ReplaceFile(AssestsFolder + "/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/DarkTheme/tabs.css", Config.DocDirectory+"/html/tabs.css");
421
+
FileUtil.ReplaceFile(AssestsFolder + "/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/DarkTheme/img_downArrow.png", Config.DocDirectory+"/html/img_downArrow.png");
422
+
break;
423
+
case 2:
424
+
FileUtil.ReplaceFile(AssestsFolder + "/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/LightTheme/doxygen.css", Config.DocDirectory+"/html/doxygen.css");
425
+
FileUtil.ReplaceFile(AssestsFolder + "/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/LightTheme/tabs.css", Config.DocDirectory+"/html/tabs.css");
426
+
FileUtil.ReplaceFile(AssestsFolder + "/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/LightTheme/img_downArrow.png", Config.DocDirectory+"/html/img_downArrow.png");
427
+
FileUtil.ReplaceFile(AssestsFolder + "/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/LightTheme/background_navigation.png", Config.DocDirectory+"/html/background_navigation.png");
428
+
break;
429
+
}
430
+
}
431
+
432
+
public void RunDoxygen()
433
+
{
434
+
string[] Args = new string[1];
435
+
Args[0] = Config.DocDirectory + "/Doxyfile";
436
+
437
+
DoxygenOutput = new DoxyThreadSafeOutput();
438
+
DoxygenOutput.SetStarted();
439
+
440
+
Action<int> setcallback = (int returnCode) => OnDoxygenFinished(returnCode);
441
+
442
+
DoxyRunner Doxygen = new DoxyRunner(Config.PathtoDoxygen,Args,DoxygenOutput,setcallback);
443
+
444
+
Thread DoxygenThread = new Thread(new ThreadStart(Doxygen.RunThreadedDoxy));
445
+
DoxygenThread.Start();
446
+
}
447
+
448
+
}
449
+
450
+
/// <summary>
451
+
/// This class spawns and runs Doxygen in a separate thread, and could serve as an example of how to create
452
+
/// plugins for unity that call a command line application and then get the data back into Unity safely.
453
+
/// </summary>
454
+
public class DoxyRunner
455
+
{
456
+
DoxyThreadSafeOutput SafeOutput;
457
+
public Action<int> onCompleteCallBack;
458
+
List<string> DoxyLog = new List<string>();
459
+
public string EXE = null;
460
+
public string[] Args;
461
+
static string WorkingFolder;
462
+
463
+
public DoxyRunner(string exepath, string[] args,DoxyThreadSafeOutput safeoutput,Action<int> callback)
464
+
{
465
+
EXE = exepath;
466
+
Args = args;
467
+
SafeOutput = safeoutput;
468
+
onCompleteCallBack = callback;
469
+
WorkingFolder = FileUtil.GetUniqueTempPathInProject();
470
+
System.IO.Directory.CreateDirectory(WorkingFolder);
471
+
}
472
+
473
+
public void updateOuputString(string output)
474
+
{
475
+
SafeOutput.WriteLine(output);
476
+
DoxyLog.Add(output);
477
+
}
478
+
479
+
public void RunThreadedDoxy()
480
+
{
481
+
Action<string> GetOutput = (string output) => updateOuputString(output);
482
+
int ReturnCode = Run(GetOutput,null,EXE,Args);
483
+
SafeOutput.WriteFullLog(DoxyLog);
484
+
SafeOutput.SetFinished();
485
+
onCompleteCallBack(ReturnCode);
486
+
}
487
+
488
+
/// <summary>
489
+
/// Runs the specified executable with the provided arguments and returns the process' exit code.
490
+
/// </summary>
491
+
/// <param name="output">Recieves the output of either std/err or std/out</param>
492
+
/// <param name="input">Provides the line-by-line input that will be written to std/in, null for empty</param>
493
+
/// <param name="exe">The executable to run, may be unqualified or contain environment variables</param>
494
+
/// <param name="args">The list of unescaped arguments to provide to the executable</param>
495
+
/// <returns>Returns process' exit code after the program exits</returns>
496
+
/// <exception cref="System.IO.FileNotFoundException">Raised when the exe was not found</exception>
497
+
/// <exception cref="System.ArgumentNullException">Raised when one of the arguments is null</exception>
498
+
/// <exception cref="System.ArgumentOutOfRangeException">Raised if an argument contains '\0', '\r', or '\n'
499
+
public static int Run(Action<string> output, TextReader input, string exe, params string[] args)
500
+
{
501
+
if (String.IsNullOrEmpty(exe))
502
+
throw new FileNotFoundException();
503
+
if (output == null)
504
+
throw new ArgumentNullException("output");
505
+
506
+
ProcessStartInfo psi = new ProcessStartInfo();
507
+
psi.UseShellExecute = false;
508
+
psi.RedirectStandardError = true;
509
+
psi.RedirectStandardOutput = true;
510
+
psi.RedirectStandardInput = true;
511
+
psi.WindowStyle = ProcessWindowStyle.Hidden;
512
+
psi.CreateNoWindow = true;
513
+
psi.ErrorDialog = false;
514
+
psi.WorkingDirectory = WorkingFolder;
515
+
psi.FileName = FindExePath(exe);
516
+
psi.Arguments = EscapeArguments(args);
517
+
518
+
using (Process process = Process.Start(psi))
519
+
using (ManualResetEvent mreOut = new ManualResetEvent(false),
520
+
mreErr = new ManualResetEvent(false))
521
+
{
522
+
process.OutputDataReceived += (o, e) => { if (e.Data == null) mreOut.Set(); else output(e.Data); };
523
+
process.BeginOutputReadLine();
524
+
process.ErrorDataReceived += (o, e) => { if (e.Data == null) mreErr.Set(); else output(e.Data); };
525
+
process.BeginErrorReadLine();
526
+
527
+
string line;
528
+
while (input != null && null != (line = input.ReadLine()))
529
+
process.StandardInput.WriteLine(line);
530
+
531
+
process.StandardInput.Close();
532
+
process.WaitForExit();
533
+
534
+
mreOut.WaitOne();
535
+
mreErr.WaitOne();
536
+
return process.ExitCode;
537
+
}
538
+
}
539
+
540
+
/// <summary>
541
+
/// Quotes all arguments that contain whitespace, or begin with a quote and returns a single
542
+
/// argument string for use with Process.Start().
543
+
/// </summary>
544
+
/// <param name="args">A list of strings for arguments, may not contain null, '\0', '\r', or '\n'</param>
545
+
/// <returns>The combined list of escaped/quoted strings</returns>
546
+
/// <exception cref="System.ArgumentNullException">Raised when one of the arguments is null</exception>
547
+
/// <exception cref="System.ArgumentOutOfRangeException">Raised if an argument contains '\0', '\r', or '\n'</exception>
548
+
public static string EscapeArguments(params string[] args)
549
+
{
550
+
StringBuilder arguments = new StringBuilder();
551
+
Regex invalidChar = new Regex("[\x00\x0a\x0d]");// these can not be escaped
552
+
Regex needsQuotes = new Regex(@"\s|""");// contains whitespace or two quote characters
553
+
Regex escapeQuote = new Regex(@"(\\*)(""|$)");// one or more '\' followed with a quote or end of string
554
+
for (int carg = 0; args != null && carg < args.Length; carg++)
555
+
{
556
+
if (args[carg] == null)
557
+
{
558
+
throw new ArgumentNullException("args[" + carg + "]");
559
+
}
560
+
if (invalidChar.IsMatch(args[carg]))
561
+
{
562
+
throw new ArgumentOutOfRangeException("args[" + carg + "]");
563
+
}
564
+
if (args[carg] == String.Empty)
565
+
{
566
+
arguments.Append("\"\"");
567
+
}
568
+
else if (!needsQuotes.IsMatch(args[carg]))
569
+
{
570
+
arguments.Append(args[carg]);
571
+
}
572
+
else
573
+
{
574
+
arguments.Append('"');
575
+
arguments.Append(escapeQuote.Replace(args[carg], m =>
576
+
m.Groups[1].Value + m.Groups[1].Value +
577
+
(m.Groups[2].Value == "\"" ? "\\\"" : "")
578
+
));
579
+
arguments.Append('"');
580
+
}
581
+
if (carg + 1 < args.Length)
582
+
arguments.Append(' ');
583
+
}
584
+
return arguments.ToString();
585
+
}
586
+
587
+
588
+
/// <summary>
589
+
/// Expands environment variables and, if unqualified, locates the exe in the working directory
590
+
/// or the evironment's path.
591
+
/// </summary>
592
+
/// <param name="exe">The name of the executable file</param>
593
+
/// <returns>The fully-qualified path to the file</returns>
594
+
/// <exception cref="System.IO.FileNotFoundException">Raised when the exe was not found</exception>
595
+
public static string FindExePath(string exe)
596
+
{
597
+
exe = Environment.ExpandEnvironmentVariables(exe);
598
+
if (!File.Exists(exe))
599
+
{
600
+
if (Path.GetDirectoryName(exe) == String.Empty)
601
+
{
602
+
foreach (string test in (Environment.GetEnvironmentVariable("PATH") ?? "").Split(';'))
603
+
{
604
+
string path = test.Trim();
605
+
if (!String.IsNullOrEmpty(path) && File.Exists(path = Path.Combine(path, exe)))
606
+
return Path.GetFullPath(path);
607
+
}
608
+
}
609
+
throw new FileNotFoundException(new FileNotFoundException().Message, exe);
610
+
}
611
+
return Path.GetFullPath(exe);
612
+
}
613
+
}
614
+
615
+
616
+
/// <summary>
617
+
/// This class encapsulates the data output by Doxygen so it can be shared with Unity in a thread share way.
618
+
/// </summary>
619
+
public class DoxyThreadSafeOutput
620
+
{
621
+
private ReaderWriterLockSlim outputLock = new ReaderWriterLockSlim();
622
+
private string CurrentOutput = "";
623
+
private List<string> FullLog = new List<string>();
624
+
private bool Finished = false;
625
+
private bool Started = false;
626
+
627
+
public string ReadLine( )
628
+
{
629
+
outputLock.EnterReadLock();
630
+
try
631
+
{
632
+
return CurrentOutput;
633
+
}
634
+
finally
635
+
{
636
+
outputLock.ExitReadLock();
637
+
}
638
+
}
639
+
640
+
public void SetFinished( )
641
+
{
642
+
outputLock.EnterWriteLock();
643
+
try
644
+
{
645
+
Finished = true;
646
+
}
647
+
finally
648
+
{
649
+
outputLock.ExitWriteLock();
650
+
}
651
+
}
652
+
653
+
public void SetStarted( )
654
+
{
655
+
outputLock.EnterWriteLock();
656
+
try
657
+
{
658
+
Started = true;
659
+
}
660
+
finally
661
+
{
662
+
outputLock.ExitWriteLock();
663
+
}
664
+
}
665
+
666
+
public bool isStarted( )
667
+
{
668
+
outputLock.EnterReadLock();
669
+
try
670
+
{
671
+
return Started;
672
+
}
673
+
finally
674
+
{
675
+
outputLock.ExitReadLock();
676
+
}
677
+
}
678
+
679
+
public bool isFinished( )
680
+
{
681
+
outputLock.EnterReadLock();
682
+
try
683
+
{
684
+
return Finished;
685
+
}
686
+
finally
687
+
{
688
+
outputLock.ExitReadLock();
689
+
}
690
+
}
691
+
692
+
public List<string> ReadFullLog()
693
+
{
694
+
outputLock.EnterReadLock();
695
+
try
696
+
{
697
+
return FullLog;
698
+
}
699
+
finally
700
+
{
701
+
outputLock.ExitReadLock();
702
+
}
703
+
}
704
+
705
+
public void WriteFullLog(List<string> newLog)
706
+
{
707
+
outputLock.EnterWriteLock();
708
+
try
709
+
{
710
+
FullLog = newLog;
711
+
}
712
+
finally
713
+
{
714
+
outputLock.ExitWriteLock();
715
+
}
716
+
}
717
+
718
+
public void WriteLine(string newOutput)
719
+
{
720
+
outputLock.EnterWriteLock();
721
+
try
722
+
{
723
+
CurrentOutput = newOutput;
724
+
}
725
+
finally
726
+
{
727
+
outputLock.ExitWriteLock();
728
+
}
729
+
}
730
+
}
731
+
732
+
+11
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/ReadMe.txt
+11
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/ReadMe.txt
···
1
+
A Editor Plugin for automatic doc generation through Doxygen
2
+
Author: Jacob Pennock (http://Jacobpennock.com)
3
+
Version: 1.0
4
+
5
+
Install it in Unity like any other plugin.
6
+
Go to: Window -> Documentation with Doxygen
7
+
Follow the prompts.
8
+
9
+
You can also configure more advanced settings
10
+
of Doxygen by editing the file
11
+
Editor -> Doxygen -> Resources -> BaseDoxyfile
+6
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/ReadMe.txt.meta
+6
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/ReadMe.txt.meta
+9
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources.meta
+9
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources.meta
+1789
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/BaseDoxyfile.txt
+1789
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/BaseDoxyfile.txt
···
1
+
# Doxyfile 1.7.5
2
+
3
+
# This file describes the settings to be used by the documentation system
4
+
# doxygen (www.doxygen.org) for a project
5
+
#
6
+
# All text after a hash (#) is considered a comment and will be ignored
7
+
# The format is:
8
+
# TAG = value [value, ...]
9
+
# For lists items can also be appended using:
10
+
# TAG += value [value, ...]
11
+
# Values that contain spaces should be placed between quotes (" ")
12
+
13
+
#---------------------------------------------------------------------------
14
+
# Project related configuration options
15
+
#---------------------------------------------------------------------------
16
+
17
+
# This tag specifies the encoding used for all characters in the config file
18
+
# that follow. The default is UTF-8 which is also the encoding used for all
19
+
# text before the first occurrence of this tag. Doxygen uses libiconv (or the
20
+
# iconv built into libc) for the transcoding. See
21
+
# http://www.gnu.org/software/libiconv for the list of possible encodings.
22
+
23
+
DOXYFILE_ENCODING = UTF-8
24
+
25
+
# The PROJECT_NAME tag is a single word (or sequence of words) that should
26
+
# identify the project. Note that if you do not use Doxywizard you need
27
+
# to put quotes around the project name if it contains spaces.
28
+
29
+
PROJECT_NAME =
30
+
31
+
# The PROJECT_NUMBER tag can be used to enter a project or revision number.
32
+
# This could be handy for archiving the generated documentation or
33
+
# if some version control system is used.
34
+
35
+
PROJECT_NUMBER =
36
+
37
+
# Using the PROJECT_BRIEF tag one can provide an optional one line description
38
+
# for a project that appears at the top of each page and should give viewer
39
+
# a quick idea about the purpose of the project. Keep the description short.
40
+
41
+
PROJECT_BRIEF =
42
+
43
+
# With the PROJECT_LOGO tag one can specify an logo or icon that is
44
+
# included in the documentation. The maximum height of the logo should not
45
+
# exceed 55 pixels and the maximum width should not exceed 200 pixels.
46
+
# Doxygen will copy the logo to the output directory.
47
+
48
+
PROJECT_LOGO =
49
+
50
+
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
51
+
# base path where the generated documentation will be put.
52
+
# If a relative path is entered, it will be relative to the location
53
+
# where doxygen was started. If left blank the current directory will be used.
54
+
55
+
OUTPUT_DIRECTORY =
56
+
57
+
# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
58
+
# 4096 sub-directories (in 2 levels) under the output directory of each output
59
+
# format and will distribute the generated files over these directories.
60
+
# Enabling this option can be useful when feeding doxygen a huge amount of
61
+
# source files, where putting all generated files in the same directory would
62
+
# otherwise cause performance problems for the file system.
63
+
64
+
CREATE_SUBDIRS = NO
65
+
66
+
# The OUTPUT_LANGUAGE tag is used to specify the language in which all
67
+
# documentation generated by doxygen is written. Doxygen will use this
68
+
# information to generate all constant output in the proper language.
69
+
# The default language is English, other supported languages are:
70
+
# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
71
+
# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,
72
+
# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English
73
+
# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,
74
+
# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak,
75
+
# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
76
+
77
+
OUTPUT_LANGUAGE = English
78
+
79
+
# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
80
+
# include brief member descriptions after the members that are listed in
81
+
# the file and class documentation (similar to JavaDoc).
82
+
# Set to NO to disable this.
83
+
84
+
BRIEF_MEMBER_DESC = YES
85
+
86
+
# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
87
+
# the brief description of a member or function before the detailed description.
88
+
# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
89
+
# brief descriptions will be completely suppressed.
90
+
91
+
REPEAT_BRIEF = YES
92
+
93
+
# This tag implements a quasi-intelligent brief description abbreviator
94
+
# that is used to form the text in various listings. Each string
95
+
# in this list, if found as the leading text of the brief description, will be
96
+
# stripped from the text and the result after processing the whole list, is
97
+
# used as the annotated text. Otherwise, the brief description is used as-is.
98
+
# If left blank, the following values are used ("$name" is automatically
99
+
# replaced with the name of the entity): "The $name class" "The $name widget"
100
+
# "The $name file" "is" "provides" "specifies" "contains"
101
+
# "represents" "a" "an" "the"
102
+
103
+
ABBREVIATE_BRIEF = "The $name class" \
104
+
"The $name widget" \
105
+
"The $name file" \
106
+
is \
107
+
provides \
108
+
specifies \
109
+
contains \
110
+
represents \
111
+
a \
112
+
an \
113
+
the
114
+
115
+
# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
116
+
# Doxygen will generate a detailed section even if there is only a brief
117
+
# description.
118
+
119
+
ALWAYS_DETAILED_SEC = NO
120
+
121
+
# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
122
+
# inherited members of a class in the documentation of that class as if those
123
+
# members were ordinary class members. Constructors, destructors and assignment
124
+
# operators of the base classes will not be shown.
125
+
126
+
INLINE_INHERITED_MEMB = NO
127
+
128
+
# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
129
+
# path before files name in the file list and in the header files. If set
130
+
# to NO the shortest path that makes the file name unique will be used.
131
+
132
+
FULL_PATH_NAMES = YES
133
+
134
+
# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
135
+
# can be used to strip a user-defined part of the path. Stripping is
136
+
# only done if one of the specified strings matches the left-hand part of
137
+
# the path. The tag can be used to show relative paths in the file list.
138
+
# If left blank the directory from which doxygen is run is used as the
139
+
# path to strip.
140
+
141
+
STRIP_FROM_PATH =
142
+
143
+
# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
144
+
# the path mentioned in the documentation of a class, which tells
145
+
# the reader which header file to include in order to use a class.
146
+
# If left blank only the name of the header file containing the class
147
+
# definition is used. Otherwise one should specify the include paths that
148
+
# are normally passed to the compiler using the -I flag.
149
+
150
+
STRIP_FROM_INC_PATH =
151
+
152
+
# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
153
+
# (but less readable) file names. This can be useful if your file system
154
+
# doesn't support long names like on DOS, Mac, or CD-ROM.
155
+
156
+
SHORT_NAMES = NO
157
+
158
+
# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
159
+
# will interpret the first line (until the first dot) of a JavaDoc-style
160
+
# comment as the brief description. If set to NO, the JavaDoc
161
+
# comments will behave just like regular Qt-style comments
162
+
# (thus requiring an explicit @brief command for a brief description.)
163
+
164
+
JAVADOC_AUTOBRIEF = YES
165
+
166
+
# If the QT_AUTOBRIEF tag is set to YES then Doxygen will
167
+
# interpret the first line (until the first dot) of a Qt-style
168
+
# comment as the brief description. If set to NO, the comments
169
+
# will behave just like regular Qt-style comments (thus requiring
170
+
# an explicit \brief command for a brief description.)
171
+
172
+
QT_AUTOBRIEF = NO
173
+
174
+
# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
175
+
# treat a multi-line C++ special comment block (i.e. a block of //! or ///
176
+
# comments) as a brief description. This used to be the default behaviour.
177
+
# The new default is to treat a multi-line C++ comment block as a detailed
178
+
# description. Set this tag to YES if you prefer the old behaviour instead.
179
+
180
+
MULTILINE_CPP_IS_BRIEF = NO
181
+
182
+
# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
183
+
# member inherits the documentation from any documented member that it
184
+
# re-implements.
185
+
186
+
INHERIT_DOCS = YES
187
+
188
+
# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
189
+
# a new page for each member. If set to NO, the documentation of a member will
190
+
# be part of the file/class/namespace that contains it.
191
+
192
+
SEPARATE_MEMBER_PAGES = NO
193
+
194
+
# The TAB_SIZE tag can be used to set the number of spaces in a tab.
195
+
# Doxygen uses this value to replace tabs by spaces in code fragments.
196
+
197
+
TAB_SIZE = 4
198
+
199
+
# This tag can be used to specify a number of aliases that acts
200
+
# as commands in the documentation. An alias has the form "name=value".
201
+
# For example adding "sideeffect=\par Side Effects:\n" will allow you to
202
+
# put the command \sideeffect (or @sideeffect) in the documentation, which
203
+
# will result in a user-defined paragraph with heading "Side Effects:".
204
+
# You can put \n's in the value part of an alias to insert newlines.
205
+
206
+
ALIASES =
207
+
208
+
# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
209
+
# sources only. Doxygen will then generate output that is more tailored for C.
210
+
# For instance, some of the names that are used will be different. The list
211
+
# of all members will be omitted, etc.
212
+
213
+
OPTIMIZE_OUTPUT_FOR_C = NO
214
+
215
+
# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
216
+
# sources only. Doxygen will then generate output that is more tailored for
217
+
# Java. For instance, namespaces will be presented as packages, qualified
218
+
# scopes will look different, etc.
219
+
220
+
OPTIMIZE_OUTPUT_JAVA = YES
221
+
222
+
# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
223
+
# sources only. Doxygen will then generate output that is more tailored for
224
+
# Fortran.
225
+
226
+
OPTIMIZE_FOR_FORTRAN = NO
227
+
228
+
# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
229
+
# sources. Doxygen will then generate output that is tailored for
230
+
# VHDL.
231
+
232
+
OPTIMIZE_OUTPUT_VHDL = NO
233
+
234
+
# Doxygen selects the parser to use depending on the extension of the files it
235
+
# parses. With this tag you can assign which parser to use for a given extension.
236
+
# Doxygen has a built-in mapping, but you can override or extend it using this
237
+
# tag. The format is ext=language, where ext is a file extension, and language
238
+
# is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C,
239
+
# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make
240
+
# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C
241
+
# (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions
242
+
# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.
243
+
244
+
EXTENSION_MAPPING =
245
+
246
+
# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
247
+
# to include (a tag file for) the STL sources as input, then you should
248
+
# set this tag to YES in order to let doxygen match functions declarations and
249
+
# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
250
+
# func(std::string) {}). This also makes the inheritance and collaboration
251
+
# diagrams that involve STL classes more complete and accurate.
252
+
253
+
BUILTIN_STL_SUPPORT = NO
254
+
255
+
# If you use Microsoft's C++/CLI language, you should set this option to YES to
256
+
# enable parsing support.
257
+
258
+
CPP_CLI_SUPPORT = NO
259
+
260
+
# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.
261
+
# Doxygen will parse them like normal C++ but will assume all classes use public
262
+
# instead of private inheritance when no explicit protection keyword is present.
263
+
264
+
SIP_SUPPORT = NO
265
+
266
+
# For Microsoft's IDL there are propget and propput attributes to indicate getter
267
+
# and setter methods for a property. Setting this option to YES (the default)
268
+
# will make doxygen replace the get and set methods by a property in the
269
+
# documentation. This will only work if the methods are indeed getting or
270
+
# setting a simple type. If this is not the case, or you want to show the
271
+
# methods anyway, you should set this option to NO.
272
+
273
+
IDL_PROPERTY_SUPPORT = YES
274
+
275
+
# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
276
+
# tag is set to YES, then doxygen will reuse the documentation of the first
277
+
# member in the group (if any) for the other members of the group. By default
278
+
# all members of a group must be documented explicitly.
279
+
280
+
DISTRIBUTE_GROUP_DOC = NO
281
+
282
+
# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
283
+
# the same type (for instance a group of public functions) to be put as a
284
+
# subgroup of that type (e.g. under the Public Functions section). Set it to
285
+
# NO to prevent subgrouping. Alternatively, this can be done per class using
286
+
# the \nosubgrouping command.
287
+
288
+
SUBGROUPING = YES
289
+
290
+
# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and
291
+
# unions are shown inside the group in which they are included (e.g. using
292
+
# @ingroup) instead of on a separate page (for HTML and Man pages) or
293
+
# section (for LaTeX and RTF).
294
+
295
+
INLINE_GROUPED_CLASSES = NO
296
+
297
+
# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and
298
+
# unions with only public data fields will be shown inline in the documentation
299
+
# of the scope in which they are defined (i.e. file, namespace, or group
300
+
# documentation), provided this scope is documented. If set to NO (the default),
301
+
# structs, classes, and unions are shown on a separate page (for HTML and Man
302
+
# pages) or section (for LaTeX and RTF).
303
+
304
+
INLINE_SIMPLE_STRUCTS = NO
305
+
306
+
# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
307
+
# is documented as struct, union, or enum with the name of the typedef. So
308
+
# typedef struct TypeS {} TypeT, will appear in the documentation as a struct
309
+
# with name TypeT. When disabled the typedef will appear as a member of a file,
310
+
# namespace, or class. And the struct will be named TypeS. This can typically
311
+
# be useful for C code in case the coding convention dictates that all compound
312
+
# types are typedef'ed and only the typedef is referenced, never the tag name.
313
+
314
+
TYPEDEF_HIDES_STRUCT = NO
315
+
316
+
# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to
317
+
# determine which symbols to keep in memory and which to flush to disk.
318
+
# When the cache is full, less often used symbols will be written to disk.
319
+
# For small to medium size projects (<1000 input files) the default value is
320
+
# probably good enough. For larger projects a too small cache size can cause
321
+
# doxygen to be busy swapping symbols to and from disk most of the time
322
+
# causing a significant performance penalty.
323
+
# If the system has enough physical memory increasing the cache will improve the
324
+
# performance by keeping more symbols in memory. Note that the value works on
325
+
# a logarithmic scale so increasing the size by one will roughly double the
326
+
# memory usage. The cache size is given by this formula:
327
+
# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
328
+
# corresponding to a cache size of 2^16 = 65536 symbols
329
+
330
+
SYMBOL_CACHE_SIZE = 0
331
+
332
+
#---------------------------------------------------------------------------
333
+
# Build related configuration options
334
+
#---------------------------------------------------------------------------
335
+
336
+
# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
337
+
# documentation are documented, even if no documentation was available.
338
+
# Private class members and static file members will be hidden unless
339
+
# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
340
+
341
+
EXTRACT_ALL = YES
342
+
343
+
# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
344
+
# will be included in the documentation.
345
+
346
+
EXTRACT_PRIVATE = NO
347
+
348
+
# If the EXTRACT_STATIC tag is set to YES all static members of a file
349
+
# will be included in the documentation.
350
+
351
+
EXTRACT_STATIC = YES
352
+
353
+
# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
354
+
# defined locally in source files will be included in the documentation.
355
+
# If set to NO only classes defined in header files are included.
356
+
357
+
EXTRACT_LOCAL_CLASSES = YES
358
+
359
+
# This flag is only useful for Objective-C code. When set to YES local
360
+
# methods, which are defined in the implementation section but not in
361
+
# the interface are included in the documentation.
362
+
# If set to NO (the default) only methods in the interface are included.
363
+
364
+
EXTRACT_LOCAL_METHODS = NO
365
+
366
+
# If this flag is set to YES, the members of anonymous namespaces will be
367
+
# extracted and appear in the documentation as a namespace called
368
+
# 'anonymous_namespace{file}', where file will be replaced with the base
369
+
# name of the file that contains the anonymous namespace. By default
370
+
# anonymous namespaces are hidden.
371
+
372
+
EXTRACT_ANON_NSPACES = NO
373
+
374
+
# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
375
+
# undocumented members of documented classes, files or namespaces.
376
+
# If set to NO (the default) these members will be included in the
377
+
# various overviews, but no documentation section is generated.
378
+
# This option has no effect if EXTRACT_ALL is enabled.
379
+
380
+
HIDE_UNDOC_MEMBERS = NO
381
+
382
+
# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
383
+
# undocumented classes that are normally visible in the class hierarchy.
384
+
# If set to NO (the default) these classes will be included in the various
385
+
# overviews. This option has no effect if EXTRACT_ALL is enabled.
386
+
387
+
HIDE_UNDOC_CLASSES = NO
388
+
389
+
# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
390
+
# friend (class|struct|union) declarations.
391
+
# If set to NO (the default) these declarations will be included in the
392
+
# documentation.
393
+
394
+
HIDE_FRIEND_COMPOUNDS = NO
395
+
396
+
# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
397
+
# documentation blocks found inside the body of a function.
398
+
# If set to NO (the default) these blocks will be appended to the
399
+
# function's detailed documentation block.
400
+
401
+
HIDE_IN_BODY_DOCS = NO
402
+
403
+
# The INTERNAL_DOCS tag determines if documentation
404
+
# that is typed after a \internal command is included. If the tag is set
405
+
# to NO (the default) then the documentation will be excluded.
406
+
# Set it to YES to include the internal documentation.
407
+
408
+
INTERNAL_DOCS = NO
409
+
410
+
# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
411
+
# file names in lower-case letters. If set to YES upper-case letters are also
412
+
# allowed. This is useful if you have classes or files whose names only differ
413
+
# in case and if your file system supports case sensitive file names. Windows
414
+
# and Mac users are advised to set this option to NO.
415
+
416
+
CASE_SENSE_NAMES = NO
417
+
418
+
# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
419
+
# will show members with their full class and namespace scopes in the
420
+
# documentation. If set to YES the scope will be hidden.
421
+
422
+
HIDE_SCOPE_NAMES = NO
423
+
424
+
# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
425
+
# will put a list of the files that are included by a file in the documentation
426
+
# of that file.
427
+
428
+
SHOW_INCLUDE_FILES = YES
429
+
430
+
# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen
431
+
# will list include files with double quotes in the documentation
432
+
# rather than with sharp brackets.
433
+
434
+
FORCE_LOCAL_INCLUDES = NO
435
+
436
+
# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
437
+
# is inserted in the documentation for inline members.
438
+
439
+
INLINE_INFO = YES
440
+
441
+
# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
442
+
# will sort the (detailed) documentation of file and class members
443
+
# alphabetically by member name. If set to NO the members will appear in
444
+
# declaration order.
445
+
446
+
SORT_MEMBER_DOCS = YES
447
+
448
+
# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
449
+
# brief documentation of file, namespace and class members alphabetically
450
+
# by member name. If set to NO (the default) the members will appear in
451
+
# declaration order.
452
+
453
+
SORT_BRIEF_DOCS = NO
454
+
455
+
# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen
456
+
# will sort the (brief and detailed) documentation of class members so that
457
+
# constructors and destructors are listed first. If set to NO (the default)
458
+
# the constructors will appear in the respective orders defined by
459
+
# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.
460
+
# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO
461
+
# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
462
+
463
+
SORT_MEMBERS_CTORS_1ST = NO
464
+
465
+
# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
466
+
# hierarchy of group names into alphabetical order. If set to NO (the default)
467
+
# the group names will appear in their defined order.
468
+
469
+
SORT_GROUP_NAMES = NO
470
+
471
+
# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
472
+
# sorted by fully-qualified names, including namespaces. If set to
473
+
# NO (the default), the class list will be sorted only by class name,
474
+
# not including the namespace part.
475
+
# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
476
+
# Note: This option applies only to the class list, not to the
477
+
# alphabetical list.
478
+
479
+
SORT_BY_SCOPE_NAME = NO
480
+
481
+
# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to
482
+
# do proper type resolution of all parameters of a function it will reject a
483
+
# match between the prototype and the implementation of a member function even
484
+
# if there is only one candidate or it is obvious which candidate to choose
485
+
# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen
486
+
# will still accept a match between prototype and implementation in such cases.
487
+
488
+
STRICT_PROTO_MATCHING = NO
489
+
490
+
# The GENERATE_TODOLIST tag can be used to enable (YES) or
491
+
# disable (NO) the todo list. This list is created by putting \todo
492
+
# commands in the documentation.
493
+
494
+
GENERATE_TODOLIST = YES
495
+
496
+
# The GENERATE_TESTLIST tag can be used to enable (YES) or
497
+
# disable (NO) the test list. This list is created by putting \test
498
+
# commands in the documentation.
499
+
500
+
GENERATE_TESTLIST = YES
501
+
502
+
# The GENERATE_BUGLIST tag can be used to enable (YES) or
503
+
# disable (NO) the bug list. This list is created by putting \bug
504
+
# commands in the documentation.
505
+
506
+
GENERATE_BUGLIST = YES
507
+
508
+
# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
509
+
# disable (NO) the deprecated list. This list is created by putting
510
+
# \deprecated commands in the documentation.
511
+
512
+
GENERATE_DEPRECATEDLIST= YES
513
+
514
+
# The ENABLED_SECTIONS tag can be used to enable conditional
515
+
# documentation sections, marked by \if sectionname ... \endif.
516
+
517
+
ENABLED_SECTIONS =
518
+
519
+
# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
520
+
# the initial value of a variable or macro consists of for it to appear in
521
+
# the documentation. If the initializer consists of more lines than specified
522
+
# here it will be hidden. Use a value of 0 to hide initializers completely.
523
+
# The appearance of the initializer of individual variables and macros in the
524
+
# documentation can be controlled using \showinitializer or \hideinitializer
525
+
# command in the documentation regardless of this setting.
526
+
527
+
MAX_INITIALIZER_LINES = 30
528
+
529
+
# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
530
+
# at the bottom of the documentation of classes and structs. If set to YES the
531
+
# list will mention the files that were used to generate the documentation.
532
+
533
+
SHOW_USED_FILES = YES
534
+
535
+
# If the sources in your project are distributed over multiple directories
536
+
# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
537
+
# in the documentation. The default is NO.
538
+
539
+
SHOW_DIRECTORIES = NO
540
+
541
+
# Set the SHOW_FILES tag to NO to disable the generation of the Files page.
542
+
# This will remove the Files entry from the Quick Index and from the
543
+
# Folder Tree View (if specified). The default is YES.
544
+
545
+
SHOW_FILES = YES
546
+
547
+
# Set the SHOW_NAMESPACES tag to NO to disable the generation of the
548
+
# Namespaces page. This will remove the Namespaces entry from the Quick Index
549
+
# and from the Folder Tree View (if specified). The default is YES.
550
+
551
+
SHOW_NAMESPACES = YES
552
+
553
+
# The FILE_VERSION_FILTER tag can be used to specify a program or script that
554
+
# doxygen should invoke to get the current version for each file (typically from
555
+
# the version control system). Doxygen will invoke the program by executing (via
556
+
# popen()) the command <command> <input-file>, where <command> is the value of
557
+
# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
558
+
# provided by doxygen. Whatever the program writes to standard output
559
+
# is used as the file version. See the manual for examples.
560
+
561
+
FILE_VERSION_FILTER =
562
+
563
+
# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
564
+
# by doxygen. The layout file controls the global structure of the generated
565
+
# output files in an output format independent way. The create the layout file
566
+
# that represents doxygen's defaults, run doxygen with the -l option.
567
+
# You can optionally specify a file name after the option, if omitted
568
+
# DoxygenLayout.xml will be used as the name of the layout file.
569
+
570
+
LAYOUT_FILE =
571
+
572
+
# The CITE_BIB_FILES tag can be used to specify one or more bib files
573
+
# containing the references data. This must be a list of .bib files. The
574
+
# .bib extension is automatically appended if omitted. Using this command
575
+
# requires the bibtex tool to be installed. See also
576
+
# http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style
577
+
# of the bibliography can be controlled using LATEX_BIB_STYLE.
578
+
579
+
CITE_BIB_FILES =
580
+
581
+
#---------------------------------------------------------------------------
582
+
# configuration options related to warning and progress messages
583
+
#---------------------------------------------------------------------------
584
+
585
+
# The QUIET tag can be used to turn on/off the messages that are generated
586
+
# by doxygen. Possible values are YES and NO. If left blank NO is used.
587
+
588
+
QUIET = NO
589
+
590
+
# The WARNINGS tag can be used to turn on/off the warning messages that are
591
+
# generated by doxygen. Possible values are YES and NO. If left blank
592
+
# NO is used.
593
+
594
+
WARNINGS = NO
595
+
596
+
# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
597
+
# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
598
+
# automatically be disabled.
599
+
600
+
WARN_IF_UNDOCUMENTED = YES
601
+
602
+
# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
603
+
# potential errors in the documentation, such as not documenting some
604
+
# parameters in a documented function, or documenting parameters that
605
+
# don't exist or using markup commands wrongly.
606
+
607
+
WARN_IF_DOC_ERROR = YES
608
+
609
+
# The WARN_NO_PARAMDOC option can be enabled to get warnings for
610
+
# functions that are documented, but have no documentation for their parameters
611
+
# or return value. If set to NO (the default) doxygen will only warn about
612
+
# wrong or incomplete parameter documentation, but not about the absence of
613
+
# documentation.
614
+
615
+
WARN_NO_PARAMDOC = NO
616
+
617
+
# The WARN_FORMAT tag determines the format of the warning messages that
618
+
# doxygen can produce. The string should contain the $file, $line, and $text
619
+
# tags, which will be replaced by the file and line number from which the
620
+
# warning originated and the warning text. Optionally the format may contain
621
+
# $version, which will be replaced by the version of the file (if it could
622
+
# be obtained via FILE_VERSION_FILTER)
623
+
624
+
WARN_FORMAT = "$file:$line: $text"
625
+
626
+
# The WARN_LOGFILE tag can be used to specify a file to which warning
627
+
# and error messages should be written. If left blank the output is written
628
+
# to stderr.
629
+
630
+
WARN_LOGFILE =
631
+
632
+
#---------------------------------------------------------------------------
633
+
# configuration options related to the input files
634
+
#---------------------------------------------------------------------------
635
+
636
+
# The INPUT tag can be used to specify the files and/or directories that contain
637
+
# documented source files. You may enter file names like "myfile.cpp" or
638
+
# directories like "/usr/src/myproject". Separate the files or directories
639
+
# with spaces.
640
+
641
+
INPUT =
642
+
643
+
# This tag can be used to specify the character encoding of the source files
644
+
# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
645
+
# also the default input encoding. Doxygen uses libiconv (or the iconv built
646
+
# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
647
+
# the list of possible encodings.
648
+
649
+
INPUT_ENCODING = UTF-8
650
+
651
+
# If the value of the INPUT tag contains directories, you can use the
652
+
# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
653
+
# and *.h) to filter out the source-files in the directories. If left
654
+
# blank the following patterns are tested:
655
+
# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh
656
+
# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py
657
+
# *.f90 *.f *.for *.vhd *.vhdl
658
+
659
+
FILE_PATTERNS = *.c \
660
+
*.cc \
661
+
*.cxx \
662
+
*.cpp \
663
+
*.c++ \
664
+
*.d \
665
+
*.java \
666
+
*.ii \
667
+
*.ixx \
668
+
*.ipp \
669
+
*.i++ \
670
+
*.inl \
671
+
*.h \
672
+
*.hh \
673
+
*.hxx \
674
+
*.hpp \
675
+
*.h++ \
676
+
*.idl \
677
+
*.odl \
678
+
*.cs \
679
+
*.php \
680
+
*.php3 \
681
+
*.inc \
682
+
*.m \
683
+
*.mm \
684
+
*.dox \
685
+
*.py \
686
+
*.f90 \
687
+
*.f \
688
+
*.for \
689
+
*.vhd \
690
+
*.vhdl
691
+
692
+
# The RECURSIVE tag can be used to turn specify whether or not subdirectories
693
+
# should be searched for input files as well. Possible values are YES and NO.
694
+
# If left blank NO is used.
695
+
696
+
RECURSIVE = YES
697
+
698
+
# The EXCLUDE tag can be used to specify files and/or directories that should
699
+
# excluded from the INPUT source files. This way you can easily exclude a
700
+
# subdirectory from a directory tree whose root is specified with the INPUT tag.
701
+
# Note that relative paths are relative to directory from which doxygen is run.
702
+
703
+
EXCLUDE =
704
+
705
+
# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
706
+
# directories that are symbolic links (a Unix file system feature) are excluded
707
+
# from the input.
708
+
709
+
EXCLUDE_SYMLINKS = NO
710
+
711
+
# If the value of the INPUT tag contains directories, you can use the
712
+
# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
713
+
# certain files from those directories. Note that the wildcards are matched
714
+
# against the file with absolute path, so to exclude all test directories
715
+
# for example use the pattern */test/*
716
+
717
+
EXCLUDE_PATTERNS =
718
+
719
+
# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
720
+
# (namespaces, classes, functions, etc.) that should be excluded from the
721
+
# output. The symbol name can be a fully qualified name, a word, or if the
722
+
# wildcard * is used, a substring. Examples: ANamespace, AClass,
723
+
# AClass::ANamespace, ANamespace::*Test
724
+
725
+
EXCLUDE_SYMBOLS =
726
+
727
+
# The EXAMPLE_PATH tag can be used to specify one or more files or
728
+
# directories that contain example code fragments that are included (see
729
+
# the \include command).
730
+
731
+
EXAMPLE_PATH =
732
+
733
+
# If the value of the EXAMPLE_PATH tag contains directories, you can use the
734
+
# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
735
+
# and *.h) to filter out the source-files in the directories. If left
736
+
# blank all files are included.
737
+
738
+
EXAMPLE_PATTERNS = *
739
+
740
+
# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
741
+
# searched for input files to be used with the \include or \dontinclude
742
+
# commands irrespective of the value of the RECURSIVE tag.
743
+
# Possible values are YES and NO. If left blank NO is used.
744
+
745
+
EXAMPLE_RECURSIVE = NO
746
+
747
+
# The IMAGE_PATH tag can be used to specify one or more files or
748
+
# directories that contain image that are included in the documentation (see
749
+
# the \image command).
750
+
751
+
IMAGE_PATH =
752
+
753
+
# The INPUT_FILTER tag can be used to specify a program that doxygen should
754
+
# invoke to filter for each input file. Doxygen will invoke the filter program
755
+
# by executing (via popen()) the command <filter> <input-file>, where <filter>
756
+
# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
757
+
# input file. Doxygen will then use the output that the filter program writes
758
+
# to standard output. If FILTER_PATTERNS is specified, this tag will be
759
+
# ignored.
760
+
761
+
INPUT_FILTER =
762
+
763
+
# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
764
+
# basis. Doxygen will compare the file name with each pattern and apply the
765
+
# filter if there is a match. The filters are a list of the form:
766
+
# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
767
+
# info on how filters are used. If FILTER_PATTERNS is empty or if
768
+
# non of the patterns match the file name, INPUT_FILTER is applied.
769
+
770
+
FILTER_PATTERNS =
771
+
772
+
# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
773
+
# INPUT_FILTER) will be used to filter the input files when producing source
774
+
# files to browse (i.e. when SOURCE_BROWSER is set to YES).
775
+
776
+
FILTER_SOURCE_FILES = NO
777
+
778
+
# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
779
+
# pattern. A pattern will override the setting for FILTER_PATTERN (if any)
780
+
# and it is also possible to disable source filtering for a specific pattern
781
+
# using *.ext= (so without naming a filter). This option only has effect when
782
+
# FILTER_SOURCE_FILES is enabled.
783
+
784
+
FILTER_SOURCE_PATTERNS =
785
+
786
+
#---------------------------------------------------------------------------
787
+
# configuration options related to source browsing
788
+
#---------------------------------------------------------------------------
789
+
790
+
# If the SOURCE_BROWSER tag is set to YES then a list of source files will
791
+
# be generated. Documented entities will be cross-referenced with these sources.
792
+
# Note: To get rid of all source code in the generated output, make sure also
793
+
# VERBATIM_HEADERS is set to NO.
794
+
795
+
SOURCE_BROWSER = NO
796
+
797
+
# Setting the INLINE_SOURCES tag to YES will include the body
798
+
# of functions and classes directly in the documentation.
799
+
800
+
INLINE_SOURCES = NO
801
+
802
+
# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
803
+
# doxygen to hide any special comment blocks from generated source code
804
+
# fragments. Normal C and C++ comments will always remain visible.
805
+
806
+
STRIP_CODE_COMMENTS = YES
807
+
808
+
# If the REFERENCED_BY_RELATION tag is set to YES
809
+
# then for each documented function all documented
810
+
# functions referencing it will be listed.
811
+
812
+
REFERENCED_BY_RELATION = NO
813
+
814
+
# If the REFERENCES_RELATION tag is set to YES
815
+
# then for each documented function all documented entities
816
+
# called/used by that function will be listed.
817
+
818
+
REFERENCES_RELATION = NO
819
+
820
+
# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
821
+
# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
822
+
# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
823
+
# link to the source code. Otherwise they will link to the documentation.
824
+
825
+
REFERENCES_LINK_SOURCE = YES
826
+
827
+
# If the USE_HTAGS tag is set to YES then the references to source code
828
+
# will point to the HTML generated by the htags(1) tool instead of doxygen
829
+
# built-in source browser. The htags tool is part of GNU's global source
830
+
# tagging system (see http://www.gnu.org/software/global/global.html). You
831
+
# will need version 4.8.6 or higher.
832
+
833
+
USE_HTAGS = NO
834
+
835
+
# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
836
+
# will generate a verbatim copy of the header file for each class for
837
+
# which an include is specified. Set to NO to disable this.
838
+
839
+
VERBATIM_HEADERS = YES
840
+
841
+
#---------------------------------------------------------------------------
842
+
# configuration options related to the alphabetical class index
843
+
#---------------------------------------------------------------------------
844
+
845
+
# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
846
+
# of all compounds will be generated. Enable this if the project
847
+
# contains a lot of classes, structs, unions or interfaces.
848
+
849
+
ALPHABETICAL_INDEX = YES
850
+
851
+
# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
852
+
# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
853
+
# in which this list will be split (can be a number in the range [1..20])
854
+
855
+
COLS_IN_ALPHA_INDEX = 5
856
+
857
+
# In case all classes in a project start with a common prefix, all
858
+
# classes will be put under the same header in the alphabetical index.
859
+
# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
860
+
# should be ignored while generating the index headers.
861
+
862
+
IGNORE_PREFIX =
863
+
864
+
#---------------------------------------------------------------------------
865
+
# configuration options related to the HTML output
866
+
#---------------------------------------------------------------------------
867
+
868
+
# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
869
+
# generate HTML output.
870
+
871
+
GENERATE_HTML = YES
872
+
873
+
# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
874
+
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
875
+
# put in front of it. If left blank `html' will be used as the default path.
876
+
877
+
HTML_OUTPUT = html
878
+
879
+
# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
880
+
# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
881
+
# doxygen will generate files with .html extension.
882
+
883
+
HTML_FILE_EXTENSION = .html
884
+
885
+
# The HTML_HEADER tag can be used to specify a personal HTML header for
886
+
# each generated HTML page. If it is left blank doxygen will generate a
887
+
# standard header. Note that when using a custom header you are responsible
888
+
# for the proper inclusion of any scripts and style sheets that doxygen
889
+
# needs, which is dependent on the configuration options used.
890
+
# It is adviced to generate a default header using "doxygen -w html
891
+
# header.html footer.html stylesheet.css YourConfigFile" and then modify
892
+
# that header. Note that the header is subject to change so you typically
893
+
# have to redo this when upgrading to a newer version of doxygen or when
894
+
# changing the value of configuration settings such as GENERATE_TREEVIEW!
895
+
896
+
HTML_HEADER =
897
+
898
+
# The HTML_FOOTER tag can be used to specify a personal HTML footer for
899
+
# each generated HTML page. If it is left blank doxygen will generate a
900
+
# standard footer.
901
+
902
+
HTML_FOOTER =
903
+
904
+
# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
905
+
# style sheet that is used by each HTML page. It can be used to
906
+
# fine-tune the look of the HTML output. If the tag is left blank doxygen
907
+
# will generate a default style sheet. Note that doxygen will try to copy
908
+
# the style sheet file to the HTML output directory, so don't put your own
909
+
# stylesheet in the HTML output directory as well, or it will be erased!
910
+
911
+
HTML_STYLESHEET =
912
+
913
+
# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
914
+
# other source files which should be copied to the HTML output directory. Note
915
+
# that these files will be copied to the base HTML output directory. Use the
916
+
# $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
917
+
# files. In the HTML_STYLESHEET file, use the file name only. Also note that
918
+
# the files will be copied as-is; there are no commands or markers available.
919
+
920
+
HTML_EXTRA_FILES =
921
+
922
+
# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.
923
+
# Doxygen will adjust the colors in the stylesheet and background images
924
+
# according to this color. Hue is specified as an angle on a colorwheel,
925
+
# see http://en.wikipedia.org/wiki/Hue for more information.
926
+
# For instance the value 0 represents red, 60 is yellow, 120 is green,
927
+
# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.
928
+
# The allowed range is 0 to 359.
929
+
930
+
HTML_COLORSTYLE_HUE = 220
931
+
932
+
# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of
933
+
# the colors in the HTML output. For a value of 0 the output will use
934
+
# grayscales only. A value of 255 will produce the most vivid colors.
935
+
936
+
HTML_COLORSTYLE_SAT = 100
937
+
938
+
# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to
939
+
# the luminance component of the colors in the HTML output. Values below
940
+
# 100 gradually make the output lighter, whereas values above 100 make
941
+
# the output darker. The value divided by 100 is the actual gamma applied,
942
+
# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,
943
+
# and 100 does not change the gamma.
944
+
945
+
HTML_COLORSTYLE_GAMMA = 80
946
+
947
+
# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
948
+
# page will contain the date and time when the page was generated. Setting
949
+
# this to NO can help when comparing the output of multiple runs.
950
+
951
+
HTML_TIMESTAMP = YES
952
+
953
+
# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
954
+
# files or namespaces will be aligned in HTML using tables. If set to
955
+
# NO a bullet list will be used.
956
+
957
+
HTML_ALIGN_MEMBERS = YES
958
+
959
+
# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
960
+
# documentation will contain sections that can be hidden and shown after the
961
+
# page has loaded. For this to work a browser that supports
962
+
# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
963
+
# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
964
+
965
+
HTML_DYNAMIC_SECTIONS = NO
966
+
967
+
# If the GENERATE_DOCSET tag is set to YES, additional index files
968
+
# will be generated that can be used as input for Apple's Xcode 3
969
+
# integrated development environment, introduced with OSX 10.5 (Leopard).
970
+
# To create a documentation set, doxygen will generate a Makefile in the
971
+
# HTML output directory. Running make will produce the docset in that
972
+
# directory and running "make install" will install the docset in
973
+
# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
974
+
# it at startup.
975
+
# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
976
+
# for more information.
977
+
978
+
GENERATE_DOCSET = NO
979
+
980
+
# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
981
+
# feed. A documentation feed provides an umbrella under which multiple
982
+
# documentation sets from a single provider (such as a company or product suite)
983
+
# can be grouped.
984
+
985
+
DOCSET_FEEDNAME = "Doxygen generated docs"
986
+
987
+
# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
988
+
# should uniquely identify the documentation set bundle. This should be a
989
+
# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
990
+
# will append .docset to the name.
991
+
992
+
DOCSET_BUNDLE_ID = org.doxygen.Project
993
+
994
+
# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify
995
+
# the documentation publisher. This should be a reverse domain-name style
996
+
# string, e.g. com.mycompany.MyDocSet.documentation.
997
+
998
+
DOCSET_PUBLISHER_ID = org.doxygen.Publisher
999
+
1000
+
# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
1001
+
1002
+
DOCSET_PUBLISHER_NAME = Publisher
1003
+
1004
+
# If the GENERATE_HTMLHELP tag is set to YES, additional index files
1005
+
# will be generated that can be used as input for tools like the
1006
+
# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
1007
+
# of the generated HTML documentation.
1008
+
1009
+
GENERATE_HTMLHELP = NO
1010
+
1011
+
# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
1012
+
# be used to specify the file name of the resulting .chm file. You
1013
+
# can add a path in front of the file if the result should not be
1014
+
# written to the html output directory.
1015
+
1016
+
CHM_FILE =
1017
+
1018
+
# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
1019
+
# be used to specify the location (absolute path including file name) of
1020
+
# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
1021
+
# the HTML help compiler on the generated index.hhp.
1022
+
1023
+
HHC_LOCATION =
1024
+
1025
+
# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
1026
+
# controls if a separate .chi index file is generated (YES) or that
1027
+
# it should be included in the master .chm file (NO).
1028
+
1029
+
GENERATE_CHI = NO
1030
+
1031
+
# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
1032
+
# is used to encode HtmlHelp index (hhk), content (hhc) and project file
1033
+
# content.
1034
+
1035
+
CHM_INDEX_ENCODING =
1036
+
1037
+
# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
1038
+
# controls whether a binary table of contents is generated (YES) or a
1039
+
# normal table of contents (NO) in the .chm file.
1040
+
1041
+
BINARY_TOC = NO
1042
+
1043
+
# The TOC_EXPAND flag can be set to YES to add extra items for group members
1044
+
# to the contents of the HTML help documentation and to the tree view.
1045
+
1046
+
TOC_EXPAND = NO
1047
+
1048
+
# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
1049
+
# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated
1050
+
# that can be used as input for Qt's qhelpgenerator to generate a
1051
+
# Qt Compressed Help (.qch) of the generated HTML documentation.
1052
+
1053
+
GENERATE_QHP = NO
1054
+
1055
+
# If the QHG_LOCATION tag is specified, the QCH_FILE tag can
1056
+
# be used to specify the file name of the resulting .qch file.
1057
+
# The path specified is relative to the HTML output folder.
1058
+
1059
+
QCH_FILE =
1060
+
1061
+
# The QHP_NAMESPACE tag specifies the namespace to use when generating
1062
+
# Qt Help Project output. For more information please see
1063
+
# http://doc.trolltech.com/qthelpproject.html#namespace
1064
+
1065
+
QHP_NAMESPACE = org.doxygen.Project
1066
+
1067
+
# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
1068
+
# Qt Help Project output. For more information please see
1069
+
# http://doc.trolltech.com/qthelpproject.html#virtual-folders
1070
+
1071
+
QHP_VIRTUAL_FOLDER = doc
1072
+
1073
+
# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to
1074
+
# add. For more information please see
1075
+
# http://doc.trolltech.com/qthelpproject.html#custom-filters
1076
+
1077
+
QHP_CUST_FILTER_NAME =
1078
+
1079
+
# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the
1080
+
# custom filter to add. For more information please see
1081
+
# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">
1082
+
# Qt Help Project / Custom Filters</a>.
1083
+
1084
+
QHP_CUST_FILTER_ATTRS =
1085
+
1086
+
# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
1087
+
# project's
1088
+
# filter section matches.
1089
+
# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">
1090
+
# Qt Help Project / Filter Attributes</a>.
1091
+
1092
+
QHP_SECT_FILTER_ATTRS =
1093
+
1094
+
# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can
1095
+
# be used to specify the location of Qt's qhelpgenerator.
1096
+
# If non-empty doxygen will try to run qhelpgenerator on the generated
1097
+
# .qhp file.
1098
+
1099
+
QHG_LOCATION =
1100
+
1101
+
# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files
1102
+
# will be generated, which together with the HTML files, form an Eclipse help
1103
+
# plugin. To install this plugin and make it available under the help contents
1104
+
# menu in Eclipse, the contents of the directory containing the HTML and XML
1105
+
# files needs to be copied into the plugins directory of eclipse. The name of
1106
+
# the directory within the plugins directory should be the same as
1107
+
# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before
1108
+
# the help appears.
1109
+
1110
+
GENERATE_ECLIPSEHELP = NO
1111
+
1112
+
# A unique identifier for the eclipse help plugin. When installing the plugin
1113
+
# the directory name containing the HTML and XML files should also have
1114
+
# this name.
1115
+
1116
+
ECLIPSE_DOC_ID = org.doxygen.Project
1117
+
1118
+
# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
1119
+
# top of each HTML page. The value NO (the default) enables the index and
1120
+
# the value YES disables it.
1121
+
1122
+
DISABLE_INDEX = NO
1123
+
1124
+
# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values
1125
+
# (range [0,1..20]) that doxygen will group on one line in the generated HTML
1126
+
# documentation. Note that a value of 0 will completely suppress the enum
1127
+
# values from appearing in the overview section.
1128
+
1129
+
ENUM_VALUES_PER_LINE = 4
1130
+
1131
+
# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1132
+
# structure should be generated to display hierarchical information.
1133
+
# If the tag value is set to YES, a side panel will be generated
1134
+
# containing a tree-like index structure (just like the one that
1135
+
# is generated for HTML Help). For this to work a browser that supports
1136
+
# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
1137
+
# Windows users are probably better off using the HTML help feature.
1138
+
1139
+
GENERATE_TREEVIEW = NO
1140
+
1141
+
# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,
1142
+
# and Class Hierarchy pages using a tree view instead of an ordered list.
1143
+
1144
+
USE_INLINE_TREES = NO
1145
+
1146
+
# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
1147
+
# used to set the initial width (in pixels) of the frame in which the tree
1148
+
# is shown.
1149
+
1150
+
TREEVIEW_WIDTH = 250
1151
+
1152
+
# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open
1153
+
# links to external symbols imported via tag files in a separate window.
1154
+
1155
+
EXT_LINKS_IN_WINDOW = NO
1156
+
1157
+
# Use this tag to change the font size of Latex formulas included
1158
+
# as images in the HTML documentation. The default is 10. Note that
1159
+
# when you change the font size after a successful doxygen run you need
1160
+
# to manually remove any form_*.png images from the HTML output directory
1161
+
# to force them to be regenerated.
1162
+
1163
+
FORMULA_FONTSIZE = 10
1164
+
1165
+
# Use the FORMULA_TRANPARENT tag to determine whether or not the images
1166
+
# generated for formulas are transparent PNGs. Transparent PNGs are
1167
+
# not supported properly for IE 6.0, but are supported on all modern browsers.
1168
+
# Note that when changing this option you need to delete any form_*.png files
1169
+
# in the HTML output before the changes have effect.
1170
+
1171
+
FORMULA_TRANSPARENT = YES
1172
+
1173
+
# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax
1174
+
# (see http://www.mathjax.org) which uses client side Javascript for the
1175
+
# rendering instead of using prerendered bitmaps. Use this if you do not
1176
+
# have LaTeX installed or if you want to formulas look prettier in the HTML
1177
+
# output. When enabled you also need to install MathJax separately and
1178
+
# configure the path to it using the MATHJAX_RELPATH option.
1179
+
1180
+
USE_MATHJAX = NO
1181
+
1182
+
# When MathJax is enabled you need to specify the location relative to the
1183
+
# HTML output directory using the MATHJAX_RELPATH option. The destination
1184
+
# directory should contain the MathJax.js script. For instance, if the mathjax
1185
+
# directory is located at the same level as the HTML output directory, then
1186
+
# MATHJAX_RELPATH should be ../mathjax. The default value points to the
1187
+
# mathjax.org site, so you can quickly see the result without installing
1188
+
# MathJax, but it is strongly recommended to install a local copy of MathJax
1189
+
# before deployment.
1190
+
1191
+
MATHJAX_RELPATH = http://www.mathjax.org/mathjax
1192
+
1193
+
# The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension
1194
+
# names that should be enabled during MathJax rendering.
1195
+
1196
+
MATHJAX_EXTENSIONS =
1197
+
1198
+
# When the SEARCHENGINE tag is enabled doxygen will generate a search box
1199
+
# for the HTML output. The underlying search engine uses javascript
1200
+
# and DHTML and should work on any modern browser. Note that when using
1201
+
# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets
1202
+
# (GENERATE_DOCSET) there is already a search function so this one should
1203
+
# typically be disabled. For large projects the javascript based search engine
1204
+
# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.
1205
+
1206
+
SEARCHENGINE = YES
1207
+
1208
+
# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1209
+
# implemented using a PHP enabled web server instead of at the web client
1210
+
# using Javascript. Doxygen will generate the search PHP script and index
1211
+
# file to put on the web server. The advantage of the server
1212
+
# based approach is that it scales better to large projects and allows
1213
+
# full text search. The disadvantages are that it is more difficult to setup
1214
+
# and does not have live searching capabilities.
1215
+
1216
+
SERVER_BASED_SEARCH = NO
1217
+
1218
+
#---------------------------------------------------------------------------
1219
+
# configuration options related to the LaTeX output
1220
+
#---------------------------------------------------------------------------
1221
+
1222
+
# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
1223
+
# generate Latex output.
1224
+
1225
+
GENERATE_LATEX = NO
1226
+
1227
+
# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
1228
+
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1229
+
# put in front of it. If left blank `latex' will be used as the default path.
1230
+
1231
+
LATEX_OUTPUT = latex
1232
+
1233
+
# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1234
+
# invoked. If left blank `latex' will be used as the default command name.
1235
+
# Note that when enabling USE_PDFLATEX this option is only used for
1236
+
# generating bitmaps for formulas in the HTML output, but not in the
1237
+
# Makefile that is written to the output directory.
1238
+
1239
+
LATEX_CMD_NAME = latex
1240
+
1241
+
# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
1242
+
# generate index for LaTeX. If left blank `makeindex' will be used as the
1243
+
# default command name.
1244
+
1245
+
MAKEINDEX_CMD_NAME = makeindex
1246
+
1247
+
# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
1248
+
# LaTeX documents. This may be useful for small projects and may help to
1249
+
# save some trees in general.
1250
+
1251
+
COMPACT_LATEX = NO
1252
+
1253
+
# The PAPER_TYPE tag can be used to set the paper type that is used
1254
+
# by the printer. Possible values are: a4, letter, legal and
1255
+
# executive. If left blank a4wide will be used.
1256
+
1257
+
PAPER_TYPE = a4
1258
+
1259
+
# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
1260
+
# packages that should be included in the LaTeX output.
1261
+
1262
+
EXTRA_PACKAGES =
1263
+
1264
+
# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
1265
+
# the generated latex document. The header should contain everything until
1266
+
# the first chapter. If it is left blank doxygen will generate a
1267
+
# standard header. Notice: only use this tag if you know what you are doing!
1268
+
1269
+
LATEX_HEADER =
1270
+
1271
+
# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for
1272
+
# the generated latex document. The footer should contain everything after
1273
+
# the last chapter. If it is left blank doxygen will generate a
1274
+
# standard footer. Notice: only use this tag if you know what you are doing!
1275
+
1276
+
LATEX_FOOTER =
1277
+
1278
+
# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
1279
+
# is prepared for conversion to pdf (using ps2pdf). The pdf file will
1280
+
# contain links (just like the HTML output) instead of page references
1281
+
# This makes the output suitable for online browsing using a pdf viewer.
1282
+
1283
+
PDF_HYPERLINKS = YES
1284
+
1285
+
# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
1286
+
# plain latex in the generated Makefile. Set this option to YES to get a
1287
+
# higher quality PDF documentation.
1288
+
1289
+
USE_PDFLATEX = YES
1290
+
1291
+
# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
1292
+
# command to the generated LaTeX files. This will instruct LaTeX to keep
1293
+
# running if errors occur, instead of asking the user for help.
1294
+
# This option is also used when generating formulas in HTML.
1295
+
1296
+
LATEX_BATCHMODE = NO
1297
+
1298
+
# If LATEX_HIDE_INDICES is set to YES then doxygen will not
1299
+
# include the index chapters (such as File Index, Compound Index, etc.)
1300
+
# in the output.
1301
+
1302
+
LATEX_HIDE_INDICES = NO
1303
+
1304
+
# If LATEX_SOURCE_CODE is set to YES then doxygen will include
1305
+
# source code with syntax highlighting in the LaTeX output.
1306
+
# Note that which sources are shown also depends on other settings
1307
+
# such as SOURCE_BROWSER.
1308
+
1309
+
LATEX_SOURCE_CODE = NO
1310
+
1311
+
# The LATEX_BIB_STYLE tag can be used to specify the style to use for the
1312
+
# bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See
1313
+
# http://en.wikipedia.org/wiki/BibTeX for more info.
1314
+
1315
+
LATEX_BIB_STYLE = plain
1316
+
1317
+
#---------------------------------------------------------------------------
1318
+
# configuration options related to the RTF output
1319
+
#---------------------------------------------------------------------------
1320
+
1321
+
# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
1322
+
# The RTF output is optimized for Word 97 and may not look very pretty with
1323
+
# other RTF readers or editors.
1324
+
1325
+
GENERATE_RTF = NO
1326
+
1327
+
# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
1328
+
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1329
+
# put in front of it. If left blank `rtf' will be used as the default path.
1330
+
1331
+
RTF_OUTPUT = rtf
1332
+
1333
+
# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
1334
+
# RTF documents. This may be useful for small projects and may help to
1335
+
# save some trees in general.
1336
+
1337
+
COMPACT_RTF = NO
1338
+
1339
+
# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
1340
+
# will contain hyperlink fields. The RTF file will
1341
+
# contain links (just like the HTML output) instead of page references.
1342
+
# This makes the output suitable for online browsing using WORD or other
1343
+
# programs which support those fields.
1344
+
# Note: wordpad (write) and others do not support links.
1345
+
1346
+
RTF_HYPERLINKS = NO
1347
+
1348
+
# Load stylesheet definitions from file. Syntax is similar to doxygen's
1349
+
# config file, i.e. a series of assignments. You only have to provide
1350
+
# replacements, missing definitions are set to their default value.
1351
+
1352
+
RTF_STYLESHEET_FILE =
1353
+
1354
+
# Set optional variables used in the generation of an rtf document.
1355
+
# Syntax is similar to doxygen's config file.
1356
+
1357
+
RTF_EXTENSIONS_FILE =
1358
+
1359
+
#---------------------------------------------------------------------------
1360
+
# configuration options related to the man page output
1361
+
#---------------------------------------------------------------------------
1362
+
1363
+
# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1364
+
# generate man pages
1365
+
1366
+
GENERATE_MAN = NO
1367
+
1368
+
# The MAN_OUTPUT tag is used to specify where the man pages will be put.
1369
+
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1370
+
# put in front of it. If left blank `man' will be used as the default path.
1371
+
1372
+
MAN_OUTPUT = man
1373
+
1374
+
# The MAN_EXTENSION tag determines the extension that is added to
1375
+
# the generated man pages (default is the subroutine's section .3)
1376
+
1377
+
MAN_EXTENSION = .3
1378
+
1379
+
# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
1380
+
# then it will generate one additional man file for each entity
1381
+
# documented in the real man page(s). These additional files
1382
+
# only source the real man page, but without them the man command
1383
+
# would be unable to find the correct page. The default is NO.
1384
+
1385
+
MAN_LINKS = NO
1386
+
1387
+
#---------------------------------------------------------------------------
1388
+
# configuration options related to the XML output
1389
+
#---------------------------------------------------------------------------
1390
+
1391
+
# If the GENERATE_XML tag is set to YES Doxygen will
1392
+
# generate an XML file that captures the structure of
1393
+
# the code including all documentation.
1394
+
1395
+
GENERATE_XML = NO
1396
+
1397
+
# The XML_OUTPUT tag is used to specify where the XML pages will be put.
1398
+
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1399
+
# put in front of it. If left blank `xml' will be used as the default path.
1400
+
1401
+
XML_OUTPUT = xml
1402
+
1403
+
# The XML_SCHEMA tag can be used to specify an XML schema,
1404
+
# which can be used by a validating XML parser to check the
1405
+
# syntax of the XML files.
1406
+
1407
+
XML_SCHEMA =
1408
+
1409
+
# The XML_DTD tag can be used to specify an XML DTD,
1410
+
# which can be used by a validating XML parser to check the
1411
+
# syntax of the XML files.
1412
+
1413
+
XML_DTD =
1414
+
1415
+
# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
1416
+
# dump the program listings (including syntax highlighting
1417
+
# and cross-referencing information) to the XML output. Note that
1418
+
# enabling this will significantly increase the size of the XML output.
1419
+
1420
+
XML_PROGRAMLISTING = YES
1421
+
1422
+
#---------------------------------------------------------------------------
1423
+
# configuration options for the AutoGen Definitions output
1424
+
#---------------------------------------------------------------------------
1425
+
1426
+
# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
1427
+
# generate an AutoGen Definitions (see autogen.sf.net) file
1428
+
# that captures the structure of the code including all
1429
+
# documentation. Note that this feature is still experimental
1430
+
# and incomplete at the moment.
1431
+
1432
+
GENERATE_AUTOGEN_DEF = NO
1433
+
1434
+
#---------------------------------------------------------------------------
1435
+
# configuration options related to the Perl module output
1436
+
#---------------------------------------------------------------------------
1437
+
1438
+
# If the GENERATE_PERLMOD tag is set to YES Doxygen will
1439
+
# generate a Perl module file that captures the structure of
1440
+
# the code including all documentation. Note that this
1441
+
# feature is still experimental and incomplete at the
1442
+
# moment.
1443
+
1444
+
GENERATE_PERLMOD = NO
1445
+
1446
+
# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
1447
+
# the necessary Makefile rules, Perl scripts and LaTeX code to be able
1448
+
# to generate PDF and DVI output from the Perl module output.
1449
+
1450
+
PERLMOD_LATEX = NO
1451
+
1452
+
# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
1453
+
# nicely formatted so it can be parsed by a human reader. This is useful
1454
+
# if you want to understand what is going on. On the other hand, if this
1455
+
# tag is set to NO the size of the Perl module output will be much smaller
1456
+
# and Perl will parse it just the same.
1457
+
1458
+
PERLMOD_PRETTY = YES
1459
+
1460
+
# The names of the make variables in the generated doxyrules.make file
1461
+
# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
1462
+
# This is useful so different doxyrules.make files included by the same
1463
+
# Makefile don't overwrite each other's variables.
1464
+
1465
+
PERLMOD_MAKEVAR_PREFIX =
1466
+
1467
+
#---------------------------------------------------------------------------
1468
+
# Configuration options related to the preprocessor
1469
+
#---------------------------------------------------------------------------
1470
+
1471
+
# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1472
+
# evaluate all C-preprocessor directives found in the sources and include
1473
+
# files.
1474
+
1475
+
ENABLE_PREPROCESSING = YES
1476
+
1477
+
# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1478
+
# names in the source code. If set to NO (the default) only conditional
1479
+
# compilation will be performed. Macro expansion can be done in a controlled
1480
+
# way by setting EXPAND_ONLY_PREDEF to YES.
1481
+
1482
+
MACRO_EXPANSION = NO
1483
+
1484
+
# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1485
+
# then the macro expansion is limited to the macros specified with the
1486
+
# PREDEFINED and EXPAND_AS_DEFINED tags.
1487
+
1488
+
EXPAND_ONLY_PREDEF = NO
1489
+
1490
+
# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1491
+
# pointed to by INCLUDE_PATH will be searched when a #include is found.
1492
+
1493
+
SEARCH_INCLUDES = YES
1494
+
1495
+
# The INCLUDE_PATH tag can be used to specify one or more directories that
1496
+
# contain include files that are not input files but should be processed by
1497
+
# the preprocessor.
1498
+
1499
+
INCLUDE_PATH =
1500
+
1501
+
# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1502
+
# patterns (like *.h and *.hpp) to filter out the header-files in the
1503
+
# directories. If left blank, the patterns specified with FILE_PATTERNS will
1504
+
# be used.
1505
+
1506
+
INCLUDE_FILE_PATTERNS =
1507
+
1508
+
# The PREDEFINED tag can be used to specify one or more macro names that
1509
+
# are defined before the preprocessor is started (similar to the -D option of
1510
+
# gcc). The argument of the tag is a list of macros of the form: name
1511
+
# or name=definition (no spaces). If the definition and the = are
1512
+
# omitted =1 is assumed. To prevent a macro definition from being
1513
+
# undefined via #undef or recursively expanded use the := operator
1514
+
# instead of the = operator.
1515
+
1516
+
PREDEFINED =
1517
+
1518
+
# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1519
+
# this tag can be used to specify a list of macro names that should be expanded.
1520
+
# The macro definition that is found in the sources will be used.
1521
+
# Use the PREDEFINED tag if you want to use a different macro definition that
1522
+
# overrules the definition found in the source code.
1523
+
1524
+
EXPAND_AS_DEFINED =
1525
+
1526
+
# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1527
+
# doxygen's preprocessor will remove all references to function-like macros
1528
+
# that are alone on a line, have an all uppercase name, and do not end with a
1529
+
# semicolon, because these will confuse the parser if not removed.
1530
+
1531
+
SKIP_FUNCTION_MACROS = YES
1532
+
1533
+
#---------------------------------------------------------------------------
1534
+
# Configuration::additions related to external references
1535
+
#---------------------------------------------------------------------------
1536
+
1537
+
# The TAGFILES option can be used to specify one or more tagfiles.
1538
+
# Optionally an initial location of the external documentation
1539
+
# can be added for each tagfile. The format of a tag file without
1540
+
# this location is as follows:
1541
+
# TAGFILES = file1 file2 ...
1542
+
# Adding location for the tag files is done as follows:
1543
+
# TAGFILES = file1=loc1 "file2 = loc2" ...
1544
+
# where "loc1" and "loc2" can be relative or absolute paths or
1545
+
# URLs. If a location is present for each tag, the installdox tool
1546
+
# does not have to be run to correct the links.
1547
+
# Note that each tag file must have a unique name
1548
+
# (where the name does NOT include the path)
1549
+
# If a tag file is not located in the directory in which doxygen
1550
+
# is run, you must also specify the path to the tagfile here.
1551
+
1552
+
TAGFILES =
1553
+
1554
+
# When a file name is specified after GENERATE_TAGFILE, doxygen will create
1555
+
# a tag file that is based on the input files it reads.
1556
+
1557
+
GENERATE_TAGFILE =
1558
+
1559
+
# If the ALLEXTERNALS tag is set to YES all external classes will be listed
1560
+
# in the class index. If set to NO only the inherited external classes
1561
+
# will be listed.
1562
+
1563
+
ALLEXTERNALS = NO
1564
+
1565
+
# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1566
+
# in the modules index. If set to NO, only the current project's groups will
1567
+
# be listed.
1568
+
1569
+
EXTERNAL_GROUPS = YES
1570
+
1571
+
# The PERL_PATH should be the absolute path and name of the perl script
1572
+
# interpreter (i.e. the result of `which perl').
1573
+
1574
+
PERL_PATH = /usr/bin/perl
1575
+
1576
+
#---------------------------------------------------------------------------
1577
+
# Configuration options related to the dot tool
1578
+
#---------------------------------------------------------------------------
1579
+
1580
+
# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1581
+
# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1582
+
# or super classes. Setting the tag to NO turns the diagrams off. Note that
1583
+
# this option also works with HAVE_DOT disabled, but it is recommended to
1584
+
# install and use dot, since it yields more powerful graphs.
1585
+
1586
+
CLASS_DIAGRAMS = YES
1587
+
1588
+
# You can define message sequence charts within doxygen comments using the \msc
1589
+
# command. Doxygen will then run the mscgen tool (see
1590
+
# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the
1591
+
# documentation. The MSCGEN_PATH tag allows you to specify the directory where
1592
+
# the mscgen tool resides. If left empty the tool is assumed to be found in the
1593
+
# default search path.
1594
+
1595
+
MSCGEN_PATH =
1596
+
1597
+
# If set to YES, the inheritance and collaboration graphs will hide
1598
+
# inheritance and usage relations if the target is undocumented
1599
+
# or is not a class.
1600
+
1601
+
HIDE_UNDOC_RELATIONS = YES
1602
+
1603
+
# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1604
+
# available from the path. This tool is part of Graphviz, a graph visualization
1605
+
# toolkit from AT&T and Lucent Bell Labs. The other options in this section
1606
+
# have no effect if this option is set to NO (the default)
1607
+
1608
+
HAVE_DOT = NO
1609
+
1610
+
# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is
1611
+
# allowed to run in parallel. When set to 0 (the default) doxygen will
1612
+
# base this on the number of processors available in the system. You can set it
1613
+
# explicitly to a value larger than 0 to get control over the balance
1614
+
# between CPU load and processing speed.
1615
+
1616
+
DOT_NUM_THREADS = 0
1617
+
1618
+
# By default doxygen will use the Helvetica font for all dot files that
1619
+
# doxygen generates. When you want a differently looking font you can specify
1620
+
# the font name using DOT_FONTNAME. You need to make sure dot is able to find
1621
+
# the font, which can be done by putting it in a standard location or by setting
1622
+
# the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the
1623
+
# directory containing the font.
1624
+
1625
+
DOT_FONTNAME = Helvetica
1626
+
1627
+
# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.
1628
+
# The default size is 10pt.
1629
+
1630
+
DOT_FONTSIZE = 10
1631
+
1632
+
# By default doxygen will tell dot to use the Helvetica font.
1633
+
# If you specify a different font using DOT_FONTNAME you can use DOT_FONTPATH to
1634
+
# set the path where dot can find it.
1635
+
1636
+
DOT_FONTPATH =
1637
+
1638
+
# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1639
+
# will generate a graph for each documented class showing the direct and
1640
+
# indirect inheritance relations. Setting this tag to YES will force the
1641
+
# the CLASS_DIAGRAMS tag to NO.
1642
+
1643
+
CLASS_GRAPH = YES
1644
+
1645
+
# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1646
+
# will generate a graph for each documented class showing the direct and
1647
+
# indirect implementation dependencies (inheritance, containment, and
1648
+
# class references variables) of the class with other documented classes.
1649
+
1650
+
COLLABORATION_GRAPH = YES
1651
+
1652
+
# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
1653
+
# will generate a graph for groups, showing the direct groups dependencies
1654
+
1655
+
GROUP_GRAPHS = YES
1656
+
1657
+
# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1658
+
# collaboration diagrams in a style similar to the OMG's Unified Modeling
1659
+
# Language.
1660
+
1661
+
UML_LOOK = NO
1662
+
1663
+
# If set to YES, the inheritance and collaboration graphs will show the
1664
+
# relations between templates and their instances.
1665
+
1666
+
TEMPLATE_RELATIONS = NO
1667
+
1668
+
# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1669
+
# tags are set to YES then doxygen will generate a graph for each documented
1670
+
# file showing the direct and indirect include dependencies of the file with
1671
+
# other documented files.
1672
+
1673
+
INCLUDE_GRAPH = YES
1674
+
1675
+
# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1676
+
# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1677
+
# documented header file showing the documented files that directly or
1678
+
# indirectly include this file.
1679
+
1680
+
INCLUDED_BY_GRAPH = YES
1681
+
1682
+
# If the CALL_GRAPH and HAVE_DOT options are set to YES then
1683
+
# doxygen will generate a call dependency graph for every global function
1684
+
# or class method. Note that enabling this option will significantly increase
1685
+
# the time of a run. So in most cases it will be better to enable call graphs
1686
+
# for selected functions only using the \callgraph command.
1687
+
1688
+
CALL_GRAPH = NO
1689
+
1690
+
# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then
1691
+
# doxygen will generate a caller dependency graph for every global function
1692
+
# or class method. Note that enabling this option will significantly increase
1693
+
# the time of a run. So in most cases it will be better to enable caller
1694
+
# graphs for selected functions only using the \callergraph command.
1695
+
1696
+
CALLER_GRAPH = NO
1697
+
1698
+
# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1699
+
# will generate a graphical hierarchy of all classes instead of a textual one.
1700
+
1701
+
GRAPHICAL_HIERARCHY = YES
1702
+
1703
+
# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
1704
+
# then doxygen will show the dependencies a directory has on other directories
1705
+
# in a graphical way. The dependency relations are determined by the #include
1706
+
# relations between the files in the directories.
1707
+
1708
+
DIRECTORY_GRAPH = YES
1709
+
1710
+
# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1711
+
# generated by dot. Possible values are svg, png, jpg, or gif.
1712
+
# If left blank png will be used. If you choose svg you need to set
1713
+
# HTML_FILE_EXTENSION to xhtml in order to make the SVG files
1714
+
# visible in IE 9+ (other browsers do not have this requirement).
1715
+
1716
+
DOT_IMAGE_FORMAT = png
1717
+
1718
+
# If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
1719
+
# enable generation of interactive SVG images that allow zooming and panning.
1720
+
# Note that this requires a modern browser other than Internet Explorer.
1721
+
# Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you
1722
+
# need to set HTML_FILE_EXTENSION to xhtml in order to make the SVG files
1723
+
# visible. Older versions of IE do not have SVG support.
1724
+
1725
+
INTERACTIVE_SVG = NO
1726
+
1727
+
# The tag DOT_PATH can be used to specify the path where the dot tool can be
1728
+
# found. If left blank, it is assumed the dot tool can be found in the path.
1729
+
1730
+
DOT_PATH =
1731
+
1732
+
# The DOTFILE_DIRS tag can be used to specify one or more directories that
1733
+
# contain dot files that are included in the documentation (see the
1734
+
# \dotfile command).
1735
+
1736
+
DOTFILE_DIRS =
1737
+
1738
+
# The MSCFILE_DIRS tag can be used to specify one or more directories that
1739
+
# contain msc files that are included in the documentation (see the
1740
+
# \mscfile command).
1741
+
1742
+
MSCFILE_DIRS =
1743
+
1744
+
# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
1745
+
# nodes that will be shown in the graph. If the number of nodes in a graph
1746
+
# becomes larger than this value, doxygen will truncate the graph, which is
1747
+
# visualized by representing a node as a red box. Note that doxygen if the
1748
+
# number of direct children of the root node in a graph is already larger than
1749
+
# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
1750
+
# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
1751
+
1752
+
DOT_GRAPH_MAX_NODES = 50
1753
+
1754
+
# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1755
+
# graphs generated by dot. A depth value of 3 means that only nodes reachable
1756
+
# from the root by following a path via at most 3 edges will be shown. Nodes
1757
+
# that lay further from the root node will be omitted. Note that setting this
1758
+
# option to 1 or 2 may greatly reduce the computation time needed for large
1759
+
# code bases. Also note that the size of a graph can be further restricted by
1760
+
# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
1761
+
1762
+
MAX_DOT_GRAPH_DEPTH = 0
1763
+
1764
+
# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1765
+
# background. This is disabled by default, because dot on Windows does not
1766
+
# seem to support this out of the box. Warning: Depending on the platform used,
1767
+
# enabling this option may lead to badly anti-aliased labels on the edges of
1768
+
# a graph (i.e. they become hard to read).
1769
+
1770
+
DOT_TRANSPARENT = NO
1771
+
1772
+
# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
1773
+
# files in one run (i.e. multiple -o and -T options on the command line). This
1774
+
# makes dot run faster, but since only newer versions of dot (>1.8.10)
1775
+
# support this, this feature is disabled by default.
1776
+
1777
+
DOT_MULTI_TARGETS = NO
1778
+
1779
+
# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1780
+
# generate a legend page explaining the meaning of the various boxes and
1781
+
# arrows in the dot generated graphs.
1782
+
1783
+
GENERATE_LEGEND = YES
1784
+
1785
+
# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1786
+
# remove the intermediate dot files that are used to generate
1787
+
# the various graphs.
1788
+
1789
+
DOT_CLEANUP = YES
+6
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/BaseDoxyfile.txt.meta
+6
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/BaseDoxyfile.txt.meta
+9
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/DarkTheme.meta
+9
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/DarkTheme.meta
+586
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/DarkTheme/doxygen.css
+586
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/DarkTheme/doxygen.css
···
1
+
/* The A Dark and Colorful CSS for doxygen
2
+
by JacobPennock.com
3
+
*/
4
+
5
+
body, table, div, p, dl {
6
+
font-family: Lucida Grande, Verdana, Geneva, Arial, sans-serif;
7
+
font-size: 12px;
8
+
}
9
+
10
+
.title {
11
+
font-size: 150%;
12
+
font-weight: 700;
13
+
margin: 10px 2px;
14
+
}
15
+
16
+
p, div, dl {
17
+
color:#75715E;
18
+
}
19
+
20
+
div.contents p {
21
+
22
+
font-family:Lucida Grande, Verdana, Geneva, Arial, sans-serif;
23
+
24
+
}
25
+
26
+
/* @group Heading Levels */
27
+
28
+
h1 {
29
+
margin-bottom: 10px;
30
+
font-size: 30px;
31
+
padding: 0px 0px 20px 0px ;
32
+
33
+
border-bottom:1px dotted #75715E;
34
+
}
35
+
36
+
h2 {
37
+
padding-top: 30px;
38
+
font-size: 17px;
39
+
color:#f964aa;
40
+
font-family: Lucida Grande, Verdana, Geneva, Arial, sans-serif;
41
+
}
42
+
43
+
h3 {
44
+
font-size: 17px;
45
+
font-family: Lucida Grande, Verdana, Geneva, Arial, sans-serif;
46
+
}
47
+
48
+
dt {
49
+
font-weight: bold;
50
+
}
51
+
52
+
div.multicol {
53
+
-moz-column-gap: 1em;
54
+
-webkit-column-gap: 1em;
55
+
-moz-column-count: 3;
56
+
-webkit-column-count: 3;
57
+
}
58
+
59
+
p.startli, p.startdd, p.starttd {
60
+
margin-top: 2px;
61
+
}
62
+
63
+
p.endli {
64
+
margin-bottom: 0px;
65
+
}
66
+
67
+
p.enddd {
68
+
margin-bottom: 4px;
69
+
}
70
+
71
+
p.endtd {
72
+
margin-bottom: 2px;
73
+
}
74
+
75
+
/* @end */
76
+
77
+
caption {
78
+
font-weight: bold;
79
+
}
80
+
81
+
span.legend {
82
+
font-size: 70%;
83
+
text-align: center;
84
+
}
85
+
86
+
h3.version {
87
+
font-size: 90%;
88
+
padding-bottom:10px;
89
+
border-bottom:1px dotted #75715E;
90
+
}
91
+
92
+
div.qindex, div.navtab{
93
+
background-color: #3C4244;
94
+
border: 1px dotted #75715E;
95
+
text-align: center;
96
+
margin: 2px;
97
+
padding: 2px;
98
+
}
99
+
100
+
div.qindex, div.navpath {
101
+
width: 100%;
102
+
line-height: 140%;
103
+
}
104
+
105
+
div.navtab {
106
+
margin-right: 15px;
107
+
}
108
+
109
+
/* @group Link Styling */
110
+
111
+
a {
112
+
color: #9cccd5;
113
+
font-weight: normal;
114
+
text-decoration: none;
115
+
}
116
+
117
+
.contents a:visited {
118
+
color: #66D9EF;
119
+
}
120
+
121
+
a:hover {
122
+
text-decoration: underline;
123
+
}
124
+
125
+
a.qindex {
126
+
font-weight: bold;
127
+
}
128
+
129
+
a.qindexHL {
130
+
font-weight: bold;
131
+
background-color: #6666cc;
132
+
color: #ffffff;
133
+
border: 1px double #9295C2;
134
+
}
135
+
136
+
.contents a.qindexHL:visited {
137
+
color: #ffffff;
138
+
}
139
+
140
+
a.el {
141
+
font-weight: bold;
142
+
}
143
+
144
+
a.elRef {
145
+
}
146
+
147
+
a.code {
148
+
color: #9cccd5;
149
+
}
150
+
151
+
a.codeRef {
152
+
color: #9cccd5;
153
+
}
154
+
155
+
/* @end */
156
+
157
+
dl.el {
158
+
margin-left: -1cm;
159
+
}
160
+
161
+
.fragment {
162
+
font-family: monospace, fixed;
163
+
font-size: 105%;
164
+
}
165
+
166
+
pre.fragment {
167
+
border: 1px dashed #595959;
168
+
background-color: #252525;
169
+
padding: 4px 6px;
170
+
margin: 4px 8px 4px 2px;
171
+
overflow: auto;
172
+
word-wrap: break-word;
173
+
font-size: 9pt;
174
+
line-height: 125%;
175
+
}
176
+
177
+
div.ah {
178
+
background-color: black;
179
+
font-weight: bold;
180
+
color: #ffffff;
181
+
margin-bottom: 3px;
182
+
margin-top: 3px
183
+
}
184
+
185
+
div.groupHeader {
186
+
margin-left: 16px;
187
+
margin-top: 12px;
188
+
margin-bottom: 6px;
189
+
font-weight: bold;
190
+
}
191
+
192
+
div.groupText {
193
+
margin-left: 16px;
194
+
font-style: italic;
195
+
}
196
+
197
+
body {
198
+
background: #272822;
199
+
color: #ffffff;
200
+
margin-right: 20px;
201
+
margin-left: 20px;
202
+
}
203
+
204
+
td.indexkey {
205
+
background-color: #272822;
206
+
font-weight: bold;
207
+
border: 1px dotted #75715E;
208
+
margin: 2px 0px 2px 0;
209
+
padding: 2px 10px;
210
+
}
211
+
212
+
td.indexvalue {
213
+
background-color: #272822;
214
+
border: 1px dotted #75715E;
215
+
padding: 14px 10px;
216
+
margin: 2px 0px;
217
+
}
218
+
219
+
tr.memlist {
220
+
background-color: #f0f0f0;
221
+
}
222
+
223
+
p.formulaDsp {
224
+
text-align: center;
225
+
}
226
+
227
+
img.formulaDsp {
228
+
229
+
}
230
+
231
+
img.formulaInl {
232
+
vertical-align: middle;
233
+
}
234
+
235
+
div.center {
236
+
text-align: center;
237
+
margin-top: 0px;
238
+
margin-bottom: 0px;
239
+
padding: 0px;
240
+
}
241
+
242
+
div.center img {
243
+
border: 0px;
244
+
}
245
+
246
+
img.footer {
247
+
border: 0px;
248
+
vertical-align: middle;
249
+
}
250
+
251
+
/* @group Code Colorization */
252
+
253
+
span.keyword {
254
+
color: #008000
255
+
}
256
+
257
+
span.keywordtype {
258
+
color: #604020
259
+
}
260
+
261
+
span.keywordflow {
262
+
color: #e08000
263
+
}
264
+
265
+
span.comment {
266
+
color: #F964AA
267
+
}
268
+
269
+
span.preprocessor {
270
+
color: #806020
271
+
}
272
+
273
+
span.stringliteral {
274
+
color: #002080
275
+
}
276
+
277
+
span.charliteral {
278
+
color: #008080
279
+
}
280
+
281
+
span.vhdldigit {
282
+
color: #ff00ff
283
+
}
284
+
285
+
span.vhdlchar {
286
+
color: #000000
287
+
}
288
+
289
+
span.vhdlkeyword {
290
+
color: #700070
291
+
}
292
+
293
+
span.vhdllogic {
294
+
color: #ff0000
295
+
}
296
+
297
+
/* @end */
298
+
299
+
.search {
300
+
color: #003399;
301
+
font-weight: bold;
302
+
}
303
+
304
+
form.search {
305
+
margin-bottom: 0px;
306
+
margin-top: 0px;
307
+
}
308
+
309
+
input.search {
310
+
font-size: 75%;
311
+
color: #000080;
312
+
font-weight: normal;
313
+
background-color: #F1F5F9;
314
+
}
315
+
316
+
td.tiny {
317
+
font-size: 75%;
318
+
}
319
+
320
+
.dirtab {
321
+
padding: 4px;
322
+
border-collapse: collapse;
323
+
border: 1px solid #84b0c7;
324
+
}
325
+
326
+
th.dirtab {
327
+
background: #F1F5F9;
328
+
font-weight: bold;
329
+
}
330
+
331
+
hr {
332
+
height: 0;
333
+
border: none;
334
+
border-top: 1px solid #666;
335
+
}
336
+
337
+
/* @group Member Descriptions */
338
+
339
+
.mdescLeft, .mdescRight,
340
+
.memItemLeft, .memItemRight,
341
+
.memTemplItemLeft, .memTemplItemRight, .memTemplParams {
342
+
background-color: #272822;
343
+
border: none;
344
+
margin: 4px;
345
+
padding: 1px 0 0 8px;
346
+
}
347
+
348
+
.mdescLeft, .mdescRight {
349
+
padding: 0px 8px 4px 8px;
350
+
color: #cbcbc8;
351
+
}
352
+
353
+
.memItemLeft, .memItemRight, .memTemplParams {
354
+
border-top: 1px solid #75715E;
355
+
color: #CD87FF;
356
+
background-color: #272822;
357
+
padding: 10px 0 0 8px;
358
+
}
359
+
360
+
.memItemLeft, .memTemplItemLeft {
361
+
color: #9cccd5;
362
+
white-space: nowrap;
363
+
}
364
+
365
+
.memItemRight a {
366
+
color: #9FC74F;
367
+
}
368
+
369
+
.memItemRight a:visited {
370
+
color: #9FC74F;
371
+
}
372
+
373
+
.memTemplParams {
374
+
white-space: nowrap;
375
+
}
376
+
377
+
/* @end */
378
+
379
+
/* @group Member Details */
380
+
381
+
/* Styles for detailed member documentation */
382
+
383
+
.memtemplate {
384
+
font-size: 80%;
385
+
color: #606060;
386
+
font-weight: normal;
387
+
margin-left: 3px;
388
+
}
389
+
390
+
.memnav {
391
+
background-color: #F1F5F9;
392
+
border: 1px solid #84b0c7;
393
+
text-align: center;
394
+
margin: 2px;
395
+
margin-right: 15px;
396
+
padding: 2px;
397
+
}
398
+
399
+
.memitem {
400
+
padding: 0;
401
+
margin-bottom: 30px;
402
+
}
403
+
404
+
.memname {
405
+
white-space: nowrap;
406
+
font-weight: bold;
407
+
color:#A6E22E;
408
+
padding:3px 5px;
409
+
}
410
+
411
+
.memproto, .memdoc {
412
+
border: 1px dotted #75715E;
413
+
}
414
+
415
+
.memproto {
416
+
padding: 0;
417
+
background-color:#3c4244;
418
+
font-weight: bold;
419
+
-webkit-box-shadow: 5px 5px 5px rgba(0, 0, 0, 0.15);
420
+
-moz-box-shadow: rgba(0, 0, 0, 0.15) 5px 5px 5px;
421
+
422
+
}
423
+
424
+
.memdoc {
425
+
padding: 2px 20px 20px;
426
+
background-color: #272822;
427
+
border-top-width: 0;
428
+
-webkit-box-shadow: 5px 5px 5px rgba(0, 0, 0, 0.15);
429
+
-moz-box-shadow: rgba(0, 0, 0, 0.15) 5px 5px 5px;
430
+
}
431
+
432
+
.paramkey {
433
+
text-align: right;
434
+
}
435
+
436
+
.paramtype {
437
+
white-space: nowrap;
438
+
}
439
+
440
+
.paramname {
441
+
color: #FD971F;
442
+
white-space: nowrap;
443
+
}
444
+
.paramname em {
445
+
font-style: normal;
446
+
}
447
+
448
+
/* @end */
449
+
450
+
/* @group Directory (tree) */
451
+
452
+
/* for the tree view */
453
+
454
+
.ftvtree {
455
+
font-family: sans-serif;
456
+
margin: 0.5em;
457
+
}
458
+
459
+
/* these are for tree view when used as main index */
460
+
461
+
.directory {
462
+
font-size: 9pt;
463
+
font-weight: bold;
464
+
}
465
+
466
+
.directory h3 {
467
+
margin: 0px;
468
+
margin-top: 1em;
469
+
font-size: 11pt;
470
+
}
471
+
472
+
/*
473
+
The following two styles can be used to replace the root node title
474
+
with an image of your choice. Simply uncomment the next two styles,
475
+
specify the name of your image and be sure to set 'height' to the
476
+
proper pixel height of your image.
477
+
*/
478
+
479
+
/*
480
+
.directory h3.swap {
481
+
height: 61px;
482
+
background-repeat: no-repeat;
483
+
background-image: url("yourimage.gif");
484
+
}
485
+
.directory h3.swap span {
486
+
display: none;
487
+
}
488
+
*/
489
+
490
+
.directory > h3 {
491
+
margin-top: 0;
492
+
}
493
+
494
+
.directory p {
495
+
margin: 0px;
496
+
white-space: nowrap;
497
+
}
498
+
499
+
.directory div {
500
+
display: none;
501
+
margin: 0px;
502
+
}
503
+
504
+
.directory img {
505
+
vertical-align: -30%;
506
+
}
507
+
508
+
/* these are for tree view when not used as main index */
509
+
510
+
.directory-alt {
511
+
font-size: 100%;
512
+
font-weight: bold;
513
+
}
514
+
515
+
.directory-alt h3 {
516
+
margin: 0px;
517
+
margin-top: 1em;
518
+
font-size: 11pt;
519
+
}
520
+
521
+
.directory-alt > h3 {
522
+
margin-top: 0;
523
+
}
524
+
525
+
.directory-alt p {
526
+
margin: 0px;
527
+
white-space: nowrap;
528
+
}
529
+
530
+
.directory-alt div {
531
+
display: none;
532
+
margin: 0px;
533
+
}
534
+
535
+
.directory-alt img {
536
+
vertical-align: -30%;
537
+
}
538
+
539
+
/* @end */
540
+
541
+
address {
542
+
font-style: normal;
543
+
color: #333;
544
+
}
545
+
546
+
table.doxtable {
547
+
border-collapse:collapse;
548
+
}
549
+
550
+
table.doxtable td, table.doxtable th {
551
+
border: 1px solid #153788;
552
+
padding: 3px 7px 2px;
553
+
}
554
+
555
+
table.doxtable th {
556
+
background-color: #254798;
557
+
color: #FFFFFF;
558
+
font-size: 110%;
559
+
padding-bottom: 4px;
560
+
padding-top: 5px;
561
+
text-align:left;
562
+
}
563
+
564
+
565
+
hr {
566
+
border-top:0px dotted #75715E;
567
+
border-bottom:0px dotted #75715E;
568
+
margin-top:30px;
569
+
padding-top:10px;
570
+
}
571
+
572
+
h1 {
573
+
margin-top:0;
574
+
}
575
+
.contents .dynsection {
576
+
margin-top:10px;
577
+
}
578
+
579
+
#projectname
580
+
{
581
+
font: 300% Tahoma, Arial,sans-serif;
582
+
/*font: 1.4em "arial", sans-serif;*/
583
+
letter-spacing: -0.04em;
584
+
margin-bottom: 0px;
585
+
text-transform: uppercase;
586
+
}
+6
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/DarkTheme/doxygen.css.meta
+6
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/DarkTheme/doxygen.css.meta
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/DarkTheme/img_downArrow.png
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/DarkTheme/img_downArrow.png
This is a binary file and will not be displayed.
+53
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/DarkTheme/img_downArrow.png.meta
+53
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/DarkTheme/img_downArrow.png.meta
···
1
+
fileFormatVersion: 2
2
+
guid: f3e8f711b1840f042be7d05ea9959d53
3
+
TextureImporter:
4
+
fileIDToRecycleName: {}
5
+
serializedVersion: 2
6
+
mipmaps:
7
+
mipMapMode: 0
8
+
enableMipMap: 1
9
+
linearTexture: 0
10
+
correctGamma: 0
11
+
fadeOut: 0
12
+
borderMipMap: 0
13
+
mipMapFadeDistanceStart: 1
14
+
mipMapFadeDistanceEnd: 3
15
+
bumpmap:
16
+
convertToNormalMap: 0
17
+
externalNormalMap: 0
18
+
heightScale: .25
19
+
normalMapFilter: 0
20
+
isReadable: 0
21
+
grayScaleToAlpha: 0
22
+
generateCubemap: 0
23
+
cubemapConvolution: 0
24
+
cubemapConvolutionSteps: 8
25
+
cubemapConvolutionExponent: 1.5
26
+
seamlessCubemap: 0
27
+
textureFormat: -1
28
+
maxTextureSize: 1024
29
+
textureSettings:
30
+
filterMode: -1
31
+
aniso: -1
32
+
mipBias: -1
33
+
wrapMode: -1
34
+
nPOTScale: 1
35
+
lightmap: 0
36
+
rGBM: 0
37
+
compressionQuality: 50
38
+
spriteMode: 0
39
+
spriteExtrude: 1
40
+
spriteMeshType: 1
41
+
alignment: 0
42
+
spritePivot: {x: .5, y: .5}
43
+
spriteBorder: {x: 0, y: 0, z: 0, w: 0}
44
+
spritePixelsToUnits: 100
45
+
alphaIsTransparency: 0
46
+
textureType: -1
47
+
buildTargetSettings: []
48
+
spriteSheet:
49
+
sprites: []
50
+
spritePackingTag:
51
+
userData:
52
+
assetBundleName:
53
+
assetBundleVariant:
+141
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/DarkTheme/tabs.css
+141
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/DarkTheme/tabs.css
···
1
+
.tabs, .tabs2, .tabs3 {
2
+
width: 100%;
3
+
z-index: 101;
4
+
font-size: 13px;
5
+
}
6
+
7
+
div.navigation {
8
+
display:block;
9
+
float:left;
10
+
clear:both;
11
+
width:100%;
12
+
padding-top:10px;
13
+
padding-bottom:30px;
14
+
border-bottom:1px dotted #E0E0E0;
15
+
height: 60px;
16
+
}
17
+
18
+
div.contents {
19
+
float:left;
20
+
clear:both;
21
+
22
+
}
23
+
24
+
address {
25
+
display:none;
26
+
}
27
+
28
+
DIV.tabs
29
+
{
30
+
float : left;
31
+
width : 100%;
32
+
margin-bottom : 4px;
33
+
}
34
+
35
+
DIV.tabs UL
36
+
{
37
+
margin : 0px;
38
+
padding-left : 0px;
39
+
list-style : none;
40
+
}
41
+
42
+
DIV.tabs LI, DIV.tabs FORM
43
+
{
44
+
display : inline;
45
+
margin : 0px;
46
+
padding : 0px;
47
+
background-color:#3C4244;
48
+
}
49
+
50
+
DIV.tabs FORM
51
+
{
52
+
float : right;
53
+
}
54
+
55
+
DIV.tabs A
56
+
{
57
+
float : left;
58
+
font-size : 80%;
59
+
font-weight : bold;
60
+
text-decoration : none;
61
+
}
62
+
63
+
DIV.tabs A:hover
64
+
{
65
+
background-position: 100% -150px;
66
+
}
67
+
68
+
DIV.tabs A:link, DIV.tabs A:visited,
69
+
DIV.tabs A:active, DIV.tabs A:hover
70
+
{
71
+
color: #9cccd5;
72
+
}
73
+
74
+
DIV.tabs SPAN
75
+
{
76
+
float : left;
77
+
display : block;
78
+
padding : 5px 9px;
79
+
white-space : nowrap;
80
+
text-transform: uppercase;
81
+
font: 1.4em "arial", sans-serif;
82
+
letter-spacing: -0.04em;
83
+
margin-bottom: 0px;
84
+
border-top:1px dotted #75715E;
85
+
/*border-bottom:1px dotted #75715E;*/
86
+
}
87
+
88
+
DIV.tabs #MSearchBox
89
+
{
90
+
float : right;
91
+
display : inline;
92
+
font-size : 1em;
93
+
background-color:#3C4244;
94
+
}
95
+
96
+
DIV.tabs TD
97
+
{
98
+
font-size : 80%;
99
+
font-weight : bold;
100
+
text-decoration : none;
101
+
}
102
+
103
+
104
+
105
+
/* Commented Backslash Hack hides rule from IE5-Mac \*/
106
+
DIV.tabs SPAN {float : none;}
107
+
/* End IE5-Mac hack */
108
+
109
+
DIV.tabs A:hover SPAN
110
+
{
111
+
background-position: 0% -150px;
112
+
113
+
}
114
+
115
+
DIV.tabs LI.current A
116
+
{
117
+
background-position: 100% -150px;
118
+
border-width : 0px;
119
+
background-color: #272822;
120
+
background: #272822 url(img_downArrow.png) center top no-repeat;
121
+
text-transform: uppercase;
122
+
font: 1.4em "arial", sans-serif;
123
+
letter-spacing: -0.04em;
124
+
margin-bottom: 0px;
125
+
}
126
+
127
+
DIV.tabs LI.current SPAN
128
+
{
129
+
background-position: 0% -150px;
130
+
padding-bottom : 6px;
131
+
}
132
+
133
+
DIV.navpath
134
+
{
135
+
background : none;
136
+
border : none;
137
+
border-bottom : 1px solid #84B0C7;
138
+
text-align : center;
139
+
margin : 2px;
140
+
padding : 2px;
141
+
}
+6
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/DarkTheme/tabs.css.meta
+6
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/DarkTheme/tabs.css.meta
+9
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/LightTheme.meta
+9
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/LightTheme.meta
+566
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/LightTheme/doxygen.css
+566
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/LightTheme/doxygen.css
···
1
+
/* The standard CSS for doxygen
2
+
3
+
modified by RossCairns.com
4
+
*/
5
+
6
+
body, table, div, p, dl {
7
+
font-family: Lucida Grande, Verdana, Geneva, Arial, sans-serif;
8
+
font-size: 12px;
9
+
}
10
+
11
+
p, div, dl {
12
+
color:#3E3E3E;
13
+
}
14
+
15
+
div.contents p {
16
+
17
+
font-family:Monaco, courier;
18
+
19
+
}
20
+
21
+
/* @group Heading Levels */
22
+
23
+
h1 {
24
+
margin-bottom: 10px;
25
+
font-size: 30px;
26
+
padding: 0px 0px 20px 0px ;
27
+
28
+
border-bottom:1px dotted #E0E0E0;
29
+
}
30
+
31
+
h2 {
32
+
padding-top: 30px;
33
+
font-size: 17px;
34
+
color:#42657B;
35
+
font-family: Lucida Grande, Verdana, Geneva, Arial, sans-serif;
36
+
}
37
+
38
+
h3 {
39
+
font-size: 17px;
40
+
font-family: Lucida Grande, Verdana, Geneva, Arial, sans-serif;
41
+
}
42
+
43
+
dt {
44
+
font-weight: bold;
45
+
}
46
+
47
+
div.multicol {
48
+
-moz-column-gap: 1em;
49
+
-webkit-column-gap: 1em;
50
+
-moz-column-count: 3;
51
+
-webkit-column-count: 3;
52
+
}
53
+
54
+
p.startli, p.startdd, p.starttd {
55
+
margin-top: 2px;
56
+
}
57
+
58
+
p.endli {
59
+
margin-bottom: 0px;
60
+
}
61
+
62
+
p.enddd {
63
+
margin-bottom: 4px;
64
+
}
65
+
66
+
p.endtd {
67
+
margin-bottom: 2px;
68
+
}
69
+
70
+
/* @end */
71
+
72
+
caption {
73
+
font-weight: bold;
74
+
}
75
+
76
+
span.legend {
77
+
font-size: 70%;
78
+
text-align: center;
79
+
}
80
+
81
+
h3.version {
82
+
font-size: 90%;
83
+
padding-bottom:10px;
84
+
border-bottom:1px dotted #E0E0E0;
85
+
}
86
+
87
+
div.qindex, div.navtab{
88
+
background-color: #e8eef2;
89
+
border: 1px solid #84b0c7;
90
+
text-align: center;
91
+
margin: 2px;
92
+
padding: 2px;
93
+
}
94
+
95
+
div.qindex, div.navpath {
96
+
width: 100%;
97
+
line-height: 140%;
98
+
}
99
+
100
+
div.navtab {
101
+
margin-right: 15px;
102
+
}
103
+
104
+
/* @group Link Styling */
105
+
106
+
a {
107
+
color: #153788;
108
+
font-weight: normal;
109
+
text-decoration: none;
110
+
}
111
+
112
+
.contents a:visited {
113
+
color: #1b77c5;
114
+
}
115
+
116
+
a:hover {
117
+
text-decoration: underline;
118
+
}
119
+
120
+
a.qindex {
121
+
font-weight: bold;
122
+
}
123
+
124
+
a.qindexHL {
125
+
font-weight: bold;
126
+
background-color: #6666cc;
127
+
color: #ffffff;
128
+
border: 1px double #9295C2;
129
+
}
130
+
131
+
.contents a.qindexHL:visited {
132
+
color: #ffffff;
133
+
}
134
+
135
+
a.el {
136
+
font-weight: bold;
137
+
}
138
+
139
+
a.elRef {
140
+
}
141
+
142
+
a.code {
143
+
color: #3030f0;
144
+
}
145
+
146
+
a.codeRef {
147
+
color: #3030f0;
148
+
}
149
+
150
+
/* @end */
151
+
152
+
dl.el {
153
+
margin-left: -1cm;
154
+
}
155
+
156
+
.fragment {
157
+
font-family: monospace, fixed;
158
+
font-size: 105%;
159
+
}
160
+
161
+
pre.fragment {
162
+
border: 1px solid #CCCCCC;
163
+
background-color: #f5f5f5;
164
+
padding: 4px 6px;
165
+
margin: 4px 8px 4px 2px;
166
+
overflow: auto;
167
+
word-wrap: break-word;
168
+
font-size: 9pt;
169
+
line-height: 125%;
170
+
}
171
+
172
+
div.ah {
173
+
background-color: black;
174
+
font-weight: bold;
175
+
color: #ffffff;
176
+
margin-bottom: 3px;
177
+
margin-top: 3px
178
+
}
179
+
180
+
div.groupHeader {
181
+
margin-left: 16px;
182
+
margin-top: 12px;
183
+
margin-bottom: 6px;
184
+
font-weight: bold;
185
+
}
186
+
187
+
div.groupText {
188
+
margin-left: 16px;
189
+
font-style: italic;
190
+
}
191
+
192
+
body {
193
+
background: white;
194
+
color: black;
195
+
margin-right: 20px;
196
+
margin-left: 20px;
197
+
}
198
+
199
+
td.indexkey {
200
+
background-color: #F1F5F9;
201
+
font-weight: bold;
202
+
border: 1px solid #CCCCCC;
203
+
margin: 2px 0px 2px 0;
204
+
padding: 2px 10px;
205
+
}
206
+
207
+
td.indexvalue {
208
+
background-color: #F1F5F9;
209
+
border: 1px solid #CCCCCC;
210
+
padding: 2px 10px;
211
+
margin: 2px 0px;
212
+
}
213
+
214
+
tr.memlist {
215
+
background-color: #f0f0f0;
216
+
}
217
+
218
+
p.formulaDsp {
219
+
text-align: center;
220
+
}
221
+
222
+
img.formulaDsp {
223
+
224
+
}
225
+
226
+
img.formulaInl {
227
+
vertical-align: middle;
228
+
}
229
+
230
+
div.center {
231
+
text-align: center;
232
+
margin-top: 0px;
233
+
margin-bottom: 0px;
234
+
padding: 0px;
235
+
}
236
+
237
+
div.center img {
238
+
border: 0px;
239
+
}
240
+
241
+
img.footer {
242
+
border: 0px;
243
+
vertical-align: middle;
244
+
}
245
+
246
+
/* @group Code Colorization */
247
+
248
+
span.keyword {
249
+
color: #008000
250
+
}
251
+
252
+
span.keywordtype {
253
+
color: #604020
254
+
}
255
+
256
+
span.keywordflow {
257
+
color: #e08000
258
+
}
259
+
260
+
span.comment {
261
+
color: #800000
262
+
}
263
+
264
+
span.preprocessor {
265
+
color: #806020
266
+
}
267
+
268
+
span.stringliteral {
269
+
color: #002080
270
+
}
271
+
272
+
span.charliteral {
273
+
color: #008080
274
+
}
275
+
276
+
span.vhdldigit {
277
+
color: #ff00ff
278
+
}
279
+
280
+
span.vhdlchar {
281
+
color: #000000
282
+
}
283
+
284
+
span.vhdlkeyword {
285
+
color: #700070
286
+
}
287
+
288
+
span.vhdllogic {
289
+
color: #ff0000
290
+
}
291
+
292
+
/* @end */
293
+
294
+
.search {
295
+
color: #003399;
296
+
font-weight: bold;
297
+
}
298
+
299
+
form.search {
300
+
margin-bottom: 0px;
301
+
margin-top: 0px;
302
+
}
303
+
304
+
input.search {
305
+
font-size: 75%;
306
+
color: #000080;
307
+
font-weight: normal;
308
+
background-color: #F1F5F9;
309
+
}
310
+
311
+
td.tiny {
312
+
font-size: 75%;
313
+
}
314
+
315
+
.dirtab {
316
+
padding: 4px;
317
+
border-collapse: collapse;
318
+
border: 1px solid #84b0c7;
319
+
}
320
+
321
+
th.dirtab {
322
+
background: #F1F5F9;
323
+
font-weight: bold;
324
+
}
325
+
326
+
hr {
327
+
height: 0;
328
+
border: none;
329
+
border-top: 1px solid #666;
330
+
}
331
+
332
+
/* @group Member Descriptions */
333
+
334
+
.mdescLeft, .mdescRight,
335
+
.memItemLeft, .memItemRight,
336
+
.memTemplItemLeft, .memTemplItemRight, .memTemplParams {
337
+
background-color: #FAFAFA;
338
+
border: none;
339
+
margin: 4px;
340
+
padding: 1px 0 0 8px;
341
+
}
342
+
343
+
.mdescLeft, .mdescRight {
344
+
padding: 0px 8px 4px 8px;
345
+
color: #555;
346
+
}
347
+
348
+
.memItemLeft, .memItemRight, .memTemplParams {
349
+
border-top: 1px solid #ccc;
350
+
background-color: #F9F9F9;
351
+
}
352
+
353
+
.memItemLeft, .memTemplItemLeft {
354
+
white-space: nowrap;
355
+
}
356
+
357
+
.memTemplParams {
358
+
color: #606060;
359
+
white-space: nowrap;
360
+
}
361
+
362
+
/* @end */
363
+
364
+
/* @group Member Details */
365
+
366
+
/* Styles for detailed member documentation */
367
+
368
+
.memtemplate {
369
+
font-size: 80%;
370
+
color: #606060;
371
+
font-weight: normal;
372
+
margin-left: 3px;
373
+
}
374
+
375
+
.memnav {
376
+
background-color: #F1F5F9;
377
+
border: 1px solid #84b0c7;
378
+
text-align: center;
379
+
margin: 2px;
380
+
margin-right: 15px;
381
+
padding: 2px;
382
+
}
383
+
384
+
.memitem {
385
+
padding: 0;
386
+
margin-bottom: 30px;
387
+
}
388
+
389
+
.memname {
390
+
white-space: nowrap;
391
+
font-weight: bold;
392
+
color:#42657B;
393
+
padding:3px 5px;
394
+
}
395
+
396
+
.memproto, .memdoc {
397
+
border: 1px dotted #E0E0E0;
398
+
}
399
+
400
+
.memproto {
401
+
padding: 0;
402
+
background-color: #F9F9F9;
403
+
font-weight: bold;
404
+
-webkit-box-shadow: 5px 5px 5px rgba(0, 0, 0, 0.15);
405
+
-moz-box-shadow: rgba(0, 0, 0, 0.15) 5px 5px 5px;
406
+
407
+
}
408
+
409
+
.memdoc {
410
+
padding: 2px 20px 20px;
411
+
background-color: #FFFFFF;
412
+
border-top-width: 0;
413
+
-webkit-box-shadow: 5px 5px 5px rgba(0, 0, 0, 0.15);
414
+
-moz-box-shadow: rgba(0, 0, 0, 0.15) 5px 5px 5px;
415
+
}
416
+
417
+
.paramkey {
418
+
text-align: right;
419
+
}
420
+
421
+
.paramtype {
422
+
white-space: nowrap;
423
+
}
424
+
425
+
.paramname {
426
+
color: #885656;
427
+
white-space: nowrap;
428
+
}
429
+
.paramname em {
430
+
font-style: normal;
431
+
}
432
+
433
+
/* @end */
434
+
435
+
/* @group Directory (tree) */
436
+
437
+
/* for the tree view */
438
+
439
+
.ftvtree {
440
+
font-family: sans-serif;
441
+
margin: 0.5em;
442
+
}
443
+
444
+
/* these are for tree view when used as main index */
445
+
446
+
.directory {
447
+
font-size: 9pt;
448
+
font-weight: bold;
449
+
}
450
+
451
+
.directory h3 {
452
+
margin: 0px;
453
+
margin-top: 1em;
454
+
font-size: 11pt;
455
+
}
456
+
457
+
/*
458
+
The following two styles can be used to replace the root node title
459
+
with an image of your choice. Simply uncomment the next two styles,
460
+
specify the name of your image and be sure to set 'height' to the
461
+
proper pixel height of your image.
462
+
*/
463
+
464
+
/*
465
+
.directory h3.swap {
466
+
height: 61px;
467
+
background-repeat: no-repeat;
468
+
background-image: url("yourimage.gif");
469
+
}
470
+
.directory h3.swap span {
471
+
display: none;
472
+
}
473
+
*/
474
+
475
+
.directory > h3 {
476
+
margin-top: 0;
477
+
}
478
+
479
+
.directory p {
480
+
margin: 0px;
481
+
white-space: nowrap;
482
+
}
483
+
484
+
.directory div {
485
+
display: none;
486
+
margin: 0px;
487
+
}
488
+
489
+
.directory img {
490
+
vertical-align: -30%;
491
+
}
492
+
493
+
/* these are for tree view when not used as main index */
494
+
495
+
.directory-alt {
496
+
font-size: 100%;
497
+
font-weight: bold;
498
+
}
499
+
500
+
.directory-alt h3 {
501
+
margin: 0px;
502
+
margin-top: 1em;
503
+
font-size: 11pt;
504
+
}
505
+
506
+
.directory-alt > h3 {
507
+
margin-top: 0;
508
+
}
509
+
510
+
.directory-alt p {
511
+
margin: 0px;
512
+
white-space: nowrap;
513
+
}
514
+
515
+
.directory-alt div {
516
+
display: none;
517
+
margin: 0px;
518
+
}
519
+
520
+
.directory-alt img {
521
+
vertical-align: -30%;
522
+
}
523
+
524
+
/* @end */
525
+
526
+
address {
527
+
font-style: normal;
528
+
color: #333;
529
+
}
530
+
531
+
table.doxtable {
532
+
border-collapse:collapse;
533
+
}
534
+
535
+
table.doxtable td, table.doxtable th {
536
+
border: 1px solid #153788;
537
+
padding: 3px 7px 2px;
538
+
}
539
+
540
+
table.doxtable th {
541
+
background-color: #254798;
542
+
color: #FFFFFF;
543
+
font-size: 110%;
544
+
padding-bottom: 4px;
545
+
padding-top: 5px;
546
+
text-align:left;
547
+
}
548
+
549
+
550
+
hr {
551
+
border-top:1px dotted #E0E0E0;
552
+
border-bottom:1px dotted #E0E0E0;
553
+
margin-top:30px;
554
+
padding-top:10px;
555
+
}
556
+
557
+
.contents {
558
+
padding-top: 30px;
559
+
}
560
+
561
+
h1 {
562
+
margin-top:0;
563
+
}
564
+
.contents .dynsection {
565
+
margin-top:10px;
566
+
}
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/LightTheme/img_downArrow.png
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/LightTheme/img_downArrow.png
This is a binary file and will not be displayed.
+53
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/LightTheme/img_downArrow.png.meta
+53
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/LightTheme/img_downArrow.png.meta
···
1
+
fileFormatVersion: 2
2
+
guid: bf417702d792d0c46940b2f2be78185c
3
+
TextureImporter:
4
+
fileIDToRecycleName: {}
5
+
serializedVersion: 2
6
+
mipmaps:
7
+
mipMapMode: 0
8
+
enableMipMap: 1
9
+
linearTexture: 0
10
+
correctGamma: 0
11
+
fadeOut: 0
12
+
borderMipMap: 0
13
+
mipMapFadeDistanceStart: 1
14
+
mipMapFadeDistanceEnd: 3
15
+
bumpmap:
16
+
convertToNormalMap: 0
17
+
externalNormalMap: 0
18
+
heightScale: .25
19
+
normalMapFilter: 0
20
+
isReadable: 0
21
+
grayScaleToAlpha: 0
22
+
generateCubemap: 0
23
+
cubemapConvolution: 0
24
+
cubemapConvolutionSteps: 8
25
+
cubemapConvolutionExponent: 1.5
26
+
seamlessCubemap: 0
27
+
textureFormat: -1
28
+
maxTextureSize: 1024
29
+
textureSettings:
30
+
filterMode: -1
31
+
aniso: -1
32
+
mipBias: -1
33
+
wrapMode: -1
34
+
nPOTScale: 1
35
+
lightmap: 0
36
+
rGBM: 0
37
+
compressionQuality: 50
38
+
spriteMode: 0
39
+
spriteExtrude: 1
40
+
spriteMeshType: 1
41
+
alignment: 0
42
+
spritePivot: {x: .5, y: .5}
43
+
spriteBorder: {x: 0, y: 0, z: 0, w: 0}
44
+
spritePixelsToUnits: 100
45
+
alphaIsTransparency: 0
46
+
textureType: -1
47
+
buildTargetSettings: []
48
+
spriteSheet:
49
+
sprites: []
50
+
spritePackingTag:
51
+
userData:
52
+
assetBundleName:
53
+
assetBundleVariant:
+128
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/LightTheme/tabs.css
+128
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/LightTheme/tabs.css
···
1
+
/* tabs styles, based on http://www.alistapart.com/articles/slidingdoors */
2
+
3
+
div.navigation {
4
+
display:block;
5
+
float:left;
6
+
clear:both;
7
+
width:100%;
8
+
padding-top:10px;
9
+
padding-bottom:30px;
10
+
border-bottom:1px dotted #E0E0E0;
11
+
height: 60px;
12
+
background:url(background_navigation.png);
13
+
}
14
+
15
+
div.contents {
16
+
float:left;
17
+
clear:both;
18
+
19
+
}
20
+
21
+
address {
22
+
display:none;
23
+
}
24
+
25
+
DIV.tabs
26
+
{
27
+
float : left;
28
+
width : 100%;
29
+
margin-bottom : 4px;
30
+
}
31
+
32
+
DIV.tabs UL
33
+
{
34
+
margin : 0px;
35
+
padding-left : 0px;
36
+
list-style : none;
37
+
}
38
+
39
+
DIV.tabs LI, DIV.tabs FORM
40
+
{
41
+
display : inline;
42
+
margin : 0px;
43
+
padding : 0px;
44
+
background-color:#FFFFFF;
45
+
}
46
+
47
+
DIV.tabs FORM
48
+
{
49
+
float : right;
50
+
}
51
+
52
+
DIV.tabs A
53
+
{
54
+
float : left;
55
+
font-size : 80%;
56
+
font-weight : bold;
57
+
text-decoration : none;
58
+
}
59
+
60
+
DIV.tabs A:hover
61
+
{
62
+
background-position: 100% -150px;
63
+
}
64
+
65
+
DIV.tabs A:link, DIV.tabs A:visited,
66
+
DIV.tabs A:active, DIV.tabs A:hover
67
+
{
68
+
color: #1A419D;
69
+
}
70
+
71
+
DIV.tabs SPAN
72
+
{
73
+
float : left;
74
+
display : block;
75
+
padding : 5px 9px;
76
+
white-space : nowrap;
77
+
border-top:1px dotted #E0E0E0;
78
+
border-bottom:1px dotted #E0E0E0;
79
+
}
80
+
81
+
DIV.tabs #MSearchBox
82
+
{
83
+
float : right;
84
+
display : inline;
85
+
font-size : 1em;
86
+
}
87
+
88
+
DIV.tabs TD
89
+
{
90
+
font-size : 80%;
91
+
font-weight : bold;
92
+
text-decoration : none;
93
+
}
94
+
95
+
96
+
97
+
/* Commented Backslash Hack hides rule from IE5-Mac \*/
98
+
DIV.tabs SPAN {float : none;}
99
+
/* End IE5-Mac hack */
100
+
101
+
DIV.tabs A:hover SPAN
102
+
{
103
+
background-position: 0% -150px;
104
+
}
105
+
106
+
DIV.tabs LI.current A
107
+
{
108
+
background-position: 100% -150px;
109
+
border-width : 0px;
110
+
background-color: #F0F0F0;
111
+
background: #F0F0F0 url(img_downArrow.png) center bottom no-repeat;
112
+
}
113
+
114
+
DIV.tabs LI.current SPAN
115
+
{
116
+
background-position: 0% -150px;
117
+
padding-bottom : 6px;
118
+
}
119
+
120
+
DIV.navpath
121
+
{
122
+
background : none;
123
+
border : none;
124
+
border-bottom : 1px solid #84B0C7;
125
+
text-align : center;
126
+
margin : 2px;
127
+
padding : 2px;
128
+
}
+6
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/LightTheme/tabs.css.meta
+6
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/Resources/LightTheme/tabs.css.meta
+1
-1
Assets/External Libraries/UnityUtilLib/Pooling/BasicPool.cs
+1
-1
Assets/External Libraries/UnityUtilLib/Pooling/BasicPool.cs
+1
-10
Assets/External Libraries/UnityUtilLib/Pooling/IPool.cs
+1
-10
Assets/External Libraries/UnityUtilLib/Pooling/IPool.cs
···
1
-
//------------------------------------------------------------------------------
2
-
// <auto-generated>
3
-
// This code was generated by a tool.
4
-
// Runtime Version:4.0.30319.18063
5
-
//
6
-
// Changes to this file may cause incorrect behavior and will be lost if
7
-
// the code is regenerated.
8
-
// </auto-generated>
9
-
//------------------------------------------------------------------------------
10
1
using System;
11
2
12
-
namespace UnityUtilLib {
3
+
namespace UnityUtilLib.Pooling {
13
4
public interface IPool {
14
5
object Get();
15
6
void Return (object obj);
+2
-10
Assets/External Libraries/UnityUtilLib/Pooling/IPooledObject.cs
+2
-10
Assets/External Libraries/UnityUtilLib/Pooling/IPooledObject.cs
···
1
-
//------------------------------------------------------------------------------
2
-
// <auto-generated>
3
-
// This code was generated by a tool.
4
-
// Runtime Version:4.0.30319.18063
5
-
//
6
-
// Changes to this file may cause incorrect behavior and will be lost if
7
-
// the code is regenerated.
8
-
// </auto-generated>
9
-
//------------------------------------------------------------------------------
10
1
using System;
11
-
namespace UnityUtilLib {
2
+
3
+
namespace UnityUtilLib.Pooling {
12
4
public interface IPooledObject {
13
5
IPool Pool { get; set; }
14
6
bool IsActive { get; }
+1
-1
Assets/External Libraries/UnityUtilLib/Pooling/IPrefabedPool.cs
+1
-1
Assets/External Libraries/UnityUtilLib/Pooling/IPrefabedPool.cs
+1
-1
Assets/External Libraries/UnityUtilLib/Pooling/Pool.cs
+1
-1
Assets/External Libraries/UnityUtilLib/Pooling/Pool.cs
+1
-1
Assets/External Libraries/UnityUtilLib/Pooling/PooledObject.cs
+1
-1
Assets/External Libraries/UnityUtilLib/Pooling/PooledObject.cs
+5
-5
Assets/Scenes/Main Gameplay - Sea.unity
+5
-5
Assets/Scenes/Main Gameplay - Sea.unity
···
296
296
m_GameObject: {fileID: 36195106}
297
297
m_Enabled: 1
298
298
m_EditorHideFlags: 0
299
-
m_Script: {fileID: 11500000, guid: 540ec571544598b45aa142b4cff38dd1, type: 3}
299
+
m_Script: {fileID: 11500000, guid: 9fd7c15c8bef28b4cbe718ddf624796c, type: 3}
300
300
m_Name:
301
301
m_EditorClassIdentifier:
302
302
gameController: {fileID: 787077639}
···
311
311
m_GameObject: {fileID: 36195106}
312
312
m_Enabled: 1
313
313
m_EditorHideFlags: 0
314
-
m_Script: {fileID: 11500000, guid: 540ec571544598b45aa142b4cff38dd1, type: 3}
314
+
m_Script: {fileID: 11500000, guid: 9fd7c15c8bef28b4cbe718ddf624796c, type: 3}
315
315
m_Name:
316
316
m_EditorClassIdentifier:
317
317
gameController: {fileID: 787077639}
···
2599
2599
m_GameObject: {fileID: 1518786336}
2600
2600
m_Enabled: 1
2601
2601
m_EditorHideFlags: 0
2602
-
m_Script: {fileID: 11500000, guid: 5870ca566be46e44d835829dd28776e6, type: 3}
2602
+
m_Script: {fileID: 11500000, guid: 1caa3cd050dcf534dbf0568021c0c20d, type: 3}
2603
2603
m_Name:
2604
2604
m_EditorClassIdentifier:
2605
2605
field: {fileID: 827357119}
2606
-
chargeCapacity: {fileID: 1990498015}
2606
+
chargeCapacity: {fileID: 96955232}
2607
2607
chargeLevel: {fileID: 96955232}
2608
2608
indicator: {fileID: 1559619104}
2609
2609
--- !u!1 &1559619104
···
2973
2973
m_GameObject: {fileID: 1772426189}
2974
2974
m_Enabled: 1
2975
2975
m_EditorHideFlags: 0
2976
-
m_Script: {fileID: 11500000, guid: 5870ca566be46e44d835829dd28776e6, type: 3}
2976
+
m_Script: {fileID: 11500000, guid: 1caa3cd050dcf534dbf0568021c0c20d, type: 3}
2977
2977
m_Name:
2978
2978
m_EditorClassIdentifier:
2979
2979
field: {fileID: 2023493317}
-21
Assets/Scripts/GUI/PlayerLifeIndicator.cs
-21
Assets/Scripts/GUI/PlayerLifeIndicator.cs
···
1
-
using UnityEngine;
2
-
using System.Collections;
3
-
using UnityUtilLib.GUI;
4
-
using Danmaku2D.Phantasmagoria;
5
-
6
-
public class PlayerLifeIndicator : MultiObjectValueIndicator {
7
-
8
-
private PhantasmagoriaGameController gameControl;
9
-
10
-
void Awake() {
11
-
gameControl = (PhantasmagoriaGameController)GameController;
12
-
}
13
-
14
-
protected override int GetMaxValue () {
15
-
return gameControl.MaximumLives;
16
-
}
17
-
18
-
protected override int GetValue () {
19
-
return ((player) ? gameControl.player1 : gameControl.player2).Field.Player.LivesRemaining;
20
-
}
21
-
}
Assets/Scripts/GUI/PlayerLifeIndicator.cs.meta
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/GUI/PlayerLifeIndicator.cs.meta
Assets/Scripts/GUI/PlayerLifeIndicator.cs.meta
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/GUI/PlayerLifeIndicator.cs.meta
-21
Assets/Scripts/GUI/PlayerScoreIndicator.cs
-21
Assets/Scripts/GUI/PlayerScoreIndicator.cs
···
1
-
using UnityEngine;
2
-
using System.Collections;
3
-
using UnityUtilLib.GUI;
4
-
using Danmaku2D.Phantasmagoria;
5
-
6
-
public class PlayerScoreIndicator : MultiObjectValueIndicator {
7
-
8
-
private PhantasmagoriaGameController gameControl;
9
-
10
-
void Awake() {
11
-
gameControl = (PhantasmagoriaGameController)GameController;
12
-
}
13
-
14
-
protected override int GetMaxValue () {
15
-
return gameControl.WinningScore;
16
-
}
17
-
18
-
protected override int GetValue() {
19
-
return ((player) ? gameControl.player1 : gameControl.player2).score;
20
-
}
21
-
}
+3
-1
Assets/Scripts/GUI/PlayerScoreIndicator.cs.meta
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/DoxygenWindow.cs.meta
+3
-1
Assets/Scripts/GUI/PlayerScoreIndicator.cs.meta
Assets/External Libraries/UnityUtilLib/Editor/Doxygen/DoxygenWindow.cs.meta
-47
Assets/Scripts/GUI/RoundTimer.cs
-47
Assets/Scripts/GUI/RoundTimer.cs
···
1
-
using UnityEngine;
2
-
using System.Collections;
3
-
using UnityUtilLib;
4
-
using Danmaku2D.Phantasmagoria;
5
-
6
-
[RequireComponent(typeof(GUIText))]
7
-
public class RoundTimer : MonoBehaviour {
8
-
9
-
[SerializeField]
10
-
private PhantasmagoriaGameController gameController;
11
-
12
-
[SerializeField]
13
-
private Color flashColor;
14
-
15
-
[SerializeField]
16
-
private FrameCounter flashInterval;
17
-
18
-
[SerializeField]
19
-
private float flashThreshold;
20
-
21
-
private Color normalColor;
22
-
private bool flashState;
23
-
private GUIText label;
24
-
25
-
void Start() {
26
-
label = GetComponent<GUIText>();
27
-
normalColor = label.color;
28
-
flashState = false;
29
-
}
30
-
31
-
void Update() {
32
-
int timeSec = Mathf.FloorToInt (gameController.RemainingRoundTime);
33
-
int seconds = timeSec % 60;
34
-
int minutes = timeSec / 60;
35
-
label.text = minutes.ToString ("D2") + ":" + seconds.ToString ("D2");;
36
-
if (timeSec < flashThreshold) {
37
-
if(flashInterval.Tick()) {
38
-
label.color = (flashState) ? flashColor : normalColor;
39
-
flashState = !flashState;
40
-
}
41
-
} else {
42
-
label.color = normalColor;
43
-
flashState = false;
44
-
flashInterval.ForceReady();
45
-
}
46
-
}
47
-
}
Assets/Scripts/GUI/RoundTimer.cs.meta
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/GUI/RoundTimer.cs.meta
Assets/Scripts/GUI/RoundTimer.cs.meta
Assets/External Libraries/DanmakuUnity2D/Phantasmagoria/GUI/RoundTimer.cs.meta
-5
Assets/Scripts/Test.meta
-5
Assets/Scripts/Test.meta
+1789
Docs/Doxyfile
+1789
Docs/Doxyfile
···
1
+
# Doxyfile 1.7.5
2
+
3
+
# This file describes the settings to be used by the documentation system
4
+
# doxygen (www.doxygen.org) for a project
5
+
#
6
+
# All text after a hash (#) is considered a comment and will be ignored
7
+
# The format is:
8
+
# TAG = value [value, ...]
9
+
# For lists items can also be appended using:
10
+
# TAG += value [value, ...]
11
+
# Values that contain spaces should be placed between quotes (" ")
12
+
13
+
#---------------------------------------------------------------------------
14
+
# Project related configuration options
15
+
#---------------------------------------------------------------------------
16
+
17
+
# This tag specifies the encoding used for all characters in the config file
18
+
# that follow. The default is UTF-8 which is also the encoding used for all
19
+
# text before the first occurrence of this tag. Doxygen uses libiconv (or the
20
+
# iconv built into libc) for the transcoding. See
21
+
# http://www.gnu.org/software/libiconv for the list of possible encodings.
22
+
23
+
DOXYFILE_ENCODING = UTF-8
24
+
25
+
# The PROJECT_NAME tag is a single word (or sequence of words) that should
26
+
# identify the project. Note that if you do not use Doxywizard you need
27
+
# to put quotes around the project name if it contains spaces.
28
+
29
+
PROJECT_NAME = "DanmakuUnity2D"
30
+
31
+
# The PROJECT_NUMBER tag can be used to enter a project or revision number.
32
+
# This could be handy for archiving the generated documentation or
33
+
# if some version control system is used.
34
+
35
+
PROJECT_NUMBER = 0.1.0
36
+
37
+
# Using the PROJECT_BRIEF tag one can provide an optional one line description
38
+
# for a project that appears at the top of each page and should give viewer
39
+
# a quick idea about the purpose of the project. Keep the description short.
40
+
41
+
PROJECT_BRIEF = "A Unity Development Kit for 2D Danmaku Games"
42
+
43
+
# With the PROJECT_LOGO tag one can specify an logo or icon that is
44
+
# included in the documentation. The maximum height of the logo should not
45
+
# exceed 55 pixels and the maximum width should not exceed 200 pixels.
46
+
# Doxygen will copy the logo to the output directory.
47
+
48
+
PROJECT_LOGO =
49
+
50
+
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
51
+
# base path where the generated documentation will be put.
52
+
# If a relative path is entered, it will be relative to the location
53
+
# where doxygen was started. If left blank the current directory will be used.
54
+
55
+
OUTPUT_DIRECTORY = "D:/Documents/GitHub/Dogfight/Docs"
56
+
57
+
# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
58
+
# 4096 sub-directories (in 2 levels) under the output directory of each output
59
+
# format and will distribute the generated files over these directories.
60
+
# Enabling this option can be useful when feeding doxygen a huge amount of
61
+
# source files, where putting all generated files in the same directory would
62
+
# otherwise cause performance problems for the file system.
63
+
64
+
CREATE_SUBDIRS = NO
65
+
66
+
# The OUTPUT_LANGUAGE tag is used to specify the language in which all
67
+
# documentation generated by doxygen is written. Doxygen will use this
68
+
# information to generate all constant output in the proper language.
69
+
# The default language is English, other supported languages are:
70
+
# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
71
+
# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,
72
+
# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English
73
+
# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,
74
+
# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak,
75
+
# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
76
+
77
+
OUTPUT_LANGUAGE = English
78
+
79
+
# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
80
+
# include brief member descriptions after the members that are listed in
81
+
# the file and class documentation (similar to JavaDoc).
82
+
# Set to NO to disable this.
83
+
84
+
BRIEF_MEMBER_DESC = YES
85
+
86
+
# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
87
+
# the brief description of a member or function before the detailed description.
88
+
# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
89
+
# brief descriptions will be completely suppressed.
90
+
91
+
REPEAT_BRIEF = YES
92
+
93
+
# This tag implements a quasi-intelligent brief description abbreviator
94
+
# that is used to form the text in various listings. Each string
95
+
# in this list, if found as the leading text of the brief description, will be
96
+
# stripped from the text and the result after processing the whole list, is
97
+
# used as the annotated text. Otherwise, the brief description is used as-is.
98
+
# If left blank, the following values are used ("$name" is automatically
99
+
# replaced with the name of the entity): "The $name class" "The $name widget"
100
+
# "The $name file" "is" "provides" "specifies" "contains"
101
+
# "represents" "a" "an" "the"
102
+
103
+
ABBREVIATE_BRIEF = "The $name class" \
104
+
"The $name widget" \
105
+
"The $name file" \
106
+
is \
107
+
provides \
108
+
specifies \
109
+
contains \
110
+
represents \
111
+
a \
112
+
an \
113
+
the
114
+
115
+
# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
116
+
# Doxygen will generate a detailed section even if there is only a brief
117
+
# description.
118
+
119
+
ALWAYS_DETAILED_SEC = NO
120
+
121
+
# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
122
+
# inherited members of a class in the documentation of that class as if those
123
+
# members were ordinary class members. Constructors, destructors and assignment
124
+
# operators of the base classes will not be shown.
125
+
126
+
INLINE_INHERITED_MEMB = NO
127
+
128
+
# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
129
+
# path before files name in the file list and in the header files. If set
130
+
# to NO the shortest path that makes the file name unique will be used.
131
+
132
+
FULL_PATH_NAMES = YES
133
+
134
+
# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
135
+
# can be used to strip a user-defined part of the path. Stripping is
136
+
# only done if one of the specified strings matches the left-hand part of
137
+
# the path. The tag can be used to show relative paths in the file list.
138
+
# If left blank the directory from which doxygen is run is used as the
139
+
# path to strip.
140
+
141
+
STRIP_FROM_PATH =
142
+
143
+
# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
144
+
# the path mentioned in the documentation of a class, which tells
145
+
# the reader which header file to include in order to use a class.
146
+
# If left blank only the name of the header file containing the class
147
+
# definition is used. Otherwise one should specify the include paths that
148
+
# are normally passed to the compiler using the -I flag.
149
+
150
+
STRIP_FROM_INC_PATH =
151
+
152
+
# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
153
+
# (but less readable) file names. This can be useful if your file system
154
+
# doesn't support long names like on DOS, Mac, or CD-ROM.
155
+
156
+
SHORT_NAMES = NO
157
+
158
+
# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
159
+
# will interpret the first line (until the first dot) of a JavaDoc-style
160
+
# comment as the brief description. If set to NO, the JavaDoc
161
+
# comments will behave just like regular Qt-style comments
162
+
# (thus requiring an explicit @brief command for a brief description.)
163
+
164
+
JAVADOC_AUTOBRIEF = YES
165
+
166
+
# If the QT_AUTOBRIEF tag is set to YES then Doxygen will
167
+
# interpret the first line (until the first dot) of a Qt-style
168
+
# comment as the brief description. If set to NO, the comments
169
+
# will behave just like regular Qt-style comments (thus requiring
170
+
# an explicit \brief command for a brief description.)
171
+
172
+
QT_AUTOBRIEF = NO
173
+
174
+
# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
175
+
# treat a multi-line C++ special comment block (i.e. a block of //! or ///
176
+
# comments) as a brief description. This used to be the default behaviour.
177
+
# The new default is to treat a multi-line C++ comment block as a detailed
178
+
# description. Set this tag to YES if you prefer the old behaviour instead.
179
+
180
+
MULTILINE_CPP_IS_BRIEF = NO
181
+
182
+
# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
183
+
# member inherits the documentation from any documented member that it
184
+
# re-implements.
185
+
186
+
INHERIT_DOCS = YES
187
+
188
+
# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
189
+
# a new page for each member. If set to NO, the documentation of a member will
190
+
# be part of the file/class/namespace that contains it.
191
+
192
+
SEPARATE_MEMBER_PAGES = NO
193
+
194
+
# The TAB_SIZE tag can be used to set the number of spaces in a tab.
195
+
# Doxygen uses this value to replace tabs by spaces in code fragments.
196
+
197
+
TAB_SIZE = 4
198
+
199
+
# This tag can be used to specify a number of aliases that acts
200
+
# as commands in the documentation. An alias has the form "name=value".
201
+
# For example adding "sideeffect=\par Side Effects:\n" will allow you to
202
+
# put the command \sideeffect (or @sideeffect) in the documentation, which
203
+
# will result in a user-defined paragraph with heading "Side Effects:".
204
+
# You can put \n's in the value part of an alias to insert newlines.
205
+
206
+
ALIASES =
207
+
208
+
# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
209
+
# sources only. Doxygen will then generate output that is more tailored for C.
210
+
# For instance, some of the names that are used will be different. The list
211
+
# of all members will be omitted, etc.
212
+
213
+
OPTIMIZE_OUTPUT_FOR_C = NO
214
+
215
+
# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
216
+
# sources only. Doxygen will then generate output that is more tailored for
217
+
# Java. For instance, namespaces will be presented as packages, qualified
218
+
# scopes will look different, etc.
219
+
220
+
OPTIMIZE_OUTPUT_JAVA = YES
221
+
222
+
# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
223
+
# sources only. Doxygen will then generate output that is more tailored for
224
+
# Fortran.
225
+
226
+
OPTIMIZE_FOR_FORTRAN = NO
227
+
228
+
# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
229
+
# sources. Doxygen will then generate output that is tailored for
230
+
# VHDL.
231
+
232
+
OPTIMIZE_OUTPUT_VHDL = NO
233
+
234
+
# Doxygen selects the parser to use depending on the extension of the files it
235
+
# parses. With this tag you can assign which parser to use for a given extension.
236
+
# Doxygen has a built-in mapping, but you can override or extend it using this
237
+
# tag. The format is ext=language, where ext is a file extension, and language
238
+
# is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C,
239
+
# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make
240
+
# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C
241
+
# (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions
242
+
# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.
243
+
244
+
EXTENSION_MAPPING =
245
+
246
+
# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
247
+
# to include (a tag file for) the STL sources as input, then you should
248
+
# set this tag to YES in order to let doxygen match functions declarations and
249
+
# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
250
+
# func(std::string) {}). This also makes the inheritance and collaboration
251
+
# diagrams that involve STL classes more complete and accurate.
252
+
253
+
BUILTIN_STL_SUPPORT = NO
254
+
255
+
# If you use Microsoft's C++/CLI language, you should set this option to YES to
256
+
# enable parsing support.
257
+
258
+
CPP_CLI_SUPPORT = NO
259
+
260
+
# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.
261
+
# Doxygen will parse them like normal C++ but will assume all classes use public
262
+
# instead of private inheritance when no explicit protection keyword is present.
263
+
264
+
SIP_SUPPORT = NO
265
+
266
+
# For Microsoft's IDL there are propget and propput attributes to indicate getter
267
+
# and setter methods for a property. Setting this option to YES (the default)
268
+
# will make doxygen replace the get and set methods by a property in the
269
+
# documentation. This will only work if the methods are indeed getting or
270
+
# setting a simple type. If this is not the case, or you want to show the
271
+
# methods anyway, you should set this option to NO.
272
+
273
+
IDL_PROPERTY_SUPPORT = YES
274
+
275
+
# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
276
+
# tag is set to YES, then doxygen will reuse the documentation of the first
277
+
# member in the group (if any) for the other members of the group. By default
278
+
# all members of a group must be documented explicitly.
279
+
280
+
DISTRIBUTE_GROUP_DOC = NO
281
+
282
+
# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
283
+
# the same type (for instance a group of public functions) to be put as a
284
+
# subgroup of that type (e.g. under the Public Functions section). Set it to
285
+
# NO to prevent subgrouping. Alternatively, this can be done per class using
286
+
# the \nosubgrouping command.
287
+
288
+
SUBGROUPING = YES
289
+
290
+
# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and
291
+
# unions are shown inside the group in which they are included (e.g. using
292
+
# @ingroup) instead of on a separate page (for HTML and Man pages) or
293
+
# section (for LaTeX and RTF).
294
+
295
+
INLINE_GROUPED_CLASSES = NO
296
+
297
+
# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and
298
+
# unions with only public data fields will be shown inline in the documentation
299
+
# of the scope in which they are defined (i.e. file, namespace, or group
300
+
# documentation), provided this scope is documented. If set to NO (the default),
301
+
# structs, classes, and unions are shown on a separate page (for HTML and Man
302
+
# pages) or section (for LaTeX and RTF).
303
+
304
+
INLINE_SIMPLE_STRUCTS = NO
305
+
306
+
# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
307
+
# is documented as struct, union, or enum with the name of the typedef. So
308
+
# typedef struct TypeS {} TypeT, will appear in the documentation as a struct
309
+
# with name TypeT. When disabled the typedef will appear as a member of a file,
310
+
# namespace, or class. And the struct will be named TypeS. This can typically
311
+
# be useful for C code in case the coding convention dictates that all compound
312
+
# types are typedef'ed and only the typedef is referenced, never the tag name.
313
+
314
+
TYPEDEF_HIDES_STRUCT = NO
315
+
316
+
# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to
317
+
# determine which symbols to keep in memory and which to flush to disk.
318
+
# When the cache is full, less often used symbols will be written to disk.
319
+
# For small to medium size projects (<1000 input files) the default value is
320
+
# probably good enough. For larger projects a too small cache size can cause
321
+
# doxygen to be busy swapping symbols to and from disk most of the time
322
+
# causing a significant performance penalty.
323
+
# If the system has enough physical memory increasing the cache will improve the
324
+
# performance by keeping more symbols in memory. Note that the value works on
325
+
# a logarithmic scale so increasing the size by one will roughly double the
326
+
# memory usage. The cache size is given by this formula:
327
+
# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
328
+
# corresponding to a cache size of 2^16 = 65536 symbols
329
+
330
+
SYMBOL_CACHE_SIZE = 0
331
+
332
+
#---------------------------------------------------------------------------
333
+
# Build related configuration options
334
+
#---------------------------------------------------------------------------
335
+
336
+
# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
337
+
# documentation are documented, even if no documentation was available.
338
+
# Private class members and static file members will be hidden unless
339
+
# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
340
+
341
+
EXTRACT_ALL = YES
342
+
343
+
# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
344
+
# will be included in the documentation.
345
+
346
+
EXTRACT_PRIVATE = NO
347
+
348
+
# If the EXTRACT_STATIC tag is set to YES all static members of a file
349
+
# will be included in the documentation.
350
+
351
+
EXTRACT_STATIC = YES
352
+
353
+
# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
354
+
# defined locally in source files will be included in the documentation.
355
+
# If set to NO only classes defined in header files are included.
356
+
357
+
EXTRACT_LOCAL_CLASSES = YES
358
+
359
+
# This flag is only useful for Objective-C code. When set to YES local
360
+
# methods, which are defined in the implementation section but not in
361
+
# the interface are included in the documentation.
362
+
# If set to NO (the default) only methods in the interface are included.
363
+
364
+
EXTRACT_LOCAL_METHODS = NO
365
+
366
+
# If this flag is set to YES, the members of anonymous namespaces will be
367
+
# extracted and appear in the documentation as a namespace called
368
+
# 'anonymous_namespace{file}', where file will be replaced with the base
369
+
# name of the file that contains the anonymous namespace. By default
370
+
# anonymous namespaces are hidden.
371
+
372
+
EXTRACT_ANON_NSPACES = NO
373
+
374
+
# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
375
+
# undocumented members of documented classes, files or namespaces.
376
+
# If set to NO (the default) these members will be included in the
377
+
# various overviews, but no documentation section is generated.
378
+
# This option has no effect if EXTRACT_ALL is enabled.
379
+
380
+
HIDE_UNDOC_MEMBERS = NO
381
+
382
+
# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
383
+
# undocumented classes that are normally visible in the class hierarchy.
384
+
# If set to NO (the default) these classes will be included in the various
385
+
# overviews. This option has no effect if EXTRACT_ALL is enabled.
386
+
387
+
HIDE_UNDOC_CLASSES = NO
388
+
389
+
# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
390
+
# friend (class|struct|union) declarations.
391
+
# If set to NO (the default) these declarations will be included in the
392
+
# documentation.
393
+
394
+
HIDE_FRIEND_COMPOUNDS = NO
395
+
396
+
# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
397
+
# documentation blocks found inside the body of a function.
398
+
# If set to NO (the default) these blocks will be appended to the
399
+
# function's detailed documentation block.
400
+
401
+
HIDE_IN_BODY_DOCS = NO
402
+
403
+
# The INTERNAL_DOCS tag determines if documentation
404
+
# that is typed after a \internal command is included. If the tag is set
405
+
# to NO (the default) then the documentation will be excluded.
406
+
# Set it to YES to include the internal documentation.
407
+
408
+
INTERNAL_DOCS = NO
409
+
410
+
# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
411
+
# file names in lower-case letters. If set to YES upper-case letters are also
412
+
# allowed. This is useful if you have classes or files whose names only differ
413
+
# in case and if your file system supports case sensitive file names. Windows
414
+
# and Mac users are advised to set this option to NO.
415
+
416
+
CASE_SENSE_NAMES = NO
417
+
418
+
# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
419
+
# will show members with their full class and namespace scopes in the
420
+
# documentation. If set to YES the scope will be hidden.
421
+
422
+
HIDE_SCOPE_NAMES = NO
423
+
424
+
# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
425
+
# will put a list of the files that are included by a file in the documentation
426
+
# of that file.
427
+
428
+
SHOW_INCLUDE_FILES = YES
429
+
430
+
# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen
431
+
# will list include files with double quotes in the documentation
432
+
# rather than with sharp brackets.
433
+
434
+
FORCE_LOCAL_INCLUDES = NO
435
+
436
+
# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
437
+
# is inserted in the documentation for inline members.
438
+
439
+
INLINE_INFO = YES
440
+
441
+
# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
442
+
# will sort the (detailed) documentation of file and class members
443
+
# alphabetically by member name. If set to NO the members will appear in
444
+
# declaration order.
445
+
446
+
SORT_MEMBER_DOCS = YES
447
+
448
+
# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
449
+
# brief documentation of file, namespace and class members alphabetically
450
+
# by member name. If set to NO (the default) the members will appear in
451
+
# declaration order.
452
+
453
+
SORT_BRIEF_DOCS = NO
454
+
455
+
# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen
456
+
# will sort the (brief and detailed) documentation of class members so that
457
+
# constructors and destructors are listed first. If set to NO (the default)
458
+
# the constructors will appear in the respective orders defined by
459
+
# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.
460
+
# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO
461
+
# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
462
+
463
+
SORT_MEMBERS_CTORS_1ST = NO
464
+
465
+
# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
466
+
# hierarchy of group names into alphabetical order. If set to NO (the default)
467
+
# the group names will appear in their defined order.
468
+
469
+
SORT_GROUP_NAMES = NO
470
+
471
+
# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
472
+
# sorted by fully-qualified names, including namespaces. If set to
473
+
# NO (the default), the class list will be sorted only by class name,
474
+
# not including the namespace part.
475
+
# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
476
+
# Note: This option applies only to the class list, not to the
477
+
# alphabetical list.
478
+
479
+
SORT_BY_SCOPE_NAME = NO
480
+
481
+
# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to
482
+
# do proper type resolution of all parameters of a function it will reject a
483
+
# match between the prototype and the implementation of a member function even
484
+
# if there is only one candidate or it is obvious which candidate to choose
485
+
# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen
486
+
# will still accept a match between prototype and implementation in such cases.
487
+
488
+
STRICT_PROTO_MATCHING = NO
489
+
490
+
# The GENERATE_TODOLIST tag can be used to enable (YES) or
491
+
# disable (NO) the todo list. This list is created by putting \todo
492
+
# commands in the documentation.
493
+
494
+
GENERATE_TODOLIST = YES
495
+
496
+
# The GENERATE_TESTLIST tag can be used to enable (YES) or
497
+
# disable (NO) the test list. This list is created by putting \test
498
+
# commands in the documentation.
499
+
500
+
GENERATE_TESTLIST = YES
501
+
502
+
# The GENERATE_BUGLIST tag can be used to enable (YES) or
503
+
# disable (NO) the bug list. This list is created by putting \bug
504
+
# commands in the documentation.
505
+
506
+
GENERATE_BUGLIST = YES
507
+
508
+
# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
509
+
# disable (NO) the deprecated list. This list is created by putting
510
+
# \deprecated commands in the documentation.
511
+
512
+
GENERATE_DEPRECATEDLIST= YES
513
+
514
+
# The ENABLED_SECTIONS tag can be used to enable conditional
515
+
# documentation sections, marked by \if sectionname ... \endif.
516
+
517
+
ENABLED_SECTIONS =
518
+
519
+
# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
520
+
# the initial value of a variable or macro consists of for it to appear in
521
+
# the documentation. If the initializer consists of more lines than specified
522
+
# here it will be hidden. Use a value of 0 to hide initializers completely.
523
+
# The appearance of the initializer of individual variables and macros in the
524
+
# documentation can be controlled using \showinitializer or \hideinitializer
525
+
# command in the documentation regardless of this setting.
526
+
527
+
MAX_INITIALIZER_LINES = 30
528
+
529
+
# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
530
+
# at the bottom of the documentation of classes and structs. If set to YES the
531
+
# list will mention the files that were used to generate the documentation.
532
+
533
+
SHOW_USED_FILES = YES
534
+
535
+
# If the sources in your project are distributed over multiple directories
536
+
# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
537
+
# in the documentation. The default is NO.
538
+
539
+
SHOW_DIRECTORIES = NO
540
+
541
+
# Set the SHOW_FILES tag to NO to disable the generation of the Files page.
542
+
# This will remove the Files entry from the Quick Index and from the
543
+
# Folder Tree View (if specified). The default is YES.
544
+
545
+
SHOW_FILES = YES
546
+
547
+
# Set the SHOW_NAMESPACES tag to NO to disable the generation of the
548
+
# Namespaces page. This will remove the Namespaces entry from the Quick Index
549
+
# and from the Folder Tree View (if specified). The default is YES.
550
+
551
+
SHOW_NAMESPACES = YES
552
+
553
+
# The FILE_VERSION_FILTER tag can be used to specify a program or script that
554
+
# doxygen should invoke to get the current version for each file (typically from
555
+
# the version control system). Doxygen will invoke the program by executing (via
556
+
# popen()) the command <command> <input-file>, where <command> is the value of
557
+
# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
558
+
# provided by doxygen. Whatever the program writes to standard output
559
+
# is used as the file version. See the manual for examples.
560
+
561
+
FILE_VERSION_FILTER =
562
+
563
+
# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
564
+
# by doxygen. The layout file controls the global structure of the generated
565
+
# output files in an output format independent way. The create the layout file
566
+
# that represents doxygen's defaults, run doxygen with the -l option.
567
+
# You can optionally specify a file name after the option, if omitted
568
+
# DoxygenLayout.xml will be used as the name of the layout file.
569
+
570
+
LAYOUT_FILE =
571
+
572
+
# The CITE_BIB_FILES tag can be used to specify one or more bib files
573
+
# containing the references data. This must be a list of .bib files. The
574
+
# .bib extension is automatically appended if omitted. Using this command
575
+
# requires the bibtex tool to be installed. See also
576
+
# http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style
577
+
# of the bibliography can be controlled using LATEX_BIB_STYLE.
578
+
579
+
CITE_BIB_FILES =
580
+
581
+
#---------------------------------------------------------------------------
582
+
# configuration options related to warning and progress messages
583
+
#---------------------------------------------------------------------------
584
+
585
+
# The QUIET tag can be used to turn on/off the messages that are generated
586
+
# by doxygen. Possible values are YES and NO. If left blank NO is used.
587
+
588
+
QUIET = NO
589
+
590
+
# The WARNINGS tag can be used to turn on/off the warning messages that are
591
+
# generated by doxygen. Possible values are YES and NO. If left blank
592
+
# NO is used.
593
+
594
+
WARNINGS = NO
595
+
596
+
# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
597
+
# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
598
+
# automatically be disabled.
599
+
600
+
WARN_IF_UNDOCUMENTED = YES
601
+
602
+
# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
603
+
# potential errors in the documentation, such as not documenting some
604
+
# parameters in a documented function, or documenting parameters that
605
+
# don't exist or using markup commands wrongly.
606
+
607
+
WARN_IF_DOC_ERROR = YES
608
+
609
+
# The WARN_NO_PARAMDOC option can be enabled to get warnings for
610
+
# functions that are documented, but have no documentation for their parameters
611
+
# or return value. If set to NO (the default) doxygen will only warn about
612
+
# wrong or incomplete parameter documentation, but not about the absence of
613
+
# documentation.
614
+
615
+
WARN_NO_PARAMDOC = NO
616
+
617
+
# The WARN_FORMAT tag determines the format of the warning messages that
618
+
# doxygen can produce. The string should contain the $file, $line, and $text
619
+
# tags, which will be replaced by the file and line number from which the
620
+
# warning originated and the warning text. Optionally the format may contain
621
+
# $version, which will be replaced by the version of the file (if it could
622
+
# be obtained via FILE_VERSION_FILTER)
623
+
624
+
WARN_FORMAT = "$file:$line: $text"
625
+
626
+
# The WARN_LOGFILE tag can be used to specify a file to which warning
627
+
# and error messages should be written. If left blank the output is written
628
+
# to stderr.
629
+
630
+
WARN_LOGFILE =
631
+
632
+
#---------------------------------------------------------------------------
633
+
# configuration options related to the input files
634
+
#---------------------------------------------------------------------------
635
+
636
+
# The INPUT tag can be used to specify the files and/or directories that contain
637
+
# documented source files. You may enter file names like "myfile.cpp" or
638
+
# directories like "/usr/src/myproject". Separate the files or directories
639
+
# with spaces.
640
+
641
+
INPUT = "D:/Documents/GitHub/Dogfight/Assets/External Libraries"
642
+
643
+
# This tag can be used to specify the character encoding of the source files
644
+
# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
645
+
# also the default input encoding. Doxygen uses libiconv (or the iconv built
646
+
# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
647
+
# the list of possible encodings.
648
+
649
+
INPUT_ENCODING = UTF-8
650
+
651
+
# If the value of the INPUT tag contains directories, you can use the
652
+
# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
653
+
# and *.h) to filter out the source-files in the directories. If left
654
+
# blank the following patterns are tested:
655
+
# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh
656
+
# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py
657
+
# *.f90 *.f *.for *.vhd *.vhdl
658
+
659
+
FILE_PATTERNS = *.c \
660
+
*.cc \
661
+
*.cxx \
662
+
*.cpp \
663
+
*.c++ \
664
+
*.d \
665
+
*.java \
666
+
*.ii \
667
+
*.ixx \
668
+
*.ipp \
669
+
*.i++ \
670
+
*.inl \
671
+
*.h \
672
+
*.hh \
673
+
*.hxx \
674
+
*.hpp \
675
+
*.h++ \
676
+
*.idl \
677
+
*.odl \
678
+
*.cs \
679
+
*.php \
680
+
*.php3 \
681
+
*.inc \
682
+
*.m \
683
+
*.mm \
684
+
*.dox \
685
+
*.py \
686
+
*.f90 \
687
+
*.f \
688
+
*.for \
689
+
*.vhd \
690
+
*.vhdl
691
+
692
+
# The RECURSIVE tag can be used to turn specify whether or not subdirectories
693
+
# should be searched for input files as well. Possible values are YES and NO.
694
+
# If left blank NO is used.
695
+
696
+
RECURSIVE = YES
697
+
698
+
# The EXCLUDE tag can be used to specify files and/or directories that should
699
+
# excluded from the INPUT source files. This way you can easily exclude a
700
+
# subdirectory from a directory tree whose root is specified with the INPUT tag.
701
+
# Note that relative paths are relative to directory from which doxygen is run.
702
+
703
+
EXCLUDE =
704
+
705
+
# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
706
+
# directories that are symbolic links (a Unix file system feature) are excluded
707
+
# from the input.
708
+
709
+
EXCLUDE_SYMLINKS = NO
710
+
711
+
# If the value of the INPUT tag contains directories, you can use the
712
+
# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
713
+
# certain files from those directories. Note that the wildcards are matched
714
+
# against the file with absolute path, so to exclude all test directories
715
+
# for example use the pattern */test/*
716
+
717
+
EXCLUDE_PATTERNS =
718
+
719
+
# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
720
+
# (namespaces, classes, functions, etc.) that should be excluded from the
721
+
# output. The symbol name can be a fully qualified name, a word, or if the
722
+
# wildcard * is used, a substring. Examples: ANamespace, AClass,
723
+
# AClass::ANamespace, ANamespace::*Test
724
+
725
+
EXCLUDE_SYMBOLS =
726
+
727
+
# The EXAMPLE_PATH tag can be used to specify one or more files or
728
+
# directories that contain example code fragments that are included (see
729
+
# the \include command).
730
+
731
+
EXAMPLE_PATH =
732
+
733
+
# If the value of the EXAMPLE_PATH tag contains directories, you can use the
734
+
# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
735
+
# and *.h) to filter out the source-files in the directories. If left
736
+
# blank all files are included.
737
+
738
+
EXAMPLE_PATTERNS = *
739
+
740
+
# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
741
+
# searched for input files to be used with the \include or \dontinclude
742
+
# commands irrespective of the value of the RECURSIVE tag.
743
+
# Possible values are YES and NO. If left blank NO is used.
744
+
745
+
EXAMPLE_RECURSIVE = NO
746
+
747
+
# The IMAGE_PATH tag can be used to specify one or more files or
748
+
# directories that contain image that are included in the documentation (see
749
+
# the \image command).
750
+
751
+
IMAGE_PATH =
752
+
753
+
# The INPUT_FILTER tag can be used to specify a program that doxygen should
754
+
# invoke to filter for each input file. Doxygen will invoke the filter program
755
+
# by executing (via popen()) the command <filter> <input-file>, where <filter>
756
+
# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
757
+
# input file. Doxygen will then use the output that the filter program writes
758
+
# to standard output. If FILTER_PATTERNS is specified, this tag will be
759
+
# ignored.
760
+
761
+
INPUT_FILTER =
762
+
763
+
# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
764
+
# basis. Doxygen will compare the file name with each pattern and apply the
765
+
# filter if there is a match. The filters are a list of the form:
766
+
# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
767
+
# info on how filters are used. If FILTER_PATTERNS is empty or if
768
+
# non of the patterns match the file name, INPUT_FILTER is applied.
769
+
770
+
FILTER_PATTERNS =
771
+
772
+
# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
773
+
# INPUT_FILTER) will be used to filter the input files when producing source
774
+
# files to browse (i.e. when SOURCE_BROWSER is set to YES).
775
+
776
+
FILTER_SOURCE_FILES = NO
777
+
778
+
# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
779
+
# pattern. A pattern will override the setting for FILTER_PATTERN (if any)
780
+
# and it is also possible to disable source filtering for a specific pattern
781
+
# using *.ext= (so without naming a filter). This option only has effect when
782
+
# FILTER_SOURCE_FILES is enabled.
783
+
784
+
FILTER_SOURCE_PATTERNS =
785
+
786
+
#---------------------------------------------------------------------------
787
+
# configuration options related to source browsing
788
+
#---------------------------------------------------------------------------
789
+
790
+
# If the SOURCE_BROWSER tag is set to YES then a list of source files will
791
+
# be generated. Documented entities will be cross-referenced with these sources.
792
+
# Note: To get rid of all source code in the generated output, make sure also
793
+
# VERBATIM_HEADERS is set to NO.
794
+
795
+
SOURCE_BROWSER = NO
796
+
797
+
# Setting the INLINE_SOURCES tag to YES will include the body
798
+
# of functions and classes directly in the documentation.
799
+
800
+
INLINE_SOURCES = NO
801
+
802
+
# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
803
+
# doxygen to hide any special comment blocks from generated source code
804
+
# fragments. Normal C and C++ comments will always remain visible.
805
+
806
+
STRIP_CODE_COMMENTS = YES
807
+
808
+
# If the REFERENCED_BY_RELATION tag is set to YES
809
+
# then for each documented function all documented
810
+
# functions referencing it will be listed.
811
+
812
+
REFERENCED_BY_RELATION = NO
813
+
814
+
# If the REFERENCES_RELATION tag is set to YES
815
+
# then for each documented function all documented entities
816
+
# called/used by that function will be listed.
817
+
818
+
REFERENCES_RELATION = NO
819
+
820
+
# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
821
+
# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
822
+
# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
823
+
# link to the source code. Otherwise they will link to the documentation.
824
+
825
+
REFERENCES_LINK_SOURCE = YES
826
+
827
+
# If the USE_HTAGS tag is set to YES then the references to source code
828
+
# will point to the HTML generated by the htags(1) tool instead of doxygen
829
+
# built-in source browser. The htags tool is part of GNU's global source
830
+
# tagging system (see http://www.gnu.org/software/global/global.html). You
831
+
# will need version 4.8.6 or higher.
832
+
833
+
USE_HTAGS = NO
834
+
835
+
# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
836
+
# will generate a verbatim copy of the header file for each class for
837
+
# which an include is specified. Set to NO to disable this.
838
+
839
+
VERBATIM_HEADERS = YES
840
+
841
+
#---------------------------------------------------------------------------
842
+
# configuration options related to the alphabetical class index
843
+
#---------------------------------------------------------------------------
844
+
845
+
# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
846
+
# of all compounds will be generated. Enable this if the project
847
+
# contains a lot of classes, structs, unions or interfaces.
848
+
849
+
ALPHABETICAL_INDEX = YES
850
+
851
+
# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
852
+
# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
853
+
# in which this list will be split (can be a number in the range [1..20])
854
+
855
+
COLS_IN_ALPHA_INDEX = 5
856
+
857
+
# In case all classes in a project start with a common prefix, all
858
+
# classes will be put under the same header in the alphabetical index.
859
+
# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
860
+
# should be ignored while generating the index headers.
861
+
862
+
IGNORE_PREFIX =
863
+
864
+
#---------------------------------------------------------------------------
865
+
# configuration options related to the HTML output
866
+
#---------------------------------------------------------------------------
867
+
868
+
# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
869
+
# generate HTML output.
870
+
871
+
GENERATE_HTML = YES
872
+
873
+
# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
874
+
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
875
+
# put in front of it. If left blank `html' will be used as the default path.
876
+
877
+
HTML_OUTPUT = html
878
+
879
+
# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
880
+
# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
881
+
# doxygen will generate files with .html extension.
882
+
883
+
HTML_FILE_EXTENSION = .html
884
+
885
+
# The HTML_HEADER tag can be used to specify a personal HTML header for
886
+
# each generated HTML page. If it is left blank doxygen will generate a
887
+
# standard header. Note that when using a custom header you are responsible
888
+
# for the proper inclusion of any scripts and style sheets that doxygen
889
+
# needs, which is dependent on the configuration options used.
890
+
# It is adviced to generate a default header using "doxygen -w html
891
+
# header.html footer.html stylesheet.css YourConfigFile" and then modify
892
+
# that header. Note that the header is subject to change so you typically
893
+
# have to redo this when upgrading to a newer version of doxygen or when
894
+
# changing the value of configuration settings such as GENERATE_TREEVIEW!
895
+
896
+
HTML_HEADER =
897
+
898
+
# The HTML_FOOTER tag can be used to specify a personal HTML footer for
899
+
# each generated HTML page. If it is left blank doxygen will generate a
900
+
# standard footer.
901
+
902
+
HTML_FOOTER =
903
+
904
+
# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
905
+
# style sheet that is used by each HTML page. It can be used to
906
+
# fine-tune the look of the HTML output. If the tag is left blank doxygen
907
+
# will generate a default style sheet. Note that doxygen will try to copy
908
+
# the style sheet file to the HTML output directory, so don't put your own
909
+
# stylesheet in the HTML output directory as well, or it will be erased!
910
+
911
+
HTML_STYLESHEET =
912
+
913
+
# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
914
+
# other source files which should be copied to the HTML output directory. Note
915
+
# that these files will be copied to the base HTML output directory. Use the
916
+
# $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
917
+
# files. In the HTML_STYLESHEET file, use the file name only. Also note that
918
+
# the files will be copied as-is; there are no commands or markers available.
919
+
920
+
HTML_EXTRA_FILES =
921
+
922
+
# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.
923
+
# Doxygen will adjust the colors in the stylesheet and background images
924
+
# according to this color. Hue is specified as an angle on a colorwheel,
925
+
# see http://en.wikipedia.org/wiki/Hue for more information.
926
+
# For instance the value 0 represents red, 60 is yellow, 120 is green,
927
+
# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.
928
+
# The allowed range is 0 to 359.
929
+
930
+
HTML_COLORSTYLE_HUE = 220
931
+
932
+
# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of
933
+
# the colors in the HTML output. For a value of 0 the output will use
934
+
# grayscales only. A value of 255 will produce the most vivid colors.
935
+
936
+
HTML_COLORSTYLE_SAT = 100
937
+
938
+
# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to
939
+
# the luminance component of the colors in the HTML output. Values below
940
+
# 100 gradually make the output lighter, whereas values above 100 make
941
+
# the output darker. The value divided by 100 is the actual gamma applied,
942
+
# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,
943
+
# and 100 does not change the gamma.
944
+
945
+
HTML_COLORSTYLE_GAMMA = 80
946
+
947
+
# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
948
+
# page will contain the date and time when the page was generated. Setting
949
+
# this to NO can help when comparing the output of multiple runs.
950
+
951
+
HTML_TIMESTAMP = YES
952
+
953
+
# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
954
+
# files or namespaces will be aligned in HTML using tables. If set to
955
+
# NO a bullet list will be used.
956
+
957
+
HTML_ALIGN_MEMBERS = YES
958
+
959
+
# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
960
+
# documentation will contain sections that can be hidden and shown after the
961
+
# page has loaded. For this to work a browser that supports
962
+
# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
963
+
# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
964
+
965
+
HTML_DYNAMIC_SECTIONS = NO
966
+
967
+
# If the GENERATE_DOCSET tag is set to YES, additional index files
968
+
# will be generated that can be used as input for Apple's Xcode 3
969
+
# integrated development environment, introduced with OSX 10.5 (Leopard).
970
+
# To create a documentation set, doxygen will generate a Makefile in the
971
+
# HTML output directory. Running make will produce the docset in that
972
+
# directory and running "make install" will install the docset in
973
+
# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
974
+
# it at startup.
975
+
# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
976
+
# for more information.
977
+
978
+
GENERATE_DOCSET = NO
979
+
980
+
# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
981
+
# feed. A documentation feed provides an umbrella under which multiple
982
+
# documentation sets from a single provider (such as a company or product suite)
983
+
# can be grouped.
984
+
985
+
DOCSET_FEEDNAME = "Doxygen generated docs"
986
+
987
+
# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
988
+
# should uniquely identify the documentation set bundle. This should be a
989
+
# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
990
+
# will append .docset to the name.
991
+
992
+
DOCSET_BUNDLE_ID = org.doxygen.Project
993
+
994
+
# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify
995
+
# the documentation publisher. This should be a reverse domain-name style
996
+
# string, e.g. com.mycompany.MyDocSet.documentation.
997
+
998
+
DOCSET_PUBLISHER_ID = org.doxygen.Publisher
999
+
1000
+
# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
1001
+
1002
+
DOCSET_PUBLISHER_NAME = Publisher
1003
+
1004
+
# If the GENERATE_HTMLHELP tag is set to YES, additional index files
1005
+
# will be generated that can be used as input for tools like the
1006
+
# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
1007
+
# of the generated HTML documentation.
1008
+
1009
+
GENERATE_HTMLHELP = NO
1010
+
1011
+
# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
1012
+
# be used to specify the file name of the resulting .chm file. You
1013
+
# can add a path in front of the file if the result should not be
1014
+
# written to the html output directory.
1015
+
1016
+
CHM_FILE =
1017
+
1018
+
# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
1019
+
# be used to specify the location (absolute path including file name) of
1020
+
# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
1021
+
# the HTML help compiler on the generated index.hhp.
1022
+
1023
+
HHC_LOCATION =
1024
+
1025
+
# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
1026
+
# controls if a separate .chi index file is generated (YES) or that
1027
+
# it should be included in the master .chm file (NO).
1028
+
1029
+
GENERATE_CHI = NO
1030
+
1031
+
# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
1032
+
# is used to encode HtmlHelp index (hhk), content (hhc) and project file
1033
+
# content.
1034
+
1035
+
CHM_INDEX_ENCODING =
1036
+
1037
+
# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
1038
+
# controls whether a binary table of contents is generated (YES) or a
1039
+
# normal table of contents (NO) in the .chm file.
1040
+
1041
+
BINARY_TOC = NO
1042
+
1043
+
# The TOC_EXPAND flag can be set to YES to add extra items for group members
1044
+
# to the contents of the HTML help documentation and to the tree view.
1045
+
1046
+
TOC_EXPAND = NO
1047
+
1048
+
# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
1049
+
# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated
1050
+
# that can be used as input for Qt's qhelpgenerator to generate a
1051
+
# Qt Compressed Help (.qch) of the generated HTML documentation.
1052
+
1053
+
GENERATE_QHP = NO
1054
+
1055
+
# If the QHG_LOCATION tag is specified, the QCH_FILE tag can
1056
+
# be used to specify the file name of the resulting .qch file.
1057
+
# The path specified is relative to the HTML output folder.
1058
+
1059
+
QCH_FILE =
1060
+
1061
+
# The QHP_NAMESPACE tag specifies the namespace to use when generating
1062
+
# Qt Help Project output. For more information please see
1063
+
# http://doc.trolltech.com/qthelpproject.html#namespace
1064
+
1065
+
QHP_NAMESPACE = org.doxygen.Project
1066
+
1067
+
# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
1068
+
# Qt Help Project output. For more information please see
1069
+
# http://doc.trolltech.com/qthelpproject.html#virtual-folders
1070
+
1071
+
QHP_VIRTUAL_FOLDER = doc
1072
+
1073
+
# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to
1074
+
# add. For more information please see
1075
+
# http://doc.trolltech.com/qthelpproject.html#custom-filters
1076
+
1077
+
QHP_CUST_FILTER_NAME =
1078
+
1079
+
# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the
1080
+
# custom filter to add. For more information please see
1081
+
# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">
1082
+
# Qt Help Project / Custom Filters</a>.
1083
+
1084
+
QHP_CUST_FILTER_ATTRS =
1085
+
1086
+
# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
1087
+
# project's
1088
+
# filter section matches.
1089
+
# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">
1090
+
# Qt Help Project / Filter Attributes</a>.
1091
+
1092
+
QHP_SECT_FILTER_ATTRS =
1093
+
1094
+
# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can
1095
+
# be used to specify the location of Qt's qhelpgenerator.
1096
+
# If non-empty doxygen will try to run qhelpgenerator on the generated
1097
+
# .qhp file.
1098
+
1099
+
QHG_LOCATION =
1100
+
1101
+
# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files
1102
+
# will be generated, which together with the HTML files, form an Eclipse help
1103
+
# plugin. To install this plugin and make it available under the help contents
1104
+
# menu in Eclipse, the contents of the directory containing the HTML and XML
1105
+
# files needs to be copied into the plugins directory of eclipse. The name of
1106
+
# the directory within the plugins directory should be the same as
1107
+
# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before
1108
+
# the help appears.
1109
+
1110
+
GENERATE_ECLIPSEHELP = NO
1111
+
1112
+
# A unique identifier for the eclipse help plugin. When installing the plugin
1113
+
# the directory name containing the HTML and XML files should also have
1114
+
# this name.
1115
+
1116
+
ECLIPSE_DOC_ID = org.doxygen.Project
1117
+
1118
+
# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
1119
+
# top of each HTML page. The value NO (the default) enables the index and
1120
+
# the value YES disables it.
1121
+
1122
+
DISABLE_INDEX = NO
1123
+
1124
+
# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values
1125
+
# (range [0,1..20]) that doxygen will group on one line in the generated HTML
1126
+
# documentation. Note that a value of 0 will completely suppress the enum
1127
+
# values from appearing in the overview section.
1128
+
1129
+
ENUM_VALUES_PER_LINE = 4
1130
+
1131
+
# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1132
+
# structure should be generated to display hierarchical information.
1133
+
# If the tag value is set to YES, a side panel will be generated
1134
+
# containing a tree-like index structure (just like the one that
1135
+
# is generated for HTML Help). For this to work a browser that supports
1136
+
# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
1137
+
# Windows users are probably better off using the HTML help feature.
1138
+
1139
+
GENERATE_TREEVIEW = YES
1140
+
1141
+
# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,
1142
+
# and Class Hierarchy pages using a tree view instead of an ordered list.
1143
+
1144
+
USE_INLINE_TREES = NO
1145
+
1146
+
# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
1147
+
# used to set the initial width (in pixels) of the frame in which the tree
1148
+
# is shown.
1149
+
1150
+
TREEVIEW_WIDTH = 250
1151
+
1152
+
# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open
1153
+
# links to external symbols imported via tag files in a separate window.
1154
+
1155
+
EXT_LINKS_IN_WINDOW = NO
1156
+
1157
+
# Use this tag to change the font size of Latex formulas included
1158
+
# as images in the HTML documentation. The default is 10. Note that
1159
+
# when you change the font size after a successful doxygen run you need
1160
+
# to manually remove any form_*.png images from the HTML output directory
1161
+
# to force them to be regenerated.
1162
+
1163
+
FORMULA_FONTSIZE = 10
1164
+
1165
+
# Use the FORMULA_TRANPARENT tag to determine whether or not the images
1166
+
# generated for formulas are transparent PNGs. Transparent PNGs are
1167
+
# not supported properly for IE 6.0, but are supported on all modern browsers.
1168
+
# Note that when changing this option you need to delete any form_*.png files
1169
+
# in the HTML output before the changes have effect.
1170
+
1171
+
FORMULA_TRANSPARENT = YES
1172
+
1173
+
# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax
1174
+
# (see http://www.mathjax.org) which uses client side Javascript for the
1175
+
# rendering instead of using prerendered bitmaps. Use this if you do not
1176
+
# have LaTeX installed or if you want to formulas look prettier in the HTML
1177
+
# output. When enabled you also need to install MathJax separately and
1178
+
# configure the path to it using the MATHJAX_RELPATH option.
1179
+
1180
+
USE_MATHJAX = NO
1181
+
1182
+
# When MathJax is enabled you need to specify the location relative to the
1183
+
# HTML output directory using the MATHJAX_RELPATH option. The destination
1184
+
# directory should contain the MathJax.js script. For instance, if the mathjax
1185
+
# directory is located at the same level as the HTML output directory, then
1186
+
# MATHJAX_RELPATH should be ../mathjax. The default value points to the
1187
+
# mathjax.org site, so you can quickly see the result without installing
1188
+
# MathJax, but it is strongly recommended to install a local copy of MathJax
1189
+
# before deployment.
1190
+
1191
+
MATHJAX_RELPATH = http://www.mathjax.org/mathjax
1192
+
1193
+
# The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension
1194
+
# names that should be enabled during MathJax rendering.
1195
+
1196
+
MATHJAX_EXTENSIONS =
1197
+
1198
+
# When the SEARCHENGINE tag is enabled doxygen will generate a search box
1199
+
# for the HTML output. The underlying search engine uses javascript
1200
+
# and DHTML and should work on any modern browser. Note that when using
1201
+
# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets
1202
+
# (GENERATE_DOCSET) there is already a search function so this one should
1203
+
# typically be disabled. For large projects the javascript based search engine
1204
+
# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.
1205
+
1206
+
SEARCHENGINE = YES
1207
+
1208
+
# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1209
+
# implemented using a PHP enabled web server instead of at the web client
1210
+
# using Javascript. Doxygen will generate the search PHP script and index
1211
+
# file to put on the web server. The advantage of the server
1212
+
# based approach is that it scales better to large projects and allows
1213
+
# full text search. The disadvantages are that it is more difficult to setup
1214
+
# and does not have live searching capabilities.
1215
+
1216
+
SERVER_BASED_SEARCH = NO
1217
+
1218
+
#---------------------------------------------------------------------------
1219
+
# configuration options related to the LaTeX output
1220
+
#---------------------------------------------------------------------------
1221
+
1222
+
# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
1223
+
# generate Latex output.
1224
+
1225
+
GENERATE_LATEX = NO
1226
+
1227
+
# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
1228
+
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1229
+
# put in front of it. If left blank `latex' will be used as the default path.
1230
+
1231
+
LATEX_OUTPUT = latex
1232
+
1233
+
# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1234
+
# invoked. If left blank `latex' will be used as the default command name.
1235
+
# Note that when enabling USE_PDFLATEX this option is only used for
1236
+
# generating bitmaps for formulas in the HTML output, but not in the
1237
+
# Makefile that is written to the output directory.
1238
+
1239
+
LATEX_CMD_NAME = latex
1240
+
1241
+
# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
1242
+
# generate index for LaTeX. If left blank `makeindex' will be used as the
1243
+
# default command name.
1244
+
1245
+
MAKEINDEX_CMD_NAME = makeindex
1246
+
1247
+
# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
1248
+
# LaTeX documents. This may be useful for small projects and may help to
1249
+
# save some trees in general.
1250
+
1251
+
COMPACT_LATEX = NO
1252
+
1253
+
# The PAPER_TYPE tag can be used to set the paper type that is used
1254
+
# by the printer. Possible values are: a4, letter, legal and
1255
+
# executive. If left blank a4wide will be used.
1256
+
1257
+
PAPER_TYPE = a4
1258
+
1259
+
# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
1260
+
# packages that should be included in the LaTeX output.
1261
+
1262
+
EXTRA_PACKAGES =
1263
+
1264
+
# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
1265
+
# the generated latex document. The header should contain everything until
1266
+
# the first chapter. If it is left blank doxygen will generate a
1267
+
# standard header. Notice: only use this tag if you know what you are doing!
1268
+
1269
+
LATEX_HEADER =
1270
+
1271
+
# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for
1272
+
# the generated latex document. The footer should contain everything after
1273
+
# the last chapter. If it is left blank doxygen will generate a
1274
+
# standard footer. Notice: only use this tag if you know what you are doing!
1275
+
1276
+
LATEX_FOOTER =
1277
+
1278
+
# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
1279
+
# is prepared for conversion to pdf (using ps2pdf). The pdf file will
1280
+
# contain links (just like the HTML output) instead of page references
1281
+
# This makes the output suitable for online browsing using a pdf viewer.
1282
+
1283
+
PDF_HYPERLINKS = YES
1284
+
1285
+
# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
1286
+
# plain latex in the generated Makefile. Set this option to YES to get a
1287
+
# higher quality PDF documentation.
1288
+
1289
+
USE_PDFLATEX = YES
1290
+
1291
+
# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
1292
+
# command to the generated LaTeX files. This will instruct LaTeX to keep
1293
+
# running if errors occur, instead of asking the user for help.
1294
+
# This option is also used when generating formulas in HTML.
1295
+
1296
+
LATEX_BATCHMODE = NO
1297
+
1298
+
# If LATEX_HIDE_INDICES is set to YES then doxygen will not
1299
+
# include the index chapters (such as File Index, Compound Index, etc.)
1300
+
# in the output.
1301
+
1302
+
LATEX_HIDE_INDICES = NO
1303
+
1304
+
# If LATEX_SOURCE_CODE is set to YES then doxygen will include
1305
+
# source code with syntax highlighting in the LaTeX output.
1306
+
# Note that which sources are shown also depends on other settings
1307
+
# such as SOURCE_BROWSER.
1308
+
1309
+
LATEX_SOURCE_CODE = NO
1310
+
1311
+
# The LATEX_BIB_STYLE tag can be used to specify the style to use for the
1312
+
# bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See
1313
+
# http://en.wikipedia.org/wiki/BibTeX for more info.
1314
+
1315
+
LATEX_BIB_STYLE = plain
1316
+
1317
+
#---------------------------------------------------------------------------
1318
+
# configuration options related to the RTF output
1319
+
#---------------------------------------------------------------------------
1320
+
1321
+
# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
1322
+
# The RTF output is optimized for Word 97 and may not look very pretty with
1323
+
# other RTF readers or editors.
1324
+
1325
+
GENERATE_RTF = NO
1326
+
1327
+
# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
1328
+
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1329
+
# put in front of it. If left blank `rtf' will be used as the default path.
1330
+
1331
+
RTF_OUTPUT = rtf
1332
+
1333
+
# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
1334
+
# RTF documents. This may be useful for small projects and may help to
1335
+
# save some trees in general.
1336
+
1337
+
COMPACT_RTF = NO
1338
+
1339
+
# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
1340
+
# will contain hyperlink fields. The RTF file will
1341
+
# contain links (just like the HTML output) instead of page references.
1342
+
# This makes the output suitable for online browsing using WORD or other
1343
+
# programs which support those fields.
1344
+
# Note: wordpad (write) and others do not support links.
1345
+
1346
+
RTF_HYPERLINKS = NO
1347
+
1348
+
# Load stylesheet definitions from file. Syntax is similar to doxygen's
1349
+
# config file, i.e. a series of assignments. You only have to provide
1350
+
# replacements, missing definitions are set to their default value.
1351
+
1352
+
RTF_STYLESHEET_FILE =
1353
+
1354
+
# Set optional variables used in the generation of an rtf document.
1355
+
# Syntax is similar to doxygen's config file.
1356
+
1357
+
RTF_EXTENSIONS_FILE =
1358
+
1359
+
#---------------------------------------------------------------------------
1360
+
# configuration options related to the man page output
1361
+
#---------------------------------------------------------------------------
1362
+
1363
+
# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1364
+
# generate man pages
1365
+
1366
+
GENERATE_MAN = NO
1367
+
1368
+
# The MAN_OUTPUT tag is used to specify where the man pages will be put.
1369
+
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1370
+
# put in front of it. If left blank `man' will be used as the default path.
1371
+
1372
+
MAN_OUTPUT = man
1373
+
1374
+
# The MAN_EXTENSION tag determines the extension that is added to
1375
+
# the generated man pages (default is the subroutine's section .3)
1376
+
1377
+
MAN_EXTENSION = .3
1378
+
1379
+
# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
1380
+
# then it will generate one additional man file for each entity
1381
+
# documented in the real man page(s). These additional files
1382
+
# only source the real man page, but without them the man command
1383
+
# would be unable to find the correct page. The default is NO.
1384
+
1385
+
MAN_LINKS = NO
1386
+
1387
+
#---------------------------------------------------------------------------
1388
+
# configuration options related to the XML output
1389
+
#---------------------------------------------------------------------------
1390
+
1391
+
# If the GENERATE_XML tag is set to YES Doxygen will
1392
+
# generate an XML file that captures the structure of
1393
+
# the code including all documentation.
1394
+
1395
+
GENERATE_XML = NO
1396
+
1397
+
# The XML_OUTPUT tag is used to specify where the XML pages will be put.
1398
+
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1399
+
# put in front of it. If left blank `xml' will be used as the default path.
1400
+
1401
+
XML_OUTPUT = xml
1402
+
1403
+
# The XML_SCHEMA tag can be used to specify an XML schema,
1404
+
# which can be used by a validating XML parser to check the
1405
+
# syntax of the XML files.
1406
+
1407
+
XML_SCHEMA =
1408
+
1409
+
# The XML_DTD tag can be used to specify an XML DTD,
1410
+
# which can be used by a validating XML parser to check the
1411
+
# syntax of the XML files.
1412
+
1413
+
XML_DTD =
1414
+
1415
+
# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
1416
+
# dump the program listings (including syntax highlighting
1417
+
# and cross-referencing information) to the XML output. Note that
1418
+
# enabling this will significantly increase the size of the XML output.
1419
+
1420
+
XML_PROGRAMLISTING = YES
1421
+
1422
+
#---------------------------------------------------------------------------
1423
+
# configuration options for the AutoGen Definitions output
1424
+
#---------------------------------------------------------------------------
1425
+
1426
+
# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
1427
+
# generate an AutoGen Definitions (see autogen.sf.net) file
1428
+
# that captures the structure of the code including all
1429
+
# documentation. Note that this feature is still experimental
1430
+
# and incomplete at the moment.
1431
+
1432
+
GENERATE_AUTOGEN_DEF = NO
1433
+
1434
+
#---------------------------------------------------------------------------
1435
+
# configuration options related to the Perl module output
1436
+
#---------------------------------------------------------------------------
1437
+
1438
+
# If the GENERATE_PERLMOD tag is set to YES Doxygen will
1439
+
# generate a Perl module file that captures the structure of
1440
+
# the code including all documentation. Note that this
1441
+
# feature is still experimental and incomplete at the
1442
+
# moment.
1443
+
1444
+
GENERATE_PERLMOD = NO
1445
+
1446
+
# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
1447
+
# the necessary Makefile rules, Perl scripts and LaTeX code to be able
1448
+
# to generate PDF and DVI output from the Perl module output.
1449
+
1450
+
PERLMOD_LATEX = NO
1451
+
1452
+
# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
1453
+
# nicely formatted so it can be parsed by a human reader. This is useful
1454
+
# if you want to understand what is going on. On the other hand, if this
1455
+
# tag is set to NO the size of the Perl module output will be much smaller
1456
+
# and Perl will parse it just the same.
1457
+
1458
+
PERLMOD_PRETTY = YES
1459
+
1460
+
# The names of the make variables in the generated doxyrules.make file
1461
+
# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
1462
+
# This is useful so different doxyrules.make files included by the same
1463
+
# Makefile don't overwrite each other's variables.
1464
+
1465
+
PERLMOD_MAKEVAR_PREFIX =
1466
+
1467
+
#---------------------------------------------------------------------------
1468
+
# Configuration options related to the preprocessor
1469
+
#---------------------------------------------------------------------------
1470
+
1471
+
# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1472
+
# evaluate all C-preprocessor directives found in the sources and include
1473
+
# files.
1474
+
1475
+
ENABLE_PREPROCESSING = YES
1476
+
1477
+
# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1478
+
# names in the source code. If set to NO (the default) only conditional
1479
+
# compilation will be performed. Macro expansion can be done in a controlled
1480
+
# way by setting EXPAND_ONLY_PREDEF to YES.
1481
+
1482
+
MACRO_EXPANSION = NO
1483
+
1484
+
# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1485
+
# then the macro expansion is limited to the macros specified with the
1486
+
# PREDEFINED and EXPAND_AS_DEFINED tags.
1487
+
1488
+
EXPAND_ONLY_PREDEF = NO
1489
+
1490
+
# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1491
+
# pointed to by INCLUDE_PATH will be searched when a #include is found.
1492
+
1493
+
SEARCH_INCLUDES = YES
1494
+
1495
+
# The INCLUDE_PATH tag can be used to specify one or more directories that
1496
+
# contain include files that are not input files but should be processed by
1497
+
# the preprocessor.
1498
+
1499
+
INCLUDE_PATH =
1500
+
1501
+
# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1502
+
# patterns (like *.h and *.hpp) to filter out the header-files in the
1503
+
# directories. If left blank, the patterns specified with FILE_PATTERNS will
1504
+
# be used.
1505
+
1506
+
INCLUDE_FILE_PATTERNS =
1507
+
1508
+
# The PREDEFINED tag can be used to specify one or more macro names that
1509
+
# are defined before the preprocessor is started (similar to the -D option of
1510
+
# gcc). The argument of the tag is a list of macros of the form: name
1511
+
# or name=definition (no spaces). If the definition and the = are
1512
+
# omitted =1 is assumed. To prevent a macro definition from being
1513
+
# undefined via #undef or recursively expanded use the := operator
1514
+
# instead of the = operator.
1515
+
1516
+
PREDEFINED =
1517
+
1518
+
# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1519
+
# this tag can be used to specify a list of macro names that should be expanded.
1520
+
# The macro definition that is found in the sources will be used.
1521
+
# Use the PREDEFINED tag if you want to use a different macro definition that
1522
+
# overrules the definition found in the source code.
1523
+
1524
+
EXPAND_AS_DEFINED =
1525
+
1526
+
# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1527
+
# doxygen's preprocessor will remove all references to function-like macros
1528
+
# that are alone on a line, have an all uppercase name, and do not end with a
1529
+
# semicolon, because these will confuse the parser if not removed.
1530
+
1531
+
SKIP_FUNCTION_MACROS = YES
1532
+
1533
+
#---------------------------------------------------------------------------
1534
+
# Configuration::additions related to external references
1535
+
#---------------------------------------------------------------------------
1536
+
1537
+
# The TAGFILES option can be used to specify one or more tagfiles.
1538
+
# Optionally an initial location of the external documentation
1539
+
# can be added for each tagfile. The format of a tag file without
1540
+
# this location is as follows:
1541
+
# TAGFILES = file1 file2 ...
1542
+
# Adding location for the tag files is done as follows:
1543
+
# TAGFILES = file1=loc1 "file2 = loc2" ...
1544
+
# where "loc1" and "loc2" can be relative or absolute paths or
1545
+
# URLs. If a location is present for each tag, the installdox tool
1546
+
# does not have to be run to correct the links.
1547
+
# Note that each tag file must have a unique name
1548
+
# (where the name does NOT include the path)
1549
+
# If a tag file is not located in the directory in which doxygen
1550
+
# is run, you must also specify the path to the tagfile here.
1551
+
1552
+
TAGFILES =
1553
+
1554
+
# When a file name is specified after GENERATE_TAGFILE, doxygen will create
1555
+
# a tag file that is based on the input files it reads.
1556
+
1557
+
GENERATE_TAGFILE =
1558
+
1559
+
# If the ALLEXTERNALS tag is set to YES all external classes will be listed
1560
+
# in the class index. If set to NO only the inherited external classes
1561
+
# will be listed.
1562
+
1563
+
ALLEXTERNALS = NO
1564
+
1565
+
# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1566
+
# in the modules index. If set to NO, only the current project's groups will
1567
+
# be listed.
1568
+
1569
+
EXTERNAL_GROUPS = YES
1570
+
1571
+
# The PERL_PATH should be the absolute path and name of the perl script
1572
+
# interpreter (i.e. the result of `which perl').
1573
+
1574
+
PERL_PATH = /usr/bin/perl
1575
+
1576
+
#---------------------------------------------------------------------------
1577
+
# Configuration options related to the dot tool
1578
+
#---------------------------------------------------------------------------
1579
+
1580
+
# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1581
+
# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1582
+
# or super classes. Setting the tag to NO turns the diagrams off. Note that
1583
+
# this option also works with HAVE_DOT disabled, but it is recommended to
1584
+
# install and use dot, since it yields more powerful graphs.
1585
+
1586
+
CLASS_DIAGRAMS = YES
1587
+
1588
+
# You can define message sequence charts within doxygen comments using the \msc
1589
+
# command. Doxygen will then run the mscgen tool (see
1590
+
# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the
1591
+
# documentation. The MSCGEN_PATH tag allows you to specify the directory where
1592
+
# the mscgen tool resides. If left empty the tool is assumed to be found in the
1593
+
# default search path.
1594
+
1595
+
MSCGEN_PATH =
1596
+
1597
+
# If set to YES, the inheritance and collaboration graphs will hide
1598
+
# inheritance and usage relations if the target is undocumented
1599
+
# or is not a class.
1600
+
1601
+
HIDE_UNDOC_RELATIONS = YES
1602
+
1603
+
# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1604
+
# available from the path. This tool is part of Graphviz, a graph visualization
1605
+
# toolkit from AT&T and Lucent Bell Labs. The other options in this section
1606
+
# have no effect if this option is set to NO (the default)
1607
+
1608
+
HAVE_DOT = NO
1609
+
1610
+
# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is
1611
+
# allowed to run in parallel. When set to 0 (the default) doxygen will
1612
+
# base this on the number of processors available in the system. You can set it
1613
+
# explicitly to a value larger than 0 to get control over the balance
1614
+
# between CPU load and processing speed.
1615
+
1616
+
DOT_NUM_THREADS = 0
1617
+
1618
+
# By default doxygen will use the Helvetica font for all dot files that
1619
+
# doxygen generates. When you want a differently looking font you can specify
1620
+
# the font name using DOT_FONTNAME. You need to make sure dot is able to find
1621
+
# the font, which can be done by putting it in a standard location or by setting
1622
+
# the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the
1623
+
# directory containing the font.
1624
+
1625
+
DOT_FONTNAME = Helvetica
1626
+
1627
+
# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.
1628
+
# The default size is 10pt.
1629
+
1630
+
DOT_FONTSIZE = 10
1631
+
1632
+
# By default doxygen will tell dot to use the Helvetica font.
1633
+
# If you specify a different font using DOT_FONTNAME you can use DOT_FONTPATH to
1634
+
# set the path where dot can find it.
1635
+
1636
+
DOT_FONTPATH =
1637
+
1638
+
# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1639
+
# will generate a graph for each documented class showing the direct and
1640
+
# indirect inheritance relations. Setting this tag to YES will force the
1641
+
# the CLASS_DIAGRAMS tag to NO.
1642
+
1643
+
CLASS_GRAPH = YES
1644
+
1645
+
# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1646
+
# will generate a graph for each documented class showing the direct and
1647
+
# indirect implementation dependencies (inheritance, containment, and
1648
+
# class references variables) of the class with other documented classes.
1649
+
1650
+
COLLABORATION_GRAPH = YES
1651
+
1652
+
# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
1653
+
# will generate a graph for groups, showing the direct groups dependencies
1654
+
1655
+
GROUP_GRAPHS = YES
1656
+
1657
+
# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1658
+
# collaboration diagrams in a style similar to the OMG's Unified Modeling
1659
+
# Language.
1660
+
1661
+
UML_LOOK = NO
1662
+
1663
+
# If set to YES, the inheritance and collaboration graphs will show the
1664
+
# relations between templates and their instances.
1665
+
1666
+
TEMPLATE_RELATIONS = NO
1667
+
1668
+
# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1669
+
# tags are set to YES then doxygen will generate a graph for each documented
1670
+
# file showing the direct and indirect include dependencies of the file with
1671
+
# other documented files.
1672
+
1673
+
INCLUDE_GRAPH = YES
1674
+
1675
+
# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1676
+
# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1677
+
# documented header file showing the documented files that directly or
1678
+
# indirectly include this file.
1679
+
1680
+
INCLUDED_BY_GRAPH = YES
1681
+
1682
+
# If the CALL_GRAPH and HAVE_DOT options are set to YES then
1683
+
# doxygen will generate a call dependency graph for every global function
1684
+
# or class method. Note that enabling this option will significantly increase
1685
+
# the time of a run. So in most cases it will be better to enable call graphs
1686
+
# for selected functions only using the \callgraph command.
1687
+
1688
+
CALL_GRAPH = NO
1689
+
1690
+
# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then
1691
+
# doxygen will generate a caller dependency graph for every global function
1692
+
# or class method. Note that enabling this option will significantly increase
1693
+
# the time of a run. So in most cases it will be better to enable caller
1694
+
# graphs for selected functions only using the \callergraph command.
1695
+
1696
+
CALLER_GRAPH = NO
1697
+
1698
+
# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1699
+
# will generate a graphical hierarchy of all classes instead of a textual one.
1700
+
1701
+
GRAPHICAL_HIERARCHY = YES
1702
+
1703
+
# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
1704
+
# then doxygen will show the dependencies a directory has on other directories
1705
+
# in a graphical way. The dependency relations are determined by the #include
1706
+
# relations between the files in the directories.
1707
+
1708
+
DIRECTORY_GRAPH = YES
1709
+
1710
+
# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1711
+
# generated by dot. Possible values are svg, png, jpg, or gif.
1712
+
# If left blank png will be used. If you choose svg you need to set
1713
+
# HTML_FILE_EXTENSION to xhtml in order to make the SVG files
1714
+
# visible in IE 9+ (other browsers do not have this requirement).
1715
+
1716
+
DOT_IMAGE_FORMAT = png
1717
+
1718
+
# If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
1719
+
# enable generation of interactive SVG images that allow zooming and panning.
1720
+
# Note that this requires a modern browser other than Internet Explorer.
1721
+
# Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you
1722
+
# need to set HTML_FILE_EXTENSION to xhtml in order to make the SVG files
1723
+
# visible. Older versions of IE do not have SVG support.
1724
+
1725
+
INTERACTIVE_SVG = NO
1726
+
1727
+
# The tag DOT_PATH can be used to specify the path where the dot tool can be
1728
+
# found. If left blank, it is assumed the dot tool can be found in the path.
1729
+
1730
+
DOT_PATH =
1731
+
1732
+
# The DOTFILE_DIRS tag can be used to specify one or more directories that
1733
+
# contain dot files that are included in the documentation (see the
1734
+
# \dotfile command).
1735
+
1736
+
DOTFILE_DIRS =
1737
+
1738
+
# The MSCFILE_DIRS tag can be used to specify one or more directories that
1739
+
# contain msc files that are included in the documentation (see the
1740
+
# \mscfile command).
1741
+
1742
+
MSCFILE_DIRS =
1743
+
1744
+
# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
1745
+
# nodes that will be shown in the graph. If the number of nodes in a graph
1746
+
# becomes larger than this value, doxygen will truncate the graph, which is
1747
+
# visualized by representing a node as a red box. Note that doxygen if the
1748
+
# number of direct children of the root node in a graph is already larger than
1749
+
# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
1750
+
# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
1751
+
1752
+
DOT_GRAPH_MAX_NODES = 50
1753
+
1754
+
# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1755
+
# graphs generated by dot. A depth value of 3 means that only nodes reachable
1756
+
# from the root by following a path via at most 3 edges will be shown. Nodes
1757
+
# that lay further from the root node will be omitted. Note that setting this
1758
+
# option to 1 or 2 may greatly reduce the computation time needed for large
1759
+
# code bases. Also note that the size of a graph can be further restricted by
1760
+
# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
1761
+
1762
+
MAX_DOT_GRAPH_DEPTH = 0
1763
+
1764
+
# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1765
+
# background. This is disabled by default, because dot on Windows does not
1766
+
# seem to support this out of the box. Warning: Depending on the platform used,
1767
+
# enabling this option may lead to badly anti-aliased labels on the edges of
1768
+
# a graph (i.e. they become hard to read).
1769
+
1770
+
DOT_TRANSPARENT = NO
1771
+
1772
+
# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
1773
+
# files in one run (i.e. multiple -o and -T options on the command line). This
1774
+
# makes dot run faster, but since only newer versions of dot (>1.8.10)
1775
+
# support this, this feature is disabled by default.
1776
+
1777
+
DOT_MULTI_TARGETS = NO
1778
+
1779
+
# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1780
+
# generate a legend page explaining the meaning of the various boxes and
1781
+
# arrows in the dot generated graphs.
1782
+
1783
+
GENERATE_LEGEND = YES
1784
+
1785
+
# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1786
+
# remove the intermediate dot files that are used to generate
1787
+
# the various graphs.
1788
+
1789
+
DOT_CLEANUP = YES