![\"wxPython](\"https:\/\/www.digitalvidya.com\/blog\/wp-content\/uploads\/2019\/09\/wxpython-mini-logo.jpg\" "\\"\\""){kind=logo}
There are five major wxPython modules namely:<\/span><\/p>\n 1. Controls:<\/strong> It is a collection of all the widgets used in a Graphical application. Widgets are also known as controls in the Windows operating system. For example, static text, button, toolbar, editable text control, etc.<\/span><\/p>\n 2. Windows:<\/strong> This module contains all the window classes such as a frame, a panel, a dialogue, a scrolled window, etc.<\/span><\/p>\n 3. Misc:<\/strong> This module contains various functions and classes of modules that help in various functions such as system settings, the configuration of applications, logging in or controlling the display.<\/span><\/p>\n 4. Core:<\/strong> This module contains all the principle class used for the development of graphical user interface-based applications. These classes consist of wxObject class which is the foundation of all other classes, Sizers used for widget layout, basic geometry classes and events.<\/span><\/p>\n 5. GDI:<\/strong> wxPython API has a Graphical device interface module which is a collection of classes used for drawing onto the widgets. This contains classes such as color, brush, fonts, images, or pens, etc.<\/span><\/p>\n wxPython is a library that is used by programmers to code applications. Since wxPython is a wrapper around wxWidgets, therefore, it is not a native API and hence is not written directly in Python. wxPython has numerous widgets, they are the elementary base of any GUI application. The widgets can be grouped into five categories<\/span><\/p>\n There is a connection between widgets in wxPython, such a relation is formed on the base of inheritance. This is a vital part of the object-oriented programming language. Widgets derive functionality from the other widgets and hence creating inheritance. The widgets which provide the functionality to other widgets are known as parent widgets or base widgets or ancestors, whereas the widgets that inherit are known as child widgets, derived widgets or descendants.\u00a0<\/span><\/p>\n Let us understand this if we use a button widget in our application that derives from four other base widgets. The first one being the wx.Control class. A button widget is similar to a tiny window and basically, mostly all widgets that appear on the screen are windows. Thus they derive from wx.Window class. Some of the objects are invisible such as sizers, device context or locale objects. There exist classes which are visible but they are not windows, for example, a colour object, caret object or a cursor object. wx.A dialog is not any type of control, thus not every object a control. The controls are placed on the widgets which are known as containers. The reason due to which it has a separate wx. Control base class.<\/span><\/p>\n Every window and button widgets revert to events. By clicking on the button, the wx.EVT_COMMAND_BUTTON_CLICKED event is launched. The button widget derives the wx.EvtHandler through the wx.Window class. Every widget that reacts to events should inherit from wx.EvtHandler class and thus all objects inherit from wx.Object class.<\/span><\/p>\n wxPython 4 the Phoenix release being the latest one should be used here. The wxPython 3 and wxPython 2 are suited only for wxPython 2. Robin Dunn, the developer of wxPython cleared a lot of codes to make wxPython 4 easier to understand and even more Pythonic, it is even suitable for both wxPython 2.7 and wxPython 3.<\/span><\/p>\n Following links must be considered if you are migrating from an older version of wxPython to wxPython 4 (Phoenix):<\/span><\/p>\n<\/span>wxPython API\u00a0<\/strong><\/span><\/h2>\n
\n
<\/span>Inheritance<\/strong><\/span><\/h2>\n
<\/span>Installing wxPython<\/strong><\/span><\/h2>\n
![\"What](\"https:\/\/www.digitalvidya.com\/blog\/wp-content\/uploads\/2019\/09\/download-1.jpg\" "\\"\\"")