add_new_open_project_signal.diff
| src/app/qgisappinterface.cpp (working copy) | ||
|---|---|---|
| 52 | 52 |
this, SIGNAL( composerWillBeRemoved( QgsComposerView* ) ) ); |
| 53 | 53 |
connect( qgis, SIGNAL( initializationCompleted() ), |
| 54 | 54 |
this, SIGNAL( initializationCompleted() ) ); |
| 55 |
connect( qgis, SIGNAL( newProject() ), |
|
| 56 |
this, SIGNAL( newProjectCreated() ) ); |
|
| 57 |
connect( qgis, SIGNAL( projectRead() ), |
|
| 58 |
this, SIGNAL( projectRead() ) ); |
|
| 55 | 59 |
} |
| 56 | 60 | |
| 57 | 61 |
QgisAppInterface::~QgisAppInterface() |
| src/gui/qgisinterface.h (working copy) | ||
|---|---|---|
| 322 | 322 |
/**This signal is emitted when the initialization is complete |
| 323 | 323 |
@note added in version 1.6*/ |
| 324 | 324 |
void initializationCompleted(); |
| 325 |
/** emitted when a project file is successfully read |
|
| 326 |
@note |
|
| 327 |
This is useful for plug-ins that store properties with project files. A |
|
| 328 |
plug-in can connect to this signal. When it is emitted, the plug-in |
|
| 329 |
knows to then check the project properties for any relevant state. |
|
| 330 | ||
| 331 |
*/ |
|
| 332 |
void projectRead(); |
|
| 333 |
/** emitted when starting an entirely new project |
|
| 334 |
@note |
|
| 335 |
This is similar to projectRead(); plug-ins might want to be notified |
|
| 336 |
that they're in a new project. Yes, projectRead() could have been |
|
| 337 |
overloaded to be used in the case of new projects instead. However, |
|
| 338 |
it's probably more semantically correct to have an entirely separate |
|
| 339 |
signal for when this happens. |
|
| 340 |
*/ |
|
| 341 |
void newProjectCreated(); |
|
| 342 | ||
| 325 | 343 |
}; |
| 326 | 344 | |
| 327 | 345 |
// FIXME: also in core/qgis.h |