On 12/09/2013 10:00 AM, Alan Alpert wrote:
> Question does seem a bit clearer. But I think the answer is the same -
> ListView shouldn't be using context properties anymore. Well, it's
> worthwhile for the convenience here but maybe add an attached property
> reference as well for those cases needi
don't know the type.
Singletons don't suffer from that issue and also give the programmer full
control over the name spacing.
Simon
Fra: Alan Alpert
Sendt: 09:01 mandag 9. desember 2013
Til: Alberto Mardegan
Kopi: development@qt-project.org
Emne: Re: [Development] Namespacing QML context
On Sun, Dec 8, 2013 at 11:28 PM, Alberto Mardegan
wrote:
> On 12/09/2013 12:54 AM, Alan Alpert wrote:
>> On Sun, Dec 8, 2013 at 5:38 AM, Alberto Mardegan
>> wrote:
> [...]
>> What do you mean "current context"? The problem you seem to be hitting
>> is that there is another symbol in the current c
On 12/09/2013 12:54 AM, Alan Alpert wrote:
> On Sun, Dec 8, 2013 at 5:38 AM, Alberto Mardegan
> wrote:
[...]
> What do you mean "current context"? The problem you seem to be hitting
> is that there is another symbol in the current context that you want
> to avoid, so that it finds a symbol higher
On Sun, Dec 8, 2013 at 5:38 AM, Alberto Mardegan
wrote:
> Hi all!
> One of the issues that has most bothered me when developing in QML is
> dealing with the same variable name in item properties and context
> properties. For example:
>
> // "model" is a context property
> Loader {
> property
Hi all!
One of the issues that has most bothered me when developing in QML is
dealing with the same variable name in item properties and context
properties. For example:
// "model" is a context property
Loader {
property variant model: model
sourceComponent: someComponent
}
The code abo
