08-17-2012 04:28 PM
I would need to see your code on the C++ side;
Also a few quick validations: Are you querying the correct qml document object in your C++ code to access the item? Are you specifying your objectName as astring in your QML file? Make sure you have the double quotations;
08-19-2012 03:28 AM - edited 08-19-2012 03:30 AM
I think the double quotes shouldnt be an issue when the objectName are coming from the C++
so, i can imagine the QML like
but the issue, if it happens to be - that would be ridiculous since as per the API, the UI changes as soon as the DataModel is changed, and to change the DataModel you would need the "indexPath"
Which i think could be the limitation being encountered here.
08-24-2012 11:24 AM
So, how are you faring?
As for the original question, it seems the answer is: the leaf-level object for communication is a QObject.
The quotes was for string literals in your QML:
Are there any additional unresolved questions?
08-31-2012 06:02 AM
NO in this case i'll go with 'soman' , the findChild would not return you the listItemComponent and the refrence would be 0x0.
The QML Structure:
I do get the list on the UI, now If you try
would print --- 0x0
Thus its unable to locate the exact list item/component.
09-04-2012 10:46 AM - edited 09-04-2012 10:58 AM
There seem to be 2 questions in this thread:
Q1. If I assign an ObjectName to something that is not a QObject, can I find it with findObject<QObject*>
Q2. If I give a list component an ObjectName, can I find the object with this name?
A2. Are you trying to find all objects of this component type? What are you trying to find, and what are you expecting to have returned? The component definition?
09-05-2012 04:40 AM
09-12-2012 04:36 PM
Is it possible you have the wrong type of object in the findChild<>?
You want the row with the data, or the underlying data? It may be you just want to query your data model?