Solution "Longest Substring Without Repeating Characters" on Leet Code

Solution "Add Two Numbers" on Leet Code

Two Sum solution on Leet Code

Let's take a look at a small code example when a method is called on an object that is initialized with nullptr .

This article is the most comprehensive description of signals and slots in QML compared to all previous articles on this site.

In this article, I will try to explain the following when working with Qt/QML + Qt/C++:

• ways to declare signals and slots, also called methods in the C ++ class, which will be registered in the QML layer
• ways to connect to signals of classes declared in C ++ as context
• work with Q_PROPERTY, which also requires signals and slots
• ways to connect signals and slots in QML
• etc.

I propose to consider the option of using variables declared in the CMakeLists.txt file in C ++ code.

To begin with, what is it for? For example, you want to specify the version of the program and some other auxiliary information that is set during the assembly of the program, but at the same time you want to use this information in your C ++ code? Is it possible to do this? For example, to make it look like the image shows.

A small note about static linking Boost, so as not to forget.

Initial data:

• OS Windows
• MSVC 2017 64bit
• Boost 1.68.0
• CMake project

An example will be shown in the simplest version without special variable settings. Maximum default.

Let's write a small example of an application in which a button will be moved using property animations. To do this, we use the QSequentialAnimationGroup and QPropertyAnimation classes.

QSequentialAnimationGroup is a class that combines several animations into one group, which allows you to automatically start one animation when the previous QPropertyAnimation has completed.

Animation will be launched by pressing the button and this button will move in the window as shown in the image.

And here is an article on the boost of my some accumulated materials. I offer you the option of writing a console program with support for the console menu, which is implemented using boost::program_options .

boost::program_options is responsible for processing the arguments passed to the program and sets all the necessary variables without the need to implement long logic from if else branches. This is already implemented inside boost::program_optons .

Suppose our program takes the following data as arguments

• input file path
• output file path
• the size of the block being processed, no matter why, we will not do anything with it, just have such a parameter in the program.

Also, the program will have a help menu, which will be the console menu.

The figure below shows the use of this program.

Start at work to use a compiler that supports the standard C++17.

Actively we begin to use various features from this standard..

I was pleased with the [[fallthrough]] attribute for switch case constructions.