Some plugin classes require additional functions to be implemented. QApplication ::setStyle( QStyleFactory ::create( 'MyStyle')) If you have a new style class called MyStyle that you want to make available as a plugin, the class needs to be defined as follows ( mystyleplugin.h): You can use them, but there is no compatibility promise with later Qt versions.

Some of the classes are private, and are therefore not documented. The following table summarizes the plugin base classes. Qt will not find plugins if they are not stored in the appropriate directory. Derived plugins are stored by default in sub-directories of the standard plugin directory. Writing a plugin that extends Qt itself is achieved by subclassing the appropriate plugin base class, implementing a few functions, and adding a macro. Topics: The High-Level API: Writing Qt Extensions If you want to provide plugins for use with Qt Designer, see the Qt Designer module documentation. Since the higher-level API is built on top of the lower-level API, some issues are common to both. A low-level API for extending Qt applications.įor example, if you want to write a custom QStyle subclass and have Qt applications load it dynamically, you would use the higher-level API.A high-level API for writing extensions to Qt itself: custom database drivers, image formats, text codecs, custom styles, etc.Qt provides two APIs for creating plugins:

Inkscape extensions metadata