Additionally I was going on Sunday change this area a bit.
DataProviderChangeNotifier - was suppose to stay without changes
DataProviderAddRemoveNotifier - I was going to add there updateEvent and
change its name to DataProviderItemsChangedNotifier
Create another bead DataProviderCollectionChan
Hi Peter,
I'm concerning about changes in DataProviderChangeNotifier.
Since it is no longer emits dataProviderChanged event it can break logic in
some apps which people are working on.
Some time ago when I've changed ArrayList and add itemAdded/removed etc.
events I've created separate bead [1]
Thanks. I'm having trouble understanding what code is changing the active
tab panel. I can see in the DOM, a tab with is-active set and a
corresponding tab panel has is-active set.
After I add a new tab, things look normal in the DOM. I can now select the
new tab and see that the new tab gets is-a
Peter,
If you stack on something let me know I will have some free cycles on
Sunday.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-feature-chart-work-status-tp61035p61041.html
Sent from the A
I've been working on this most of the day. I think there is something more
fundamental going on that this example has uncovered. There appear to be
duplicate events happening causing event handlers to be registered
multiple times. I'm not comfortable releasing this yet into develop.
I'll continue
I see that. I thought I fixed that. I'll look it while I'm building the
examples.
‹peter
On 4/6/17, 5:55 PM, "piotrz" wrote:
>Hi Peter,
>
>I just tried MDLExample and it look good, but MDLDynamicTabsExample has
>same
>problem. Something is going wrong when Tab is being added.
>
>Piotr
>
>
>
>---
