Build failed in Jenkins: royale-asjs_MXTests #685

See -- [...truncated 2.05 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #684

See -- [...truncated 2.03 MB...] [mxmlc] using source file:

Re: [royale-asjs] branch develop updated: core-HTMLElementWrapper: make getActualDispatcher_ function use positioner instead element

This caught my eye. Are we sure about this? If I create a Button by wrapping a in a I would think many events want to come directly from the button and not the div, but I can certainly understand the opposite could be true as well. What was the scenario here? -Alex On 4/17/19, 2:55 PM,

Build failed in Jenkins: royale-asjs_MXTests #683

See Changes: [carlosrovira] jewel-itemrenderer: fix listener to use positioner instead of element so [carlosrovira] core-HTMLElementWrapper: make getActualDispatcher_ function use

Re: Strand Initializer

When I wrote this part of the lifecycle, I couldn't find an efficient way to allow your pattern. So folks will have to instead use: We should add that to the doc somewhere. You are welcome to investigate finding an efficient way to allow your proposed pattern. HTH, -Alex

Build failed in Jenkins: royale-asjs_MXTests #682

See -- [...truncated 2.03 MB...] [mxmlc] using source file:

Strand Initializer

I’ve encountered a problem with MXML initialization of components that have a model defined in MXML beads. Suppose I have the following MXML: And the follow as3: class MyComp extends UIBase { public function set attName(value:*):void { model.attName =

Build failed in Jenkins: royale-asjs_MXTests #681

See Changes: [carlosrovira] jewel-itemrenders: refactor align property to a new interface and remove -- [...truncated 2.03 MB...]