I did some more poking around and found that this (declaratively enabling labels) was something that was addressed in the last release of the Qt SDK (which both beta 3 and beta 4 of AppStudio does use). The following sample does work for me - but unfortunately (or fortunately - depends which way you look at it!) it resembles first case that you describe. ie:
FeatureLayer {
enableLabels: true
}
The last part of the sample is indeed a button to change state of the labels (to see the change in this example change the initial state of the labels to false. I wonder if the problem your seeing is to do with the order of the components?
import QtQuick 2.3
import QtQuick.Controls 1.2
import ArcGIS.AppFramework 1.0
import ArcGIS.AppFramework.Runtime 1.0
App { id: app
width: 400
height: 640
Geodatabase { id: gdb
path: "C:\\Users\\Marika\\Desktop\\QtTest\\QtTest\\azlandbase.geodatabase"
}
Map { id: mainMap
anchors.fill: parent
GeodatabaseFeatureTable { id: gdbFT
geodatabase: gdb.valid ? gdb : null
featureServiceLayerId: 0
}
FeatureLayer { id: featureLayer_DM
featureTable: gdbFT
enableLabels: true
}
}
Button { anchors { left: parent.left
top: parent.top
}
text: " enable labels"
onClicked: { console.log("labels enabled?", featureLayer_DM.enableLabels); featureLayer_DM.enableLabels = true;
console.log("labels enabled?", featureLayer_DM.enableLabels); }
}
}
