QgisInterface.__attribute_docs__={'currentLayerChanged':'Emitted whenever current (selected) layer changes.\nThe pointer to layer can be ``None`` if no layer is selected.\n','currentThemeChanged':'Emitted when the current ``theme`` is changed so plugins\ncan change their tool button icons.\n','layoutDesignerOpened':'Emitted when a new layout ``designer`` has been opened.\n\n.. seealso:: :py:func:`layoutDesignerWillBeClosed`\n','layoutDesignerWillBeClosed':'Emitted before a layout ``designer`` is going to be closed\nand deleted.\n\n.. seealso:: :py:func:`layoutDesignerClosed`\n\n.. seealso:: :py:func:`layoutDesignerOpened`\n','layoutDesignerClosed':'Emitted after a layout designer window is closed.\n\n.. seealso:: :py:func:`layoutDesignerWillBeClosed`\n\n.. seealso:: :py:func:`layoutDesignerOpened`\n','initializationCompleted':'Emitted when the initialization is complete.\n','projectRead':'Emitted when a project file is successfully read.\n\n.. note::\n\n This is useful for plugins that store properties with project files.\n A plugin can connect to this signal. When it is emitted the plugin\n knows to then check the project properties for any relevant state.\n','newProjectCreated':"Emitted when starting an entirely new project.\n\n.. note::\n\n This is similar to :py:func:`~QgisInterface.projectRead`; plugins might want to be notified\n that they're in a new project. Yes, :py:func:`~QgisInterface.projectRead` could have been\n overloaded to be used in the case of new projects instead. However,\n it's probably more semantically correct to have an entirely separate\n signal for when this happens.\n",'layerSavedAs':'Emitted when a layer has been saved using save as.\n'}
