blob: 41538570042063916c6259d0664b53d99982aab6 (
plain)
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
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
|
// Copyright (C) 2020 The Qt Company Ltd.
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only
// **********************************************************************
// NOTE: the sections are not ordered by their logical order to avoid
// reshuffling the file each time the index order changes (i.e., often).
// Run the fixnavi.pl script to adjust the links to the index order.
// **********************************************************************
/*!
\previouspage creator-editor-external.html
\page creator-task-lists.html
\nextpage creator-logging-viewer.html
\title Showing Task List Files in Issues
You can use code scanning and analysis tools to examine source code. These
tools report issues for you to fix. \QC enables you to load lists of
issues into \l Issues for easier navigation.
\QC expects tasks to be defined in a simple line-based file format that is
easy to generate using scripts. The scripts can either convert reports from
other tools or create lists of issues in the \l{Task List File Format}
{task list format} from code. For an example of a script that checks new
lines of code and matches them against regular expressions to generate a
task list, see \c{scripts\mytasks.pl} in the \QC repository.
\section1 Managing Task List Entries
To open task list files in \uicontrol Issues, choose \uicontrol File >
\uicontrol Open. Right-click a task list entry to open a context menu that
contains commands for managing the entry. You can copy or remove task list
entries or navigate to the corresponding source code.
\QC monitors the loaded files and displays the changes in \uicontrol Issues.
To keep the current entries in a task list, but stop checking for
changes, select \uicontrol {Stop Monitoring}.
\section1 Task List File Format
The filename extension must be .tasks for \QC to recognize a file as a
task list file.
Each line in a task list file is treated as a tab-separated list of strings
with \c{\t}, \c{\n}, and \c{\\} used as escape characters. The strings are
used to create one task per line. The lines can have one of the following
formats:
\list
\li \c description
\li \c{type\tdescription}
\li \c{file\ttype\tdescription}
\li \c{file\tline\ttype\tdescription}
\endlist
The task type can have one of the following values:
\list
\li A string starting with \c err, which displays the error icon in the
beginning of the line
\li A string starting with \c warn, which displays the warning icon
\li Any other value, which sets the task type to Unknown and does not
display an icon
\endlist
The values are not case sensitive.
Lines starting with the hash mark character (#) in the first column are
ignored.
If the file path is given as a relative path, it is based on the parent
directory of the task list file.
*/
|
