Thank you for your patience on this. I did run maven as well on my
directories and got a clean run.
On 4/10/17, 4:29 PM, "Christofer Dutz" wrote:
>+1 for merging as you say you tested FlexJSStore and it¹s working, we
>might get develop working again, which is a rather desirable thing ;-)
>
>Chri
+1 for merging as you say you tested FlexJSStore and it’s working, we might get
develop working again, which is a rather desirable thing ;-)
Chris
Am 10.04.17, 20:40 schrieb "Peter Ent" :
I now have the feature/chart-work branch in good shape: the frameworks
projects build and so do al
I now have the feature/chart-work branch in good shape: the frameworks
projects build and so do all of the examples; both ANT and maven builds
ran. I'm much, much more confident in the changes and stability of this
feature branch than I was last week.
I ran the following examples successfully: Cha
I know have MDLExample working.
I think I did this unwittingly: The MaterialDesignLite project's
default.css has the IDateProviderItemRendererMapper for the Tabs and
TabBar components specified as TabsItemRendererFactoryForArrayListData.
But the dataProvider being supplied to the tab components we
I will look into it and let you know. I changed the life cycle for lists
just a little. I found that the item renderers were being created more
than once (sometimes) and the layouts were being run several times
(sometimes) so I tracked down redundant event dispatches and eliminated
them. Then I wen
Ahh I forgot to mention that you can see issue when you look into MDLExample.
Main TabBar do not display Tabs.
Basically in TabBarView itemsCreated method has not been called.
If you lost in there I will put some basic example.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View th
Hi Peter,
After couple of hours of investigation I have found the reason and fixed
bug. You can check it.
But still something is wrong in case when TabBar is using
TabsItemRendererFactoryForArrayData. If you could take a look that would be
great!
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzy
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
>
>
>
>---
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
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS
Hi,
Yesterday I intended to merge the feature/chart_work branch into develop. After
I ran some more tests with more complex container structures I found a problem
with one of the layouts. I finally worked it out, so now I'm running through
all of the examples to make sure they compile so the bu
13 matches
Mail list logo