Build failed in Jenkins: royale-asjs_MXTests #685

2019-04-17 Thread Apache Royale CI Server
See 


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

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 


Build failed in Jenkins: royale-asjs_MXTests #684

2019-04-17 Thread Apache Royale CI Server
See 


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

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 


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

2019-04-17 Thread Alex Harui
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, "carlosrov...@apache.org"  wrote:

This is an automated email from the ASF dual-hosted git repository.

carlosrovira pushed a commit to branch develop
in repository 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-asjs.git&data=02%7C01%7Caharui%40adobe.com%7C3c916dc5dfa2462e3c7108d6c37f5a86%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636911349076776345&sdata=k08fa1pwB9jQ7jwx1z0190OBt5CVnb6yHchQ73oA%2Fz0%3D&reserved=0


The following commit(s) were added to refs/heads/develop by this push:
 new e458f7c  core-HTMLElementWrapper: make getActualDispatcher_ 
function use positioner instead element
e458f7c is described below

commit e458f7c083cff64032d6081b4676454af46b5457
Author: Carlos Rovira 
AuthorDate: Wed Apr 17 23:54:55 2019 +0200

core-HTMLElementWrapper: make getActualDispatcher_ function use 
positioner instead element
---
 .../Core/src/main/royale/org/apache/royale/core/HTMLElementWrapper.as   | 
2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/HTMLElementWrapper.as
 
b/frameworks/projects/Core/src/main/royale/org/apache/royale/core/HTMLElementWrapper.as
index 4ebff5a..54a2d6c 100644
--- 
a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/HTMLElementWrapper.as
+++ 
b/frameworks/projects/Core/src/main/royale/org/apache/royale/core/HTMLElementWrapper.as
@@ -261,7 +261,7 @@ package org.apache.royale.core
 var source:Object = this;
 if (ElementEvents.elementEvents[type]) {
 // mouse and keyboard events also dispatch off the element.
-source = this.element;
+source = this.positioner;
 }
 return source;
 }





Build failed in Jenkins: royale-asjs_MXTests #683

2019-04-17 Thread Apache Royale CI Server
See 


Changes:

[carlosrovira] jewel-itemrenderer: fix listener to use positioner instead of 
element so

[carlosrovira] core-HTMLElementWrapper: make getActualDispatcher_ function use

[carlosrovira] jewel-tabbar: more changes to improve visuals in tabbar, as well 
mouse

[carlosrovira] update all jewel themes

[carlosrovira] Revert "core-HTMLElementWrapper: make getActualDispatcher_ 
function use

--
[...truncated 2.11 MB...]
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/MetaDataDefinition.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/ISpinnerView.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/SpinnerView.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IViewportModel.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/WrappedHTMLElement.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/spark/layouts/supportClasses/DropLocation.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/layout/LayoutData.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/collections/errors/CursorError.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/TextLineMetrics.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/styles/CSSStyleDeclaration.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/utils/FocusEventConverter.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/MethodDefinition.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/display/Graphics.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/ScrollControlBase.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/listClasses/ListBase.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IDataProviderVirtualItemRendererMapper.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/WatcherBase.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IImage.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/BrowserEvent.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/PanelModel.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/containers/beads/models/PanelModel.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IPopUp.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/halo/scripts/ButtonTestScript.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/spark/scripts/ButtonTestScript.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/ComboBase.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/DateField.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/RoyaleContext.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/ContainerBaseStrandChildren.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/BinaryData.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/UIUtils.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/controllers/ListSingleSelectionMouseController.js
[mxmlc] 
c:/jenkins/workspace/r

Re: Strand Initializer

2019-04-17 Thread Alex Harui
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

On 4/17/19, 6:14 AM, "Yishay Weiss"  wrote:

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 = value;
}
}

model will be initialized before CompModel is added to beads so CompModel 
is never added to MyComp.

Is this a bug? Is specifying a model in  bad practice?





Build failed in Jenkins: royale-asjs_MXTests #682

2019-04-17 Thread Apache Royale CI Server
See 


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

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 


Strand Initializer

2019-04-17 Thread Yishay Weiss
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 = value;
}
}

model will be initialized before CompModel is added to beads so CompModel is 
never added to MyComp.

Is this a bug? Is specifying a model in  bad practice?



Build failed in Jenkins: royale-asjs_MXTests #681

2019-04-17 Thread Apache Royale CI Server
See 


Changes:

[carlosrovira] jewel-itemrenders: refactor align property to a new interface 
and remove

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

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source