|  | Home · Overviews · Examples

# Qt Tutorial 4 - Let There Be Widgets

This example shows how to create your own widget, and describes how to control the minimum and maximum sizes of a widget. Missing snippet: tutorials/tutorial/t4/main.cpp.
Missing snippet: tutorials/tutorial/t4/main.cpp.
Missing snippet: tutorials/tutorial/t4/main.cpp.

## Line by Line Walkthrough

Missing snippet: tutorials/tutorial/t4/main.cpp. Here we create a new class. Because this class inherits from QWidget, the new class is a widget and may be a top-level window or a child widget (like the QPushButton in the previous chapter).

This class has only one member, a constructor (in addition to the members it inherits from QWidget). The constructor is a standard Qt widget constructor; you should always include a similar constructor when you create widgets.

The argument is its parent widget. To create a top-level window you specify a null pointer as the parent. As you can see, this widget defaults to be a top-level window. Missing snippet: tutorials/tutorial/t4/main.cpp. The implementation of the constructor starts here. Like most widgets, it just passes on the `parent` to the QWidget constructor. Missing snippet: tutorials/tutorial/t4/main.cpp. Because this widget doesn't know how to handle resizing, we fix its size. In the next chapter, we will show how a widget can respond to resize event from the user. Missing snippet: tutorials/tutorial/t4/main.cpp. Here we create and set up a child widget of this widget (the new widget's parent is `this`, i.e. the `MyWidget` instance).

The tr() function call around the string literal "Quit" marks the string for translation, making it possible to change it at run-time based on the contents of a translation file. It is a good habit to use tr() around all user-visible strings, in case you decide later to translate your application to other languages.

Note that `quit` is a local variable in the constructor. `MyWidget` does not keep track of it; Qt does, and will automatically delete it when the `MyWidget` object is deleted. This is why `MyWidget` doesn't need a destructor. (On the other hand, there is no harm in deleting a child when you choose to. The child will automatically tell Qt about its imminent death.)

The QWidget::setGeometry() call sets both the widget's screen position and the size. It is equivalent to calling QWidget::move() followed by QWidget::resize(). Missing snippet: tutorials/tutorial/t4/main.cpp. The `qApp` pointer is a global variable declared in the `<QApplication>` header file. It points to the application's unique QApplication instance. Missing snippet: tutorials/tutorial/t4/main.cpp. Here we instantiate our new child, show it, and execute the application.

## Running the Application

This program is very similar in behavior to the previous one. The difference lies in the way we have implemented it. It does behave slightly differently, however. Just try to resize it to see.

## Exercises

Try to create another `MyWidget` object in `main()`. What happens?

Try to add more buttons or put in widgets other than QPushButton.