1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
*Protect software from erosion with static code analysis, architecture analysis, and code-smells-detection.*
# Prevent code erosion
Connect to an Axivion dashboard server from Qt Creator to view results of code analysis.
> **_Note:_** To use the Axivion extension, you must be connected to an Axivion
dashboard server.
# View inline annotations in editor
The editor shows found issues as inline annotations if the project matches the
currently open one and the respective file is part of the project. Hover the
mouse over an annotation to bring up a tooltip with a short description of the
issue.
Select  to view detailed
information about the issue in the `Issue Details` view.
To hide inline annotations, go to `Analyze > Axivion` and clear
.
# View issues
To inspect issues found during the analyses, go to `Analyze > Axivion`.
Axivion looks for the following types of issues in the selected project:
| Icon | Type | Description |
|-------|-------|--------------|
|  | AV | Architecture violations, such as hidden dependencies. |
|  | CL | Clones, such as duplicates and similar pieces of code. |
|  | CY | Cyclic dependencies, such as call, component, and include cycles. |
|  | DE | Dead entities are callable entities in the source code that cannot be reached from the entry points of the system under analysis. |
|  | MV | Violations of metrics based on lines and tokens, nesting, cyclomatic complexity, control flow, and so on. |
|  | SV | Style violations, such as deviations from the naming or coding conventions. |
|
