On 12/15/16, 4:04 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
wrote:
>Hi,
>
>justo reading the problem, I think things for our users (devs) should be
>more easy and don't expect they know he must remove something for two
>places instead of one.
>Could we have the beads storage unif
Hi,
justo reading the problem, I think things for our users (devs) should be
more easy and don't expect they know he must remove something for two
places instead of one.
Could we have the beads storage unified? if not I think it could be very
hard to deal with
2016-12-15 6:08 GMT+01:00 Alex Harui
On 12/14/16, 8:59 PM, "Josh Tynjala" wrote:
>Would it keep something in memory that should be garbage collected,
>though?
Yes, sure. If you remove a bead you declared in MXML you should search
that array and remove it. We could write a utility function that does
that if folks do it often.
I
Would it keep something in memory that should be garbage collected, though?
- Josh
On Dec 14, 2016 8:43 PM, "Alex Harui" wrote:
>
>
> On 12/14/16, 1:30 PM, "piotrz" wrote:
>
> >Hi All,
> >
> >While I was moving forward with implementation of MdlColor bead I have
> >found
> >that UIBase class c
On 12/14/16, 1:30 PM, "piotrz" wrote:
>Hi All,
>
>While I was moving forward with implementation of MdlColor bead I have
>found
>that UIBase class could have a bug on JS sight.
>
>When we want to remove bead method responsible for that is removing bead
>from:
>
>COMPILE::SWF
>private var _beads
beads:Array;
Is it a bug that removeBead do not actually remove it from beads Array ?
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Removing-bead-tp57268.html
Sent from the Apache Flex
