Problem Description:
As the beginning of the design pattern, I just saw the implementation of the QSplashScreen class today. Let's take this class first.
In the process of learning C++ programming, our technology stack can basically be used for server-side and client-side programming according to many recruitment requirements. Server-side programming is basically reflected in network programming. Client programming is basically reflected in GUI programming.
Of course, the function libraries on both sides have their own advantages. Qt not only writes an interface, but itself is a framework at the same level as C++STL, boost and other function API libraries. STL and boost are richer in terms of algorithms, networks, and concurrency. If you want to transfer to this area of work, you can study in advance.
But at the end of the day, the language is the same. Java, Python, Web language, Go, etc., all have their own areas of expertise. And Qt is good at the client field, mainly desktop, embedded devices, mobile devices and so on.
Next I will share about the design issues in the Qt framework. Let's start with QSplashScreen.
Solution:
Here we do not analyze in the order of abstract class, root class, and module class. It is more formal and takes a lot of time to write. I'll just be casual here.
Open the Src directory under the Qt installation directory. Find the path location, qtbase/src/widgets/widgets/qsplashscreen.cpp
QSplashScreen