jwolib – new release 2008.12.15
5 Comments so far
Leave a comment
Monday, December 15, 2008, 5:25 am
Filed under: actionScript, client side, components, development, flash, flex, jwo_lib, mxml
Filed under: actionScript, client side, components, development, flash, flex, jwo_lib, mxml
A user of the lib brought to my attention a major flaw in my default styling setup. This new release address the default styling as well as a few things regarding the TileCanvas’s itemRenderer (IFactory) generator class (now can use UIComponent, should implement IDataRenderer for best use).
jwolib 2008.12.15 (includes src, asdocs & SWC) – link
5 Comments so far
Leave a comment
Leave a comment
Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <pre> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
With the TileCanvas, If I set the datasource though MXML, nothing renders
It only seems to work if setting the dataProvider in ActionScript as your example shows.
Comment by Devin Tuesday, December 16, 2008 @ 4:00 amare you saying something like
…..
If so are you using the array tag in it as well? I think the data provider property will only accept collection type classes and should be grouped with a tag of that nature.
Comment by jwopitz Tuesday, December 16, 2008 @ 7:21 pmfor soem reason it didn’t display the xml:
TileCanvas
Comment by jwopitz Tuesday, December 16, 2008 @ 7:52 pmdataProvider
Array
item0
item1
item2
/Array
/dataProvider
/TileCanvas
Yes, that’s exactly what I’m saying. I was building a prototype and attempting to just quickly incorporate the TileCanvas using mock data exactly as you shown in the above comment. The tiles wouldn’t render, but I could still drag around some invisible objects. After populating the dp with actionscript like your example, it worked fine
Comment by Devin Tuesday, December 23, 2008 @ 5:59 pmOk I tracked this problem down. The fix is quite extensive and will be incorporated into a bigger refactoring of the component. I am not sure if you are looking to wait a while or not, but if not, the problem is basically that when you declare the dataprovider via MXML, it is trying to render the item renderers rather than waiting for the invalidation process to take place.
Comment by jwopitz Tuesday, December 23, 2008 @ 11:43 pm