On 22 May 2014 00:07, Alexander Ivash elder...@gmail.com wrote:
Use-case: Let's say I want to customize ComboBox's TextInput control which
is not exposed via ComboBox API.
There is some private API for that, but (unless something changed
recently) no official way to search by IDs. What I do in
* Thats exactly what I would also do if it would be my component, but
** unfortunately I don't have an access to TextInput { id: input } which is
** inside the ComboBox.
*
But you are able to assign the ID or is it built-in? I don't get the
problem, although I have not used the ComboBox, so
Thats exactly what I would also do if it would be my component, but
unfortunately I don't have an access to TextInput { id: input } which
is inside the ComboBox.
But you are able to assign the ID or is it built-in? I don't get the
problem,
although I have not used the ComboBox, so maybe
On 22 May 2014 12:01, Tony Rietwyk t...@rightsoft.com.au wrote:
Thats exactly what I would also do if it would be my component, but
unfortunately I don't have an access to TextInput { id: input } which
is inside the ComboBox.
But you are able to assign the ID or is it built-in? I don't
Alexander, do you have another use case in mind? It might clarify your
requirement. (I haven't played with QML yet but I thought all QObject
info is exposed to javascript and the components anyway - isn't that how
the linkage is achieved?)
The only use-case I have in mind is extending
