We may still need that somewhere. You may need to set the dataProvider to
null in order to allow for garbage collection. But yes, in general, we
want to avoid defensive code.
-Alex
On 7/10/17, 8:17 AM, "piotrz" wrote:
>I think we should raise jira for DropDownList improvement. Once it will be
I think we should raise jira for DropDownList improvement. Once it will be
done we won't need
if(!value)return; :)
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-DropDow
I agree with Piotr about moving the removal of the elements to the view.
But really, the binding subsystem should have caught this error. That's
part of the "Payment" for using binding.
My 2 cents,
-Alex
On 7/9/17, 11:50 AM, "piotrz" wrote:
>I think this Option generation shouldn't be really
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-DropDownList-dataProvider-tp62984p62996.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
dual, cause this model was moved from HTML module to
>> Basic during dual changes.
>>
>> Piotr
>>
>>
>>
>> -
>> Apache Flex PMC
>> piotrzarzyck...@gmail.com
>> --
>> View this message in context:
>> http://apache-flex-devel
> View this message in context:
> http://apache-flex-development.247.n4.nabble.com/FlexJS-DropDownList-dataProvider-tp62984p62993.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
ge in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-DropDownList-dataProvider-tp62984p62993.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
gt;
>
> -
> Apache Flex PMC
> piotrzarzyck...@gmail.com
> --
> View this message in context:
> http://apache-flex-development.247.n4.nabble.com/FlexJS-DropDownList-dataProvider-tp62984p62991.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
.nabble.com/FlexJS-DropDownList-dataProvider-tp62984p62991.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
lexJS-DropDownList-dataProvider-tp62984p62990.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
you provide small example ? I would like to make sure myself
>> that is a bug.
>>
>> Thanks,
>> Piotr
>>
>>
>>
>> -
>> Apache Flex PMC
>> piotrzarzyck...@gmail.com
>> --
>> View this message in context:
>> htt
.@gmail.com
> --
> View this message in context:
> http://apache-flex-development.247.n4.nabble.com/FlexJS-DropDownList-dataProvider-tp62984p62986.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
Actually could you provide small example ? I would like to make sure myself
that is a bug.
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-DropDownList-dataProvider-tp62984p62986.html
Hi Harbs,
I think it's a bug. I'm wondering whether MDL DropDownList react same.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-DropDownList-dataProvider-tp62984p62985.html
Sen
If you set the dataProvider of a DropDownList using binding and the Bindable
value is not initialized when it’s declared, it causes a runtime error.
I’m trying to decide whether this is a bug, or it’s a cost of PAYG (where in
the basic implementation you are rrequired to initialize the value). I
15 matches
Mail list logo
