forked from qt-creator/qt-creator
QmlDesigner: Introduction of PropertyMetaInfo
Because the project storage is integer id based the string based API isn't fitting well for the new approach. PropertyMetaInfo can be easier mapped to the project storage. Task-number: QDS-7197 Change-Id: I49bc650abdaacf4b039d76c2514b5ad05ec84abe Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
This commit is contained in:
@@ -475,7 +475,7 @@ QStringList ConnectionModel::getPossibleSignalsForConnection(const ModelNode &co
|
||||
auto getAliasMetaSignals = [&](QString aliasPart, NodeMetaInfo metaInfo) {
|
||||
if (metaInfo.isValid() && metaInfo.hasProperty(aliasPart.toUtf8())) {
|
||||
NodeMetaInfo propertyMetaInfo = connectionView()->model()->metaInfo(
|
||||
metaInfo.propertyTypeName(aliasPart.toUtf8()));
|
||||
metaInfo.property(aliasPart.toUtf8()).propertyTypeName());
|
||||
if (propertyMetaInfo.isValid()) {
|
||||
return propertyNameListToStringList(propertyMetaInfo.signalNames());
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user