Hi Marco, >> What do you exactly mean with composer window class? >> QgsComposerView or QgsComposerView.composerWindow() = QMainWindow? > >As the signal would be needed for Plugins, I thought about adding it to >QgsComposerView class. Do you need any additional information coming with the >signal (e.g. which composerview it is)? >
Not at the moment. But I think knowing which composerView it is could be useful some day. So am I understanding you right that this is sth for the core and not for solving in the PlugIn? >> And is it right that the Map Composer is automatically opening after >> calling /self.iface.actionPrintComposer().trigger()/ >> so using the composerWindow() isn't necessary? > >composerWindow() is useful whenever you need to get a pointer to the window >(trigger() only opens a new one but then you don't have a pointer). > thx Regards, Michael -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/python-plugin-and-layer-properties-window-tp6383931p6532468.html Sent from the qgis-developer mailing list archive at Nabble.com. _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
