You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the large project, it's hard to maintain a consistent object name path. There are a lot of dynamic elements, and there is also potential for a lot of refactoring to be done on the Items hierarchy.
For this reason, it would be helpful to have a recursive approach. For example, we could add a parameter or create a separate method like "getStringPropertyRecursive" to work with QML items and their unique object names recursively.
The text was updated successfully, but these errors were encountered:
On the large project, it's hard to maintain a consistent object name path. There are a lot of dynamic elements, and there is also potential for a lot of refactoring to be done on the Items hierarchy.
For this reason, it would be helpful to have a recursive approach. For example, we could add a parameter or create a separate method like "getStringPropertyRecursive" to work with QML items and their unique object names recursively.
The text was updated successfully, but these errors were encountered: