SessionWidgetBase¶
Methods¶
qconcurrency.widgets._sessionwidgets_.SessionWidgetBase.__init__() |
|
qconcurrency.widgets._sessionwidgets_.SessionWidgetBase.get_changes() |
Returns a dict of unsaved changes that this widget contains. |
qconcurrency.widgets._sessionwidgets_.SessionWidgetBase.has_changes() |
Returns True if this widget has any unsaved changes. |
qconcurrency.widgets._sessionwidgets_.SessionWidgetBase.items() |
Returns a dictionary in the format of { _id:item } |
qconcurrency.widgets._sessionwidgets_.SessionWidgetBase.save_changes() |
If checks for unsaved new,changed, or deleted items, and if changes exist, emits save_requested signal. |
qconcurrency.widgets._sessionwidgets_.SessionWidgetBase.save_requested |
output of get_changes() |
Documentation¶
-
class
qconcurrency.widgets._sessionwidgets_.SessionWidgetBase[source]¶ Bases:
objectBaseWidget for SessionWidgets.
SessionWidgets are collection-widgets that are designed to allow the user to perform several operations, and then save them all at once.
-
get_changes()[source]¶ Returns a dict of unsaved changes that this widget contains.
Returns: { ‘new’: { _id : widget, … }, ‘deleted’: set([ _id, _id, … ]), ‘changed’: { _id : widget, … }, }
-
save_changes()[source]¶ If checks for unsaved new,changed, or deleted items, and if changes exist, emits
save_requestedsignal.It is up to the calling class/method to handle the actual saving of the information, and as items are saved, this widget can be updated using the method
SessionWidgetItemBase.set_saved().
-
save_requested= <PySide.QtCore.Signal object>¶ output of
get_changes()
-