class QAbstractFormBuilder#

The QAbstractFormBuilder class provides a default implementation for classes that create user interfaces at run-time. More…

Inherited by: QFormBuilder

Synopsis#

Methods#

def __init__()
def applyPropertyInternally()
def errorString()
def reset()
def setWorkingDirectory()
def workingDirectory()

Static functions#

def toolBarAreaMetaEnum()

Note

This documentation may contain snippets that were automatically translated from C++ to Python. We always welcome contributions to the snippet translation. If you see an issue with the translation, you can also let us know by creating a ticket on https:/bugreports.qt.io/projects/PYSIDE

Detailed Description#

Warning

This section contains snippets that were automatically translated from C++ to Python and may contain errors.

QAbstractFormBuilder provides a standard interface and a default implementation for constructing forms from user interface files. It is not intended to be instantiated directly. Use the QFormBuilder class to create user interfaces from UI files at run-time. For example:

    MyForm::MyForm(QWidget parent)
super().__init__(parent)

        builder = QFormBuilder()
        file = QFile(":/forms/myWidget.ui")
        file.open(QFile.ReadOnly)
        myWidget = builder.load(file, self)
        file.close()
        layout = QVBoxLayout(self)
        layout.addWidget(myWidget)

To override certain aspects of the form builder’s behavior, subclass QAbstractFormBuilder and reimplement the relevant virtual functions:

load() handles reading of UI format files from arbitrary QIODevices, and construction of widgets from the XML data that they contain.

save() handles saving of widget details in UI format to arbitrary QIODevices.

workingDirectory() and setWorkingDirectory() control the directory in which forms are held. The form builder looks for other resources on paths relative to this directory.

The QFormBuilder class is typically used by custom components and applications that embed Qt Designer. Standalone applications that need to dynamically generate user interfaces at run-time use the QUiLoader, found in the Qt UI Tools module.

See also

Qt UI Tools

__init__()#

Constructs a new form builder.

addMenuAction(action)#

Parameters:: action – QAction

applyPropertyInternally(o, propertyName, value)#

Parameters:

o – QObject
propertyName – str
value – object

Return type:

bool

checkProperty(obj, prop)#

Parameters:

obj – QObject
prop – str

Return type:

bool

createAction(parent, name)#

Parameters:

parent – QObject
name – str

Return type:

QAction

createActionGroup(parent, name)#

Parameters:

parent – QObject
name – str

Return type:

QActionGroup

createLayout(layoutName, parent, name)#

Parameters:

layoutName – str
parent – QObject
name – str

Return type:

QLayout

createWidget(widgetName, parentWidget, name)#

Parameters:

widgetName – str
parentWidget – QWidget
name – str

Return type:

QWidget

errorString()#

Return type:: str

Returns a human-readable description of the last error occurred in load() .

See also

load()

load(dev[, parentWidget=None])#

Parameters:

dev – QIODevice
parentWidget – QWidget

Return type:

QWidget

Loads an XML representation of a widget from the given device, and constructs a new widget with the specified parent.

See also

save() errorString()

reset()#

save(dev, widget)#

Parameters:

dev – QIODevice
widget – QWidget

Saves an XML representation of the given widget to the specified device in the standard UI file format.

Note

Unlike when saving a form in Qt Designer, all property values are written. This is because, the state of whether a property value was modified or not isn’t stored in the Qt property system. The widget that is being saved, could have been created dynamically, not loaded via load() , so in this case the form builder isn’t aware of the list of changed properties. Also, there’s no generic way to do this for widgets that were created dynamically.

Therefore, you should remove properties that are not required from your resulting XML files, before loading them. Alternatively, if you already know which properties you want to save when you call this method, you can overload computeProperties() and return a filtered list of required properties. Otherwise, unexpected behavior may occur as some of these properties may depend on each other.

See also

load()

setWorkingDirectory(directory)#

Parameters:: directory – QDir

Sets the current working directory of the form builder to the specified directory.

See also

workingDirectory()

static toolBarAreaMetaEnum()#

Return type:: QMetaEnum

workingDirectory()#

Return type:: QDir

Returns the current working directory of the form builder.

See also

setWorkingDirectory()