Return to Answer

Yes it has been removed, but alternatives exist.

Changes of the 3.0 API are listed here:

https://qgis.org/api/api_break.html

QgsMapLayerRegistry. Its functionality has been moved to QgsProject.

The main reason is, that QgsMapLayerRegistry is/was a singleton and therefore only a single registry could ever exist. With this constraint removed, major roadblocks are out of the way to implement new things like having multiple projects open side-by-side.

Yes it has been removed, but alternatives exist.

Changes of the 3.0 API are listed here:

https://qgis.org/api/api_break.html

QgsMapLayerRegistry: Its functionality has been moved to QgsProject.

The main reason is, that QgsMapLayerRegistry is/was a singleton and therefore only a single registry could ever exist. With this constraint removed, major roadblocks are out of the way to implement new things like having multiple projects open side-by-side.

Yes it has been removed.

Changes of the 3.0 API are listed here:

https://qgis.org/api/api_break.html

QgsMapLayerRegistry. Its functionality has been moved to QgsProject.

The main reason is, that QgsMapLayerRegistry is/was a singleton and therefore only a single registry could ever exist. With this constraint removed, major roadblocks are out of the way to implement new things like having multiple projects open side-by-side.

Yes it has been removed, but alternatives exist.

Changes of the 3.0 API are listed here:

https://qgis.org/api/api_break.html

QgsMapLayerRegistry. Its functionality has been moved to QgsProject.

The main reason is, that QgsMapLayerRegistry is/was a singleton and therefore only a single registry could ever exist. With this constraint removed, major roadblocks are out of the way to implement new things like having multiple projects open side-by-side.

Yes it has been removed.

Changes of the 3.0 API are listed here:

http://doc.qgis.org/api/api_break.html

QgsMapLayerRegistry. Its functionality has been moved to QgsProject.

The main reason is, that QgsMapLayerRegistry is/was a singleton and therefore only a single registry could ever exist. With this constraint removed, major roadblocks are out of the way to implement new things like having multiple projects open side-by-side.

Yes it has been removed.

Changes of the 3.0 API are listed here:

https://qgis.org/api/api_break.html

QgsMapLayerRegistry. Its functionality has been moved to QgsProject.

The main reason is, that QgsMapLayerRegistry is/was a singleton and therefore only a single registry could ever exist. With this constraint removed, major roadblocks are out of the way to implement new things like having multiple projects open side-by-side.