Conventions

In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.

Code words in text, folder names, filenames, file extensions, pathnames, system variables, URLs, and user input are shown as follows: "Each module has an associated header file (for example, core.hpp)."

A block of code is set as follows:

#include "opencv2/core/core.hpp"
#include "opencv2/highgui/highgui.hpp"
using namespace std;
using namespace cv;

int main(int argc, char *argv[])
{
  Mat frame; // Container for each frame

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

#include "opencv2/core/core.hpp"
#include "opencv2/highgui/highgui.hpp"
#include <iostream>

using namespace std;
using namespace cv;

int main(int argc, char *argv[])
{

Any command-line input or output is written as follows:

C:opencv-buildQtinstall

New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "Also, the checkboxes labeled as Grouped and Advanced should be marked in the CMake main window."

Note

Warnings or important notes appear in a box like this.

Tip

Tips and tricks appear like this.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset