Fix inconsistent UI/UX for read-only non-spatial layers (#3635)

* wip - enhancing ui/ux * adding layerIsReadOnly condition to add feature button to be visible * using current layer property
MerginMaps · Oct 8, 2024 · b2eff70 · b2eff70 · inputapp-bot · Oct 8, 2024
1 parent 153c496
commit b2eff70
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/app/qml/layers/MMFeaturesListPage.qml b/app/qml/layers/MMFeaturesListPage.qml
@@ -21,6 +21,7 @@ MMComponents.MMPage {
 
   property var selectedLayer: null
   property bool hasToolbar: false
+  property bool layerIsReadOnly: selectedLayer?.readOnly ?? false
 
   signal featureClicked( var featurePair )
   signal addFeatureClicked( var toLayer )
@@ -91,7 +92,7 @@ MMComponents.MMPage {
       anchors.bottom: parent.bottom
       anchors.bottomMargin: root.hasToolbar ? __style.margin20 : ( __style.safeAreaBottom + __style.margin8 )
 
-      visible: __inputUtils.isNoGeometryLayer( root.selectedLayer )
+      visible: __inputUtils.isNoGeometryLayer( root.selectedLayer ) && !root.layerIsReadOnly
 
       text: qsTr("Add feature")