date:20130619

Cool, we had a clean run!!!

Let the games begin ;-)

EdB



On Wed, Jun 19, 2013 at 11:01 AM,  flex.muste...@gmail.com wrote:
 See http://localhost:8080/job/flex-sdk_mustella/177/changes




-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Jenkins build is back to normal : flex-sdk_mustella #177

Hi,

 Cool, we had a clean run!!!

What version of FP was being used? (Windows and 11.1)

And you'll probably hate me for bringing this up but did we run the mobile or 
AIR tests?

Thanks,
Justin

Re: Jenkins build is back to normal : flex-sdk_mustella #177

11.1, indeed.

And I guess not on the AIR and mobile tests... what ant
targets/switches make that happen?

EdB



On Wed, Jun 19, 2013 at 11:41 AM, Justin Mclean jmcl...@apache.org wrote:
 Hi,

 Cool, we had a clean run!!!

 What version of FP was being used? (Windows and 11.1)

 And you'll probably hate me for bringing this up but did we run the mobile or 
 AIR tests?

 Thanks,
 Justin



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

[jira] [Commented] (FLEX-29002) RunTime Error #1009 at mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying more than one modal popup via PopUpManager on top of each other. On Wi

[
https://issues.apache.org/jira/browse/FLEX-29002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687823#comment-13687823
]

Justin Mclean commented on FLEX-29002:
--

Unable to reproduce on OSX. What I don't understand is why this check would be
failing on Windows.

private function
removeModalPopUpAccessibility(popUp:DisplayObject):Boolean
{
if (Capabilities.hasAccessibility Accessibility.active)
{
...
}
}

Any change you could trace out those 2 values.

RunTime Error #1009 at
mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying
more than one modal popup via PopUpManager on top of each other. On Windows 7
running on some PCs
---

Key: FLEX-29002
URL: https://issues.apache.org/jira/browse/FLEX-29002
Project: Apache Flex
Issue Type: Bug
Components: PopUp Manager
Affects Versions: Adobe Flex SDK Previous
Environment: Affected OS(s): Windows
Affected OS(s): Windows 7
Language Found: English
Reporter: Adobe JIRA
Fix For: Adobe Flex SDK Next, Apache Flex 4.10.0

Attachments: ScreenReaderOnAccessibleOffTest.zip

Steps to reproduce:
1. in the AIR application, create modal popup via popupmanager - ok.
2. on the popup, create another modal popup via popupmanager (so we have two
modal popups one on top of the other) - RT error #1009.
3. close top popup, due to RT error #1009 modal shade stays on stage and
keeps blocking the application.

Actual Results:
Popupmanager closes modal titlewindow, but the modal shade stays on display
due to RunTime error #1009 and so application becomes non-operable.

Expected Results:
Popupmanager should close the modal titlewindow along with the modal shade
as it does if only one modal popup was invoked.

Workaround (if any):
On Windows7 Control Panel, disable some stuff in control panel (Attachments)
and reboot OS. Trully, this works.

Note:
This happens only on Windows 7 OS running on some All-In-One PCs (eg.: MSI
AE2050). Bug is connected with the accessibility OS provides, so we can fix
the issue by configuring some OS parameters.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (FLEX-33592) mx.controls.MenuBar#getMenuAt RangeError

Philip Mair created FLEX-33592:
--

 Summary: mx.controls.MenuBar#getMenuAt RangeError
 Key: FLEX-33592
 URL: https://issues.apache.org/jira/browse/FLEX-33592
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: Menu Bar
Affects Versions: Apache Flex 4.9.0
Reporter: Philip Mair


When changing MenuBar dataProvider within click on MenuBar-Item causes a 
RangeError in getMenuAt if the index was greater then new amount of MenuBar 
Items.

I solved this with following workaround:

public override function getMenuAt(index:int):Menu
{
var menu:Menu = null;

try
{
menu = super.getMenuAt(index);
}
catch(e: Error)
{

}
if(menu == null) //return a fake menu to avoid 
TypeError's
return new Menu();
else
return menu;
}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (FLEX-33593) mx.controls.MenuBar#mouseOutHandler TypeError

Philip Mair created FLEX-33593:
--

 Summary: mx.controls.MenuBar#mouseOutHandler TypeError
 Key: FLEX-33593
 URL: https://issues.apache.org/jira/browse/FLEX-33593
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: Menu Bar
Affects Versions: Apache Flex 4.9.0
Reporter: Philip Mair


When changing MenuBar dataProvider within click on Menu sometimes causes a 
TypeError in mouseOutHandler.

I solved this with following workaround:

public override function 
addChild(child:DisplayObject):DisplayObject
{
if( child is IMenuBarItemRenderer )
{
var item: IMenuBarItemRenderer = 
IMenuBarItemRenderer( child );


item.addEventListener( MouseEvent.MOUSE_OUT, 
patchedMouseOutHandler, false, int.MAX_VALUE );
}

return super.addChild( child );
}

private function patchedMouseOutHandler( event: MouseEvent ) : 
void
{
//stop the event to avoid npe
event.stopImmediatePropagation();
event.stopPropagation();

var item:IMenuBarItemRenderer = 
IMenuBarItemRenderer(event.target);
var index:int = item.menuBarItemIndex;
var m:Menu = getMenuAt(index);

if (item.enabled  selectedIndex != index)
{
if( menuBarItems.indexOf( item ) = 0 )
menuBarItems[index].menuBarItemState = 
itemUpSkin;
}
// Fire the appropriate rollout event
if (item.data  
(m.dataDescriptor.getType(item.data) != 
separator))
{
var menuEvent:MenuEvent = new 
MenuEvent(MenuEvent.ITEM_ROLL_OUT);
menuEvent.index = index;
menuEvent.menuBar = this;
menuEvent.label = itemToLabel(item.data);
menuEvent.item = item.data;
menuEvent.itemRenderer = item;
dispatchEvent(menuEvent);
}
}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FLEX-29002) RunTime Error #1009 at mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying more than one modal popup via PopUpManager on top of each other. On Wi

[
https://issues.apache.org/jira/browse/FLEX-29002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687839#comment-13687839
]

Justin Mclean commented on FLEX-29002:
--

Can you run this code under the same situation and tell me if RTEs.

if (Capabilities.hasAccessibility Accessibility.active) {
Accessibility.updateProperties();
}

If so then this is a Flash player issue and needs to be raised at
https://bugbase.adobe.com.

I'll see if I can add a work around into the SDK.

RunTime Error #1009 at
mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying
more than one modal popup via PopUpManager on top of each other. On Windows 7
running on some PCs
---

Attachments: ScreenReaderOnAccessibleOffTest.zip

Actual Results:
Popupmanager closes modal titlewindow, but the modal shade stays on display
due to RunTime error #1009 and so application becomes non-operable.

Expected Results:
Popupmanager should close the modal titlewindow along with the modal shade
as it does if only one modal popup was invoked.

Workaround (if any):
On Windows7 Control Panel, disable some stuff in control panel (Attachments)
and reboot OS. Trully, this works.

[jira] [Commented] (FLEX-29002) RunTime Error #1009 at mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying more than one modal popup via PopUpManager on top of each other. On Wi

[
https://issues.apache.org/jira/browse/FLEX-29002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687854#comment-13687854
]

Justin Mclean commented on FLEX-29002:
--

Workaround added to develop branch of SDK and tested via debugger. Can someone
test on windows for me?

RunTime Error #1009 at
mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying
more than one modal popup via PopUpManager on top of each other. On Windows 7
running on some PCs
---

Attachments: ScreenReaderOnAccessibleOffTest.zip

Actual Results:
Popupmanager closes modal titlewindow, but the modal shade stays on display
due to RunTime error #1009 and so application becomes non-operable.

Expected Results:
Popupmanager should close the modal titlewindow along with the modal shade
as it does if only one modal popup was invoked.

Workaround (if any):
On Windows7 Control Panel, disable some stuff in control panel (Attachments)
and reboot OS. Trully, this works.

[jira] [Commented] (FLEX-33592) mx.controls.MenuBar#getMenuAt RangeError


[ 
https://issues.apache.org/jira/browse/FLEX-33592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687863#comment-13687863
 ] 

Justin Mclean commented on FLEX-33592:
--

Can you provide same sample code that shows the issue. Perhaps a better work 
around is to stop the propagation of the click event in the click handler after 
changing the data provider?

 mx.controls.MenuBar#getMenuAt RangeError
 

 Key: FLEX-33592
 URL: https://issues.apache.org/jira/browse/FLEX-33592
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: Menu Bar
Affects Versions: Apache Flex 4.9.0
Reporter: Philip Mair
   Original Estimate: 2h
  Remaining Estimate: 2h

 When changing MenuBar dataProvider within click on MenuBar-Item causes a 
 RangeError in getMenuAt if the index was greater then new amount of MenuBar 
 Items.
 I solved this with following workaround:
   public override function getMenuAt(index:int):Menu
   {
   var menu:Menu = null;
   
   try
   {
   menu = super.getMenuAt(index);
   }
   catch(e: Error)
   {
   
   }
   if(menu == null) //return a fake menu to avoid 
 TypeError's
   return new Menu();
   else
   return menu;
   }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FLEX-33592) mx.controls.MenuBar#getMenuAt RangeError


[ 
https://issues.apache.org/jira/browse/FLEX-33592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687916#comment-13687916
 ] 

Philip Mair commented on FLEX-33592:


Here is a sample, every click on item  1 will force the error

{code:xml}
?xml version=1.0 encoding=utf-8?
s:Application xmlns:fx=http://ns.adobe.com/mxml/2009; 
   xmlns:s=library://ns.adobe.com/flex/spark 
   xmlns:mx=library://ns.adobe.com/flex/mx
   minWidth=955 
   minHeight=600
   
   
fx:Script
![CDATA[
import mx.collections.ArrayCollection;
import mx.controls.menuClasses.MenuBarItem;

[Bindable]
private var dataProvider: ArrayCollection = 
buildDummyData( 5 );


protected function 
menubar1_clickHandler(event:MouseEvent):void
{
if(event.target is MenuBarItem)
{
var item:MenuBarItem = event.target as 
MenuBarItem;

trace(item clicked);

dataProvider = buildDummyData(1);
}
}

protected function buildDummyData( c: int 
):ArrayCollection
{
var ac: ArrayCollection = new ArrayCollection();

for( var i: int = 0; ic; i++ )
{
ac.addItem( { 'label': 'ITEM_'+i } );
}

return ac;
}

]]
/fx:Script
fx:Declarations

/fx:Declarations
mx:VBox
mx:MenuBar dataProvider={dataProvider} 
click=menubar1_clickHandler(event) /
s:Button label=reset click=dataProvider = 
buildDummyData(5) /
/mx:VBox

/s:Application
{code}

{{
TypeError: Error #1009: Cannot access a property or method of a null object 
reference.
at 
mx.controls::MenuBar/getMenuAt()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/mx/src/mx/controls/MenuBar.as:1751]
at 
mx.controls::MenuBar/mouseOutHandler()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/mx/src/mx/controls/MenuBar.as:2091]
}}

 mx.controls.MenuBar#getMenuAt RangeError
 

 Key: FLEX-33592
 URL: https://issues.apache.org/jira/browse/FLEX-33592
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: Menu Bar
Affects Versions: Apache Flex 4.9.0
Reporter: Philip Mair
   Original Estimate: 2h
  Remaining Estimate: 2h

 When changing MenuBar dataProvider within click on MenuBar-Item causes a 
 RangeError in getMenuAt if the index was greater then new amount of MenuBar 
 Items.
 I solved this with following workaround:
   public override function getMenuAt(index:int):Menu
   {
   var menu:Menu = null;
   
   try
   {
   menu = super.getMenuAt(index);
   }
   catch(e: Error)
   {
   
   }
   if(menu == null) //return a fake menu to avoid 
 TypeError's
   return new Menu();
   else
   return menu;
   }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FLEX-33592) mx.controls.MenuBar#getMenuAt RangeError


 [ 
https://issues.apache.org/jira/browse/FLEX-33592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philip Mair updated FLEX-33592:
---

Description: 
When changing MenuBar dataProvider within click on MenuBar-Item causes a 
RangeError in getMenuAt if the index was greater then new amount of MenuBar 
Items.

I solved this with following workaround:

public override function getMenuAt(index:int):Menu
{
var menu:Menu = null;

try
{
menu = super.getMenuAt(index);
}
catch(e: Error)
{

}
if(menu == null) //return a fake menu to avoid 
TypeError's
return new Menu();
else
return menu;
}

  was:
When changing MenuBar dataProvider within click on MenuBar-Item causes a 
RangeError in getMenuAt if the index was greater then new amount of MenuBar 
Items.

I solved this with following workaround:
{code:xml}
public override function getMenuAt(index:int):Menu
{
var menu:Menu = null;

try
{
menu = super.getMenuAt(index);
}
catch(e: Error)
{

}
if(menu == null) //return a fake menu to avoid 
TypeError's
return new Menu();
else
return menu;
}
{code}


 mx.controls.MenuBar#getMenuAt RangeError
 

 Key: FLEX-33592
 URL: https://issues.apache.org/jira/browse/FLEX-33592
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: Menu Bar
Affects Versions: Apache Flex 4.9.0
Reporter: Philip Mair
   Original Estimate: 2h
  Remaining Estimate: 2h

 When changing MenuBar dataProvider within click on MenuBar-Item causes a 
 RangeError in getMenuAt if the index was greater then new amount of MenuBar 
 Items.
 I solved this with following workaround:
   public override function getMenuAt(index:int):Menu
   {
   var menu:Menu = null;
   
   try
   {
   menu = super.getMenuAt(index);
   }
   catch(e: Error)
   {
   
   }
   if(menu == null) //return a fake menu to avoid 
 TypeError's
   return new Menu();
   else
   return menu;
   }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FLEX-33592) mx.controls.MenuBar#getMenuAt RangeError


 [ 
https://issues.apache.org/jira/browse/FLEX-33592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philip Mair updated FLEX-33592:
---

Description: 
When changing MenuBar dataProvider within click on MenuBar-Item causes a 
RangeError in getMenuAt if the index was greater then new amount of MenuBar 
Items.

I solved this with following workaround:
{code:xml}
public override function getMenuAt(index:int):Menu
{
var menu:Menu = null;

try
{
menu = super.getMenuAt(index);
}
catch(e: Error)
{

}
if(menu == null) //return a fake menu to avoid 
TypeError's
return new Menu();
else
return menu;
}
{code}

  was:
When changing MenuBar dataProvider within click on MenuBar-Item causes a 
RangeError in getMenuAt if the index was greater then new amount of MenuBar 
Items.

I solved this with following workaround:

public override function getMenuAt(index:int):Menu
{
var menu:Menu = null;

try
{
menu = super.getMenuAt(index);
}
catch(e: Error)
{

}
if(menu == null) //return a fake menu to avoid 
TypeError's
return new Menu();
else
return menu;
}


 mx.controls.MenuBar#getMenuAt RangeError
 

 Key: FLEX-33592
 URL: https://issues.apache.org/jira/browse/FLEX-33592
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: Menu Bar
Affects Versions: Apache Flex 4.9.0
Reporter: Philip Mair
   Original Estimate: 2h
  Remaining Estimate: 2h

 When changing MenuBar dataProvider within click on MenuBar-Item causes a 
 RangeError in getMenuAt if the index was greater then new amount of MenuBar 
 Items.
 I solved this with following workaround:
 {code:xml}
   public override function getMenuAt(index:int):Menu
   {
   var menu:Menu = null;
   
   try
   {
   menu = super.getMenuAt(index);
   }
   catch(e: Error)
   {
   
   }
   if(menu == null) //return a fake menu to avoid 
 TypeError's
   return new Menu();
   else
   return menu;
   }
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FLEX-33592) mx.controls.MenuBar#getMenuAt TypeError


 [ 
https://issues.apache.org/jira/browse/FLEX-33592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philip Mair updated FLEX-33592:
---

Summary: mx.controls.MenuBar#getMenuAt TypeError  (was: 
mx.controls.MenuBar#getMenuAt RangeError)

 mx.controls.MenuBar#getMenuAt TypeError
 ---

 Key: FLEX-33592
 URL: https://issues.apache.org/jira/browse/FLEX-33592
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: Menu Bar
Affects Versions: Apache Flex 4.9.0
Reporter: Philip Mair
   Original Estimate: 2h
  Remaining Estimate: 2h

 When changing MenuBar dataProvider within click on MenuBar-Item causes a 
 RangeError in getMenuAt if the index was greater then new amount of MenuBar 
 Items.
 I solved this with following workaround:
   public override function getMenuAt(index:int):Menu
   {
   var menu:Menu = null;
   
   try
   {
   menu = super.getMenuAt(index);
   }
   catch(e: Error)
   {
   
   }
   if(menu == null) //return a fake menu to avoid 
 TypeError's
   return new Menu();
   else
   return menu;
   }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Comment Edited] (FLEX-33592) mx.controls.MenuBar#getMenuAt RangeError


[ 
https://issues.apache.org/jira/browse/FLEX-33592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687916#comment-13687916
 ] 

Philip Mair edited comment on FLEX-33592 at 6/19/13 12:20 PM:
--

Here is a sample, every click on item  1 will force the error


?xml version=1.0 encoding=utf-8?
s:Application xmlns:fx=http://ns.adobe.com/mxml/2009; 
   xmlns:s=library://ns.adobe.com/flex/spark 
   xmlns:mx=library://ns.adobe.com/flex/mx
   minWidth=955 
   minHeight=600
   
   
fx:Script
![CDATA[
import mx.collections.ArrayCollection;
import mx.controls.menuClasses.MenuBarItem;

[Bindable]
private var dataProvider: ArrayCollection = 
buildDummyData( 5 );


protected function 
menubar1_clickHandler(event:MouseEvent):void
{
if(event.target is MenuBarItem)
{
var item:MenuBarItem = event.target as 
MenuBarItem;

trace(item clicked);

dataProvider = buildDummyData(1);
}
}

protected function buildDummyData( c: int 
):ArrayCollection
{
var ac: ArrayCollection = new ArrayCollection();

for( var i: int = 0; ic; i++ )
{
ac.addItem( { 'label': 'ITEM_'+i } );
}

return ac;
}

]]
/fx:Script
fx:Declarations

/fx:Declarations
mx:VBox
mx:MenuBar dataProvider={dataProvider} 
click=menubar1_clickHandler(event) /
s:Button label=reset click=dataProvider = 
buildDummyData(5) /
/mx:VBox

/s:Application



TypeError: Error #1009: Cannot access a property or method of a null object 
reference.
at 
mx.controls::MenuBar/getMenuAt()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/mx/src/mx/controls/MenuBar.as:1751]
at 
mx.controls::MenuBar/mouseOutHandler()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/mx/src/mx/controls/MenuBar.as:2091]


  was (Author: philipmair):
Here is a sample, every click on item  1 will force the error

{code:xml}
?xml version=1.0 encoding=utf-8?
s:Application xmlns:fx=http://ns.adobe.com/mxml/2009; 
   xmlns:s=library://ns.adobe.com/flex/spark 
   xmlns:mx=library://ns.adobe.com/flex/mx
   minWidth=955 
   minHeight=600
   
   
fx:Script
![CDATA[
import mx.collections.ArrayCollection;
import mx.controls.menuClasses.MenuBarItem;

[Bindable]
private var dataProvider: ArrayCollection = 
buildDummyData( 5 );


protected function 
menubar1_clickHandler(event:MouseEvent):void
{
if(event.target is MenuBarItem)
{
var item:MenuBarItem = event.target as 
MenuBarItem;

trace(item clicked);

dataProvider = buildDummyData(1);
}
}

protected function buildDummyData( c: int 
):ArrayCollection
{
var ac: ArrayCollection = new ArrayCollection();

for( var i: int = 0; ic; i++ )
{
ac.addItem( { 'label': 'ITEM_'+i } );
}

return ac;

[jira] [Updated] (FLEX-33592) mx.controls.MenuBar#getMenuAt RangeError


 [ 
https://issues.apache.org/jira/browse/FLEX-33592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philip Mair updated FLEX-33592:
---

Description: 
When changing MenuBar dataProvider within click on MenuBar-Item causes a 
RangeError in getMenuAt if the index was greater then new amount of MenuBar 
Items.

I solved this with following workaround:

public override function getMenuAt(index:int):Menu
{
var menu:Menu = null;

try
{
menu = super.getMenuAt(index);
}
catch(e: Error)
{

}
if(menu == null) //return a fake menu to avoid 
TypeError's
return new Menu();
else
return menu;
}


  was:
When changing MenuBar dataProvider within click on MenuBar-Item causes a 
RangeError in getMenuAt if the index was greater then new amount of MenuBar 
Items.

I solved this with following workaround:
{{
public override function getMenuAt(index:int):Menu
{
var menu:Menu = null;

try
{
menu = super.getMenuAt(index);
}
catch(e: Error)
{

}
if(menu == null) //return a fake menu to avoid 
TypeError's
return new Menu();
else
return menu;
}
}}


 mx.controls.MenuBar#getMenuAt RangeError
 

 Key: FLEX-33592
 URL: https://issues.apache.org/jira/browse/FLEX-33592
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: Menu Bar
Affects Versions: Apache Flex 4.9.0
Reporter: Philip Mair
   Original Estimate: 2h
  Remaining Estimate: 2h

 When changing MenuBar dataProvider within click on MenuBar-Item causes a 
 RangeError in getMenuAt if the index was greater then new amount of MenuBar 
 Items.
 I solved this with following workaround:
   public override function getMenuAt(index:int):Menu
   {
   var menu:Menu = null;
   
   try
   {
   menu = super.getMenuAt(index);
   }
   catch(e: Error)
   {
   
   }
   if(menu == null) //return a fake menu to avoid 
 TypeError's
   return new Menu();
   else
   return menu;
   }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FLEX-33593) mx.controls.MenuBar#mouseOutHandler TypeError


[ 
https://issues.apache.org/jira/browse/FLEX-33593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687928#comment-13687928
 ] 

Philip Mair commented on FLEX-33593:


On trying to provide a sample code i got an equal error in mouseOverHandler!

I think that all eventHandlers which are registered here:

MenuBar#insertMenuBarItem()

item.addEventListener(MouseEvent.MOUSE_OVER, mouseOverHandler);
item.addEventListener(MouseEvent.MOUSE_DOWN, mouseDownHandler);
item.addEventListener(MouseEvent.MOUSE_UP, mouseUpHandler);
item.addEventListener(MouseEvent.MOUSE_OUT, mouseOutHandler);

should be removed in removeMenuBarItemAt(), and removeAll()

 mx.controls.MenuBar#mouseOutHandler TypeError
 -

 Key: FLEX-33593
 URL: https://issues.apache.org/jira/browse/FLEX-33593
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: Menu Bar
Affects Versions: Apache Flex 4.9.0
Reporter: Philip Mair
   Original Estimate: 2h
  Remaining Estimate: 2h

 When changing MenuBar dataProvider within click on Menu sometimes causes a 
 TypeError in mouseOutHandler.
 I solved this with following workaround:
   public override function 
 addChild(child:DisplayObject):DisplayObject
   {
   if( child is IMenuBarItemRenderer )
   {
   var item: IMenuBarItemRenderer = 
 IMenuBarItemRenderer( child );
   
   
   item.addEventListener( MouseEvent.MOUSE_OUT, 
 patchedMouseOutHandler, false, int.MAX_VALUE );
   }
   
   return super.addChild( child );
   }
   
   private function patchedMouseOutHandler( event: MouseEvent ) : 
 void
   {
   //stop the event to avoid npe
   event.stopImmediatePropagation();
   event.stopPropagation();
   
   var item:IMenuBarItemRenderer = 
 IMenuBarItemRenderer(event.target);
   var index:int = item.menuBarItemIndex;
   var m:Menu = getMenuAt(index);
   
   if (item.enabled  selectedIndex != index)
   {
   if( menuBarItems.indexOf( item ) = 0 )
   menuBarItems[index].menuBarItemState = 
 itemUpSkin;
   }
   // Fire the appropriate rollout event
   if (item.data  
   (m.dataDescriptor.getType(item.data) != 
 separator))
   {
   var menuEvent:MenuEvent = new 
 MenuEvent(MenuEvent.ITEM_ROLL_OUT);
   menuEvent.index = index;
   menuEvent.menuBar = this;
   menuEvent.label = itemToLabel(item.data);
   menuEvent.item = item.data;
   menuEvent.itemRenderer = item;
   dispatchEvent(menuEvent);
   }
   }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: downloading nightly Apache Flex build from Jenkins

2013-06-19 Thread Frédéric THOMAS

What was wrong exactly ?

-Message d'origine- 
From: Nick Collins

Sent: Tuesday, June 18, 2013 11:43 PM
To: dev@flex.apache.org
Subject: Re: downloading nightly Apache Flex build from Jenkins

Yeah, I did that and deployed it to my local nexus repository, but have
been having trouble getting it to resolve from there rather than going to
sonatype and of course failing. Just haven't had the time to put into
troubleshooting it.

On Tue, Jun 18, 2013 at 11:21 AM, Frédéric THOMAS
webdoubl...@hotmail.comwrote:

Nick,

There is a https://repository.apache.org/ but we can't use it as some of
the artifacts used in a mavenized SDK have a license to validate before to
be able to download it.
So, at the moment, instead, use can mavenized yourself the SDK using the
Apache Flex SDK Mavenizer [1] and deploy it with the SDK Deployer to your
own repository.

-Fred

[1] 
http://flex.apache.org/**download-utilities.htmlhttp://flex.apache.org/download-utilities.html

-Message d'origine- From: Nick Collins
Sent: Tuesday, June 18, 2013 6:04 PM
To: dev@flex.apache.org
Cc: us...@flex.apache.org
Subject: Re: downloading nightly Apache Flex build from Jenkins

Soo where is nexus.apache.org for us to deploy our artifacts to? I
have
to think there is a way we can deploy our artifacts to a free-to-access 
but

semi-private nexus repository for Maven/Gradle use. Even if there was a
registration process to gain access to it where you then had to put a
generated auth key into your build.username.properties or something to 
that

effect.

On Tue, Jun 18, 2013 at 9:17 AM, OmPrakash Muppirala
bigosma...@gmail.comwrote:

 We have a new version of the Installer coming up soon that supports

nightly
builds.  I will be posting details about it soon.

Thanks,
Om
On Jun 18, 2013 7:00 AM, Maurice Amsellem maurice.amsel...@systar.com
wrote:

 Hi,

 I would like to download the latest nightly build of flex sdk (#100) 
from
 Jenkins

 I downloaded workspace all files in a zip file   from

https://builds.apache.org/job/**flex-sdk/ws/https://builds.apache.org/job/flex-sdk/ws/

 Is that the correct procedure ?

 Thanks

 Maurice

[jira] [Commented] (FLEX-29002) RunTime Error #1009 at mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying more than one modal popup via PopUpManager on top of each other. On Wi

2013-06-19 Thread Shigeru Nakagaki (JIRA)

[
https://issues.apache.org/jira/browse/FLEX-29002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688006#comment-13688006
]

Shigeru Nakagaki commented on FLEX-29002:
-

At the first, compiler.accessible option have to be false.
And a screen reader like Microsoft Narrator should be installed and enabled.
In this case, Capabilities.hasAccessibility and Accessibility.active are both
true.
compiler.accessible = false makes displayObject.accessibilityProperties null,
I guess.

PopUpManagerImpl/handleAccessibilityForNestedPopups() does not check
displayObject.accessibilityProperties is null or not.
So a RTE happens.

RunTime Error #1009 at
mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying
more than one modal popup via PopUpManager on top of each other. On Windows 7
running on some PCs
---

Attachments: ScreenReaderOnAccessibleOffTest.zip

Actual Results:
Popupmanager closes modal titlewindow, but the modal shade stays on display
due to RunTime error #1009 and so application becomes non-operable.

Expected Results:
Popupmanager should close the modal titlewindow along with the modal shade
as it does if only one modal popup was invoked.

Workaround (if any):
On Windows7 Control Panel, disable some stuff in control panel (Attachments)
and reboot OS. Trully, this works.

[jira] [Commented] (FLEX-29002) RunTime Error #1009 at mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying more than one modal popup via PopUpManager on top of each other. On Wi

[
https://issues.apache.org/jira/browse/FLEX-29002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688012#comment-13688012
]

Justin Mclean commented on FLEX-29002:
--

displayObject.accessibilityProperties was null and I corrected several
instances where that might create an RTE.
Accessibility.updateProperties() will also throw an exception in this case so
I've also added a try catch around it to ignore the exception.
Both of these fixes have been checked into the develop branch.

RunTime Error #1009 at
mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying
more than one modal popup via PopUpManager on top of each other. On Windows 7
running on some PCs
---

Attachments: ScreenReaderOnAccessibleOffTest.zip

Actual Results:
Popupmanager closes modal titlewindow, but the modal shade stays on display
due to RunTime error #1009 and so application becomes non-operable.

Expected Results:
Popupmanager should close the modal titlewindow along with the modal shade
as it does if only one modal popup was invoked.

Workaround (if any):
On Windows7 Control Panel, disable some stuff in control panel (Attachments)
and reboot OS. Trully, this works.

Re: Skinning FlexJS

2013-06-19 Thread Erick Ghaumez

hi,

yes Om i'm in !

I'll start with some skinning tests for the stockQuote sample.
I think I can send a first proposal next week.

Just to be sure : the goal is to create a default skin which you can use with 
SWF and html/js export ?
Does the skinning system for SWF Flex will be the same as today ( Skin class 
with MXMLG  FXG ) ?

Erick


Le 19 juin 2013 à 02:21, OmPrakash Muppirala bigosma...@gmail.com a écrit :

 
 What kind of beautification are you taking about?
 I'm don't think it looks as good as Spark or MX right now.  Colors,
 styles, spacing might make it look more like it is worth trying to use
 this stuff.
 
 Perhaps the designers in this list could help us design the next gen
 default look and feel for Flex?  Any takers?
 Thanks,
 Om
 
 
 Designers in the list,
 
 How about we try to put together a new visual look and feel for FlexJS?
 
 I am thinking that we can use the traditional approach of creating assets
 in AI or Fireworks and export them to formats we want.  This will also give
 me a chance to figure out the various approaches and tooling requirements.
 
 We have a lot of different options to do this, CSS3, FXG/MXML, SVG, etc.
 To get an idea of the first set of components we want skinned, here are
 the links to some samples Alex had put out a while ago [1,2]
 
 P.S.  Erick, you had pinged me on Twitter about wanting to help.  I hope
 you are in this list now :-)
 
 [1] http://people.apache.org/~aharui/FlexJS/
 [2] http://people.apache.org/~aharui/FlexJS/StatesTest/

Re: Jenkins build is back to normal : flex-sdk_mustella #177

2013-06-19 Thread Alex Harui

For AIR it should be ./mini_run.sh -apollo tests/apollo

For mobile you'll need to swap in a different local.properties before
running mini_run on the mobile directory.  See the wiki page for how to
set that up.

-Alex

On 6/19/13 2:48 AM, Erik de Bruin e...@ixsoftware.nl wrote:

11.1, indeed.

And I guess not on the AIR and mobile tests... what ant
targets/switches make that happen?

EdB



On Wed, Jun 19, 2013 at 11:41 AM, Justin Mclean jmcl...@apache.org
wrote:
 Hi,

 Cool, we had a clean run!!!

 What version of FP was being used? (Windows and 11.1)

 And you'll probably hate me for bringing this up but did we run the
mobile or AIR tests?

 Thanks,
 Justin



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

[jira] [Updated] (FLEX-33585) the dropDown of the spark combobox does not close regular when use alert to show the information of the selelcted item

2013-06-19 Thread Thom Wu (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLEX-33585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thom Wu updated FLEX-33585:
---

Summary: the dropDown of the spark combobox does not close regular when use 
alert to show the information of the selelcted item  (was: the dropDown of the 
spark combobox does not close regular when use alert to show the infomation of 
the selelcted item)

 the dropDown of the spark combobox does not close regular when use alert to 
 show the information of the selelcted item
 --

 Key: FLEX-33585
 URL: https://issues.apache.org/jira/browse/FLEX-33585
 Project: Apache Flex
  Issue Type: Bug
  Components: Spark: ComboBox
Affects Versions: Adobe Flex SDK 4.6 (Release)
 Environment: win7 and win xp
Reporter: Thom Wu
  Labels: combobox, dropdown
   Original Estimate: 504h
  Remaining Estimate: 504h

 the sample code:
 s:WindowedApplication xmlns:fx=http://ns.adobe.com/mxml/2009; 
   xmlns:s=library://ns.adobe.com/flex/spark 
   xmlns:mx=library://ns.adobe.com/flex/mx
   fx:Script
   ![CDATA[
   import mx.controls.Alert;
   import spark.events.IndexChangeEvent;
   
   protected function 
 myCombobox_changingHandler(event:IndexChangeEvent):void {
   Alert.show(myCombobox.selectedItem);
   }
   
   ]]
   /fx:Script
   
   s:ComboBox id=myCombobox 
 changing=myCombobox_changingHandler(event)
   s:ArrayList
   fx:StringUSA/fx:String
   fx:StringChina/fx:String
   fx:StringIt/fx:String
   /s:ArrayList
   /s:ComboBox
 /s:WindowedApplication
 Test steps:
 1.click the openButton to open the dropDown of the combobox
 2.select the first item the of the Drop-down list item,then alert display the 
 selected item
 3.expect the dropDown of the combobox close,but it does not
 4.click the ok button of the alert to close the alert
 5.click the second item of the Drop-down list item，then the dropDown 
 close??alert display the select item
 The same operation, the combobox are inconsistent performance

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Jenkins build is back to normal : flex-sdk_mustella #177

Can you give me an indication how long a run of each type takes?

EdB



On Wednesday, June 19, 2013, Alex Harui wrote:

 For AIR it should be ./mini_run.sh -apollo tests/apollo

 For mobile you'll need to swap in a different local.properties before
 running mini_run on the mobile directory.  See the wiki page for how to
 set that up.

 -Alex

 On 6/19/13 2:48 AM, Erik de Bruin e...@ixsoftware.nl javascript:;
 wrote:

 11.1, indeed.
 
 And I guess not on the AIR and mobile tests... what ant
 targets/switches make that happen?
 
 EdB
 
 
 
 On Wed, Jun 19, 2013 at 11:41 AM, Justin Mclean 
 jmcl...@apache.orgjavascript:;
 
 wrote:
  Hi,
 
  Cool, we had a clean run!!!
 
  What version of FP was being used? (Windows and 11.1)
 
  And you'll probably hate me for bringing this up but did we run the
 mobile or AIR tests?
 
  Thanks,
  Justin
 
 
 
 --
 Ix Multimedia Software
 
 Jan Luykenstraat 27
 3521 VB Utrecht
 
 T. 06-51952295
 I. www.ixsoftware.nl



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

[jira] [Commented] (FLEX-33592) mx.controls.MenuBar#getMenuAt TypeError


[ 
https://issues.apache.org/jira/browse/FLEX-33592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688042#comment-13688042
 ] 

Justin Mclean commented on FLEX-33592:
--

.event.stopImmediatePropagation() fails to fix issue will look into it. Can 
reproduce issue in develop branch.

 mx.controls.MenuBar#getMenuAt TypeError
 ---

 Key: FLEX-33592
 URL: https://issues.apache.org/jira/browse/FLEX-33592
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: Menu Bar
Affects Versions: Apache Flex 4.9.0
Reporter: Philip Mair
   Original Estimate: 2h
  Remaining Estimate: 2h

 When changing MenuBar dataProvider within click on MenuBar-Item causes a 
 RangeError in getMenuAt if the index was greater then new amount of MenuBar 
 Items.
 I solved this with following workaround:
   public override function getMenuAt(index:int):Menu
   {
   var menu:Menu = null;
   
   try
   {
   menu = super.getMenuAt(index);
   }
   catch(e: Error)
   {
   
   }
   if(menu == null) //return a fake menu to avoid 
 TypeError's
   return new Menu();
   else
   return menu;
   }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Apache Flex 4.10.0 release?

Hi,

Why aren't we talking about this anymore? We are at most 2 bug fixes
and one test (FLEX-33547) away from being zarro boogs. Mustella is
running cleanly on both Mac and Windows (Alex's machine and the VM)
and the Installer should be at or near a new release as well (Om?).

We should really start to get things together and work toward a
release sooner rather than later...

EdB



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Skinning FlexJS

If you guys need any help from the FalconJx compiler to get this
working, feel free to ping me and I'll see what I can do.

EdB



On Wed, Jun 19, 2013 at 4:09 PM, Erick Ghaumez eac...@gmail.com wrote:
 hi,

 yes Om i'm in !

 I'll start with some skinning tests for the stockQuote sample.
 I think I can send a first proposal next week.

 Just to be sure : the goal is to create a default skin which you can use with 
 SWF and html/js export ?
 Does the skinning system for SWF Flex will be the same as today ( Skin class 
 with MXMLG  FXG ) ?

 Erick


 Le 19 juin 2013 à 02:21, OmPrakash Muppirala bigosma...@gmail.com a écrit :


 What kind of beautification are you taking about?
 I'm don't think it looks as good as Spark or MX right now.  Colors,
 styles, spacing might make it look more like it is worth trying to use
 this stuff.

 Perhaps the designers in this list could help us design the next gen
 default look and feel for Flex?  Any takers?
 Thanks,
 Om


 Designers in the list,

 How about we try to put together a new visual look and feel for FlexJS?

 I am thinking that we can use the traditional approach of creating assets
 in AI or Fireworks and export them to formats we want.  This will also give
 me a chance to figure out the various approaches and tooling requirements.

 We have a lot of different options to do this, CSS3, FXG/MXML, SVG, etc.
 To get an idea of the first set of components we want skinned, here are
 the links to some samples Alex had put out a while ago [1,2]

 P.S.  Erick, you had pinged me on Twitter about wanting to help.  I hope
 you are in this list now :-)

 [1] http://people.apache.org/~aharui/FlexJS/
 [2] http://people.apache.org/~aharui/FlexJS/StatesTest/




-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

[jira] [Comment Edited] (FLEX-33592) mx.controls.MenuBar#getMenuAt TypeError


[ 
https://issues.apache.org/jira/browse/FLEX-33592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688042#comment-13688042
 ] 

Justin Mclean edited comment on FLEX-33592 at 6/19/13 2:42 PM:
---

Event.stopImmediatePropagation() fails to fix issue will look into it. Can 
reproduce issue in develop branch.

  was (Author: jmclean):
.event.stopImmediatePropagation() fails to fix issue will look into it. Can 
reproduce issue in develop branch.
  
 mx.controls.MenuBar#getMenuAt TypeError
 ---

 Key: FLEX-33592
 URL: https://issues.apache.org/jira/browse/FLEX-33592
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: Menu Bar
Affects Versions: Apache Flex 4.9.0
Reporter: Philip Mair
   Original Estimate: 2h
  Remaining Estimate: 2h

 When changing MenuBar dataProvider within click on MenuBar-Item causes a 
 RangeError in getMenuAt if the index was greater then new amount of MenuBar 
 Items.
 I solved this with following workaround:
   public override function getMenuAt(index:int):Menu
   {
   var menu:Menu = null;
   
   try
   {
   menu = super.getMenuAt(index);
   }
   catch(e: Error)
   {
   
   }
   if(menu == null) //return a fake menu to avoid 
 TypeError's
   return new Menu();
   else
   return menu;
   }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (FLEX-33592) mx.controls.MenuBar#getMenuAt TypeError


 [ 
https://issues.apache.org/jira/browse/FLEX-33592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Mclean resolved FLEX-33592.
--

   Resolution: Fixed
Fix Version/s: Apache Flex 4.10.0

Checked into develop branch. Added checks to stop RTE. Also fixed last index 
hanging about when changing data providers. Mustella MenuBar tests pass.

 mx.controls.MenuBar#getMenuAt TypeError
 ---

 Key: FLEX-33592
 URL: https://issues.apache.org/jira/browse/FLEX-33592
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: Menu Bar
Affects Versions: Apache Flex 4.9.0
Reporter: Philip Mair
 Fix For: Apache Flex 4.10.0

   Original Estimate: 2h
  Remaining Estimate: 2h

 When changing MenuBar dataProvider within click on MenuBar-Item causes a 
 RangeError in getMenuAt if the index was greater then new amount of MenuBar 
 Items.
 I solved this with following workaround:
   public override function getMenuAt(index:int):Menu
   {
   var menu:Menu = null;
   
   try
   {
   menu = super.getMenuAt(index);
   }
   catch(e: Error)
   {
   
   }
   if(menu == null) //return a fake menu to avoid 
 TypeError's
   return new Menu();
   else
   return menu;
   }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FLEX-33585) the dropDown of the spark combobox does not close regular when use alert to show the information of the selelcted item


 [ 
https://issues.apache.org/jira/browse/FLEX-33585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Mclean updated FLEX-33585:
-

Environment: win7 / win xp / OSX  (was: win7 and win xp)

 the dropDown of the spark combobox does not close regular when use alert to 
 show the information of the selelcted item
 --

 Key: FLEX-33585
 URL: https://issues.apache.org/jira/browse/FLEX-33585
 Project: Apache Flex
  Issue Type: Bug
  Components: Spark: ComboBox
Affects Versions: Adobe Flex SDK 4.6 (Release)
 Environment: win7 / win xp / OSX
Reporter: Thom Wu
  Labels: combobox, dropdown
   Original Estimate: 504h
  Remaining Estimate: 504h

 the sample code:
 s:WindowedApplication xmlns:fx=http://ns.adobe.com/mxml/2009; 
   xmlns:s=library://ns.adobe.com/flex/spark 
   xmlns:mx=library://ns.adobe.com/flex/mx
   fx:Script
   ![CDATA[
   import mx.controls.Alert;
   import spark.events.IndexChangeEvent;
   
   protected function 
 myCombobox_changingHandler(event:IndexChangeEvent):void {
   Alert.show(myCombobox.selectedItem);
   }
   
   ]]
   /fx:Script
   
   s:ComboBox id=myCombobox 
 changing=myCombobox_changingHandler(event)
   s:ArrayList
   fx:StringUSA/fx:String
   fx:StringChina/fx:String
   fx:StringIt/fx:String
   /s:ArrayList
   /s:ComboBox
 /s:WindowedApplication
 Test steps:
 1.click the openButton to open the dropDown of the combobox
 2.select the first item the of the Drop-down list item,then alert display the 
 selected item
 3.expect the dropDown of the combobox close,but it does not
 4.click the ok button of the alert to close the alert
 5.click the second item of the Drop-down list item，then the dropDown 
 close??alert display the select item
 The same operation, the combobox are inconsistent performance

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FLEX-33585) the dropDown of the spark combobox does not close regular when use alert to show the information of the selelcted item


[ 
https://issues.apache.org/jira/browse/FLEX-33585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688064#comment-13688064
 ] 

Justin Mclean commented on FLEX-33585:
--

Confirmed issue exists in Apache Flex 4.10 develop branch. No obvious fix from 
a quick look.

 the dropDown of the spark combobox does not close regular when use alert to 
 show the information of the selelcted item
 --

 Key: FLEX-33585
 URL: https://issues.apache.org/jira/browse/FLEX-33585
 Project: Apache Flex
  Issue Type: Bug
  Components: Spark: ComboBox
Affects Versions: Adobe Flex SDK 4.6 (Release)
 Environment: win7 and win xp
Reporter: Thom Wu
  Labels: combobox, dropdown
   Original Estimate: 504h
  Remaining Estimate: 504h

 the sample code:
 s:WindowedApplication xmlns:fx=http://ns.adobe.com/mxml/2009; 
   xmlns:s=library://ns.adobe.com/flex/spark 
   xmlns:mx=library://ns.adobe.com/flex/mx
   fx:Script
   ![CDATA[
   import mx.controls.Alert;
   import spark.events.IndexChangeEvent;
   
   protected function 
 myCombobox_changingHandler(event:IndexChangeEvent):void {
   Alert.show(myCombobox.selectedItem);
   }
   
   ]]
   /fx:Script
   
   s:ComboBox id=myCombobox 
 changing=myCombobox_changingHandler(event)
   s:ArrayList
   fx:StringUSA/fx:String
   fx:StringChina/fx:String
   fx:StringIt/fx:String
   /s:ArrayList
   /s:ComboBox
 /s:WindowedApplication
 Test steps:
 1.click the openButton to open the dropDown of the combobox
 2.select the first item the of the Drop-down list item,then alert display the 
 selected item
 3.expect the dropDown of the combobox close,but it does not
 4.click the ok button of the alert to close the alert
 5.click the second item of the Drop-down list item，then the dropDown 
 close??alert display the select item
 The same operation, the combobox are inconsistent performance

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Comment Edited] (FLEX-33585) the dropDown of the spark combobox does not close regular when use alert to show the information of the selelcted item


[ 
https://issues.apache.org/jira/browse/FLEX-33585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688064#comment-13688064
 ] 

Justin Mclean edited comment on FLEX-33585 at 6/19/13 3:14 PM:
---

Confirmed issue exists in Apache Flex 4.10 develop branch and on OSX as well. 
No obvious fix from a quick look.

  was (Author: jmclean):
Confirmed issue exists in Apache Flex 4.10 develop branch. No obvious fix 
from a quick look.
  
 the dropDown of the spark combobox does not close regular when use alert to 
 show the information of the selelcted item
 --

 Key: FLEX-33585
 URL: https://issues.apache.org/jira/browse/FLEX-33585
 Project: Apache Flex
  Issue Type: Bug
  Components: Spark: ComboBox
Affects Versions: Adobe Flex SDK 4.6 (Release)
 Environment: win7 / win xp / OSX
Reporter: Thom Wu
  Labels: combobox, dropdown
   Original Estimate: 504h
  Remaining Estimate: 504h

 the sample code:
 s:WindowedApplication xmlns:fx=http://ns.adobe.com/mxml/2009; 
   xmlns:s=library://ns.adobe.com/flex/spark 
   xmlns:mx=library://ns.adobe.com/flex/mx
   fx:Script
   ![CDATA[
   import mx.controls.Alert;
   import spark.events.IndexChangeEvent;
   
   protected function 
 myCombobox_changingHandler(event:IndexChangeEvent):void {
   Alert.show(myCombobox.selectedItem);
   }
   
   ]]
   /fx:Script
   
   s:ComboBox id=myCombobox 
 changing=myCombobox_changingHandler(event)
   s:ArrayList
   fx:StringUSA/fx:String
   fx:StringChina/fx:String
   fx:StringIt/fx:String
   /s:ArrayList
   /s:ComboBox
 /s:WindowedApplication
 Test steps:
 1.click the openButton to open the dropDown of the combobox
 2.select the first item the of the Drop-down list item,then alert display the 
 selected item
 3.expect the dropDown of the combobox close,but it does not
 4.click the ok button of the alert to close the alert
 5.click the second item of the Drop-down list item，then the dropDown 
 close??alert display the select item
 The same operation, the combobox are inconsistent performance

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Jenkins build is back to normal : flex-sdk_mustella #177

2013-06-19 Thread OmPrakash Muppirala

This is definitely a great milestone :-)

Om
On Jun 19, 2013 2:32 AM, Erik de Bruin e...@ixsoftware.nl wrote:

 Cool, we had a clean run!!!

 Let the games begin ;-)

 EdB



 On Wed, Jun 19, 2013 at 11:01 AM,  flex.muste...@gmail.com wrote:
  See http://localhost:8080/job/flex-sdk_mustella/177/changes
 



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl

[jira] [Updated] (FLEX-24257) DateField text scrolled when pressing DateField calendar button

[
https://issues.apache.org/jira/browse/FLEX-24257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Maurice Amsellem updated FLEX-24257:

Attachment: screenshot-2.jpg

DateField text scrolled when pressing DateField calendar button
---

Key: FLEX-24257
URL: https://issues.apache.org/jira/browse/FLEX-24257
Project: Apache Flex
Issue Type: Bug
Components: mx: DateField
Affects Versions: Adobe Flex SDK 3.2 (Release)
Environment: Affected OS(s): Windows
Affected OS(s): Windows 7
Browser: Internet Explorer 8.x
Language Found: English
Reporter: Adobe JIRA
Assignee: Justin Mclean
Fix For: Apache Flex 4.10.0

Attachments: screenshot-1.jpg, screenshot-2.jpg

Steps to reproduce:
1. Click on an editable DateField's calendar button when the DateField
doesn't currently have focus.
2. Observe the text in the DateField's textinput area.

Actual Results:
The text is automatically highlighted and scrolled to the left such that the
beginning part of the date text isn't visible.

Expected Results:
The text should not be highlighted or scrolled at all.

Workaround (if any):
Click in the textinput area before pressing the button.

Sample app:
?xml version=1.0 encoding=utf-8?
mx:Application xmlns:mx=http://www.adobe.com/2006/mxml; layout=vertical
mx:DateField editable=true/
/mx:Application
I see this on Flex SDK 3.2, 3.4 and 4.0.

[jira] [Updated] (FLEX-24257) DateField text scrolled when pressing DateField calendar button

[
https://issues.apache.org/jira/browse/FLEX-24257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Maurice Amsellem updated FLEX-24257:

Attachment: screenshot-3.jpg

DateField text scrolled when pressing DateField calendar button
---

Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg

Steps to reproduce:
1. Click on an editable DateField's calendar button when the DateField
doesn't currently have focus.
2. Observe the text in the DateField's textinput area.

Actual Results:
The text is automatically highlighted and scrolled to the left such that the
beginning part of the date text isn't visible.

Expected Results:
The text should not be highlighted or scrolled at all.

Workaround (if any):
Click in the textinput area before pressing the button.

[jira] [Commented] (FLEX-24257) DateField text scrolled when pressing DateField calendar button

[
https://issues.apache.org/jira/browse/FLEX-24257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688128#comment-13688128
]

Justin Mclean commented on FLEX-24257:
--

Looks like it not taking into effect the padding or edge metrics like the
parent class. In the en_US case the TextInput calks the width as 64 and
DateField calculates it as 60 and adds 2. It's better than before btw but still
not perfect.

DateField text scrolled when pressing DateField calendar button
---

Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg

Steps to reproduce:
1. Click on an editable DateField's calendar button when the DateField
doesn't currently have focus.
2. Observe the text in the DateField's textinput area.

Actual Results:
The text is automatically highlighted and scrolled to the left such that the
beginning part of the date text isn't visible.

Expected Results:
The text should not be highlighted or scrolled at all.

Workaround (if any):
Click in the textinput area before pressing the button.

Anyone see an issue with this code? :-)

Hi,

The rabbit hole keeps getting deeper. From displayDropdown in DateField.

if (screen.right  dd.getExplicitOrMeasuredWidth() + point.x 
screen.bottom  dd.getExplicitOrMeasuredHeight() + point.y)
{
xVal = point.x
yVal = point.y - dd.getExplicitOrMeasuredHeight();
openPos = 1;
}
else if (screen.right  dd.getExplicitOrMeasuredWidth() + point.x 
 screen.bottom  dd.getExplicitOrMeasuredHeight() + point.y)
{
xVal = point.x - dd.getExplicitOrMeasuredWidth() + 
downArrowButton.width;
yVal = point.y - dd.getExplicitOrMeasuredHeight();
openPos = 2;
}
else if (screen.right  dd.getExplicitOrMeasuredWidth() + point.x 
 screen.bottom  dd.getExplicitOrMeasuredHeight() + point.y)
{
xVal = point.x - dd.getExplicitOrMeasuredWidth() + 
downArrowButton.width;
yVal = point.y + unscaledHeight;
openPos = 3;
}
else
// Why do we need to disable downArrowButton when its hidden?
//downArrowButton.enabled = false;
openPos = 0;

What's the value of openPos after this? Why braces should be required IMO! :-)

Justin

Re: Anyone see an issue with this code? :-)

Hi,

And this may not do what you expect.

if (true)
trace(true);
else
// will false be traced?
trace(false);

Justin

Re: Anyone see an issue with this code? :-)

I feel an aslint application coming up...

;-)

EdB



On Wednesday, June 19, 2013, Justin Mclean wrote:

 Hi,

 And this may not do what you expect.

 if (true)
 trace(true);
 else
 // will false be traced?
 trace(false);

 Justin



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

[jira] [Commented] (FLEX-24257) DateField text scrolled when pressing DateField calendar button

[
https://issues.apache.org/jira/browse/FLEX-24257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688156#comment-13688156
]

Maurice Amsellem commented on FLEX-24257:
-

I did more testing with locale= fr_FR, using the date that gets the maxWidth (=
28/12/2000) and scrolling occurs in this case as well.
mx:DateField editable=true selectedDate={new Date(2000,11,28)}/
This confirms your previous comment

DateField text scrolled when pressing DateField calendar button
---

Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg

Steps to reproduce:
1. Click on an editable DateField's calendar button when the DateField
doesn't currently have focus.
2. Observe the text in the DateField's textinput area.

Actual Results:
The text is automatically highlighted and scrolled to the left such that the
beginning part of the date text isn't visible.

Expected Results:
The text should not be highlighted or scrolled at all.

Workaround (if any):
Click in the textinput area before pressing the button.

[jira] [Reopened] (FLEX-24257) DateField text scrolled when pressing DateField calendar button

[
https://issues.apache.org/jira/browse/FLEX-24257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Justin Mclean reopened FLEX-24257:
--

Look into edge and padding to see all is correct.

DateField text scrolled when pressing DateField calendar button
---

Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg

Steps to reproduce:
1. Click on an editable DateField's calendar button when the DateField
doesn't currently have focus.
2. Observe the text in the DateField's textinput area.

Actual Results:
The text is automatically highlighted and scrolled to the left such that the
beginning part of the date text isn't visible.

Expected Results:
The text should not be highlighted or scrolled at all.

Workaround (if any):
Click in the textinput area before pressing the button.

Re: Anyone see an issue with this code? :-)

Hi,

 I feel an aslint application coming up...
It exists for JS so AS shouldn't be hard :-) Flex PMD does a good job (but 
requires a little tuning) I once run it over the Flex SDK and was rather 
horrified by the results. :-)

Justin

Re: Apache Flex 4.10.0 release?

I don't have access to, nor knowledge off, a Linux distro, but if you
have boring copy-paste stuff to fix for those path issues I'll be
glad to help...

What is the timeframe for those .8 releases?

EdB



On Wed, Jun 19, 2013 at 7:28 PM, Justin Mclean jus...@classsoftware.com wrote:
 Hi,

 I've been slowing working towards it but there's still a few outstanding 
 issues that need to be sorted.

 I'd really like to see Linux support added but currently a fair number of the 
 tests fail to compile (mostly path issues) and quite a few fail.

 Air 3.8/FP 11.8 should be released soon so we should start thinking about 
 testing on that.

 Justin

 On 20/06/2013, at 12:50 AM, Erik de Bruin wrote:

 Hi,

 Why aren't we talking about this anymore? We are at most 2 bug fixes
 and one test (FLEX-33547) away from being zarro boogs. Mustella is
 running cleanly on both Mac and Windows (Alex's machine and the VM)
 and the Installer should be at or near a new release as well (Om?).

 We should really start to get things together and work toward a
 release sooner rather than later...

 EdB



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl




-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Apache Flex 4.10.0 release?

2013-06-19 Thread Alex Harui

How come Mac file system isn't case sensitive like Linux?  Is there a way
to make it case-sensitive so we can flush out these issues?

I tried putting a Linux distro in my VMWare.  It looked like it was going
to work then it croaked.  I'll try again someday.

On 6/19/13 10:31 AM, Erik de Bruin e...@ixsoftware.nl wrote:

I don't have access to, nor knowledge off, a Linux distro, but if you
have boring copy-paste stuff to fix for those path issues I'll be
glad to help...

What is the timeframe for those .8 releases?

EdB



On Wed, Jun 19, 2013 at 7:28 PM, Justin Mclean jus...@classsoftware.com
wrote:
 Hi,

 I've been slowing working towards it but there's still a few
outstanding issues that need to be sorted.

 I'd really like to see Linux support added but currently a fair number
of the tests fail to compile (mostly path issues) and quite a few fail.

 Air 3.8/FP 11.8 should be released soon so we should start thinking
about testing on that.

 Justin

 On 20/06/2013, at 12:50 AM, Erik de Bruin wrote:

 Hi,

 Why aren't we talking about this anymore? We are at most 2 bug fixes
 and one test (FLEX-33547) away from being zarro boogs. Mustella is
 running cleanly on both Mac and Windows (Alex's machine and the VM)
 and the Installer should be at or near a new release as well (Om?).

 We should really start to get things together and work toward a
 release sooner rather than later...

 EdB



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl




-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

[jira] [Created] (FLEX-33594) Flex Theme properties broken with 4.9.1 SDK

2013-06-19 Thread Beau N Brewer (JIRA)

Beau N Brewer created FLEX-33594:


 Summary: Flex Theme properties broken with 4.9.1 SDK
 Key: FLEX-33594
 URL: https://issues.apache.org/jira/browse/FLEX-33594
 Project: Apache Flex
  Issue Type: Bug
  Components: DMV Flex Builder Integration, Themes
Affects Versions: Apache Flex 4.9.0
 Environment: OSX, Flash Builder 4.7
Reporter: Beau N Brewer


After selecting 4.9.1 as the Flex SDK, you can't access the Flex Theme 
properties without getting an error.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FLEX-33594) Flex Theme properties broken with 4.9.1 SDK

2013-06-19 Thread Beau N Brewer (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLEX-33594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beau N Brewer updated FLEX-33594:
-

Attachment: Screen Shot 2013-06-19 at 11.52.30 AM.png

 Flex Theme properties broken with 4.9.1 SDK
 ---

 Key: FLEX-33594
 URL: https://issues.apache.org/jira/browse/FLEX-33594
 Project: Apache Flex
  Issue Type: Bug
  Components: DMV Flex Builder Integration, Themes
Affects Versions: Apache Flex 4.9.0
 Environment: OSX, Flash Builder 4.7
Reporter: Beau N Brewer
 Attachments: Screen Shot 2013-06-19 at 11.52.30 AM.png


 After selecting 4.9.1 as the Flex SDK, you can't access the Flex Theme 
 properties without getting an error.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Path issues with Linux

HI,

 I don't have access to, nor knowledge off, a Linux distro, but if you
 have boring copy-paste stuff to fix for those path issues I'll be
 glad to help...
Bit more involved than that. In some cases it just files names with wrong case 
so it doesn't compile, in others it run time loaded assets. Some are obvious 
.GIF vs .gif, other are more subtle I vs i in class names etc.

It's fairly easy to set up a Ubuntu VM and that's what I've been playing about 
with.

 What is the timeframe for those .8 releases?

No idea - there been 3 or 4 betas so it should be shortly. I have updated the 
SDK to work with the beta.

Justin

[jira] [Commented] (FLEX-33594) Flex Theme properties broken with 4.9.1 SDK


[ 
https://issues.apache.org/jira/browse/FLEX-33594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688224#comment-13688224
 ] 

Justin Mclean commented on FLEX-33594:
--

On OSX with FB 4.6 can't reproduce with 4.9.1 or 4.10 develop branch - may be a 
FB 4.7 issue. Can you attach a small sample project that has the issue?

 Flex Theme properties broken with 4.9.1 SDK
 ---

 Key: FLEX-33594
 URL: https://issues.apache.org/jira/browse/FLEX-33594
 Project: Apache Flex
  Issue Type: Bug
  Components: DMV Flex Builder Integration, Themes
Affects Versions: Apache Flex 4.9.0
 Environment: OSX, Flash Builder 4.7
Reporter: Beau N Brewer
 Attachments: Screen Shot 2013-06-19 at 11.52.30 AM.png


 After selecting 4.9.1 as the Flex SDK, you can't access the Flex Theme 
 properties without getting an error.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FLEX-33592) mx.controls.MenuBar#getMenuAt TypeError


[ 
https://issues.apache.org/jira/browse/FLEX-33592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688232#comment-13688232
 ] 

Philip Mair commented on FLEX-33592:


The mouseDownHandler is not null safe in acessing Menu m ... 

 m.supposedToLoseFocus = true; //m may be null here

 mx.controls.MenuBar#getMenuAt TypeError
 ---

 Key: FLEX-33592
 URL: https://issues.apache.org/jira/browse/FLEX-33592
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: Menu Bar
Affects Versions: Apache Flex 4.9.0
Reporter: Philip Mair
 Fix For: Apache Flex 4.10.0

   Original Estimate: 2h
  Remaining Estimate: 2h

 When changing MenuBar dataProvider within click on MenuBar-Item causes a 
 RangeError in getMenuAt if the index was greater then new amount of MenuBar 
 Items.
 I solved this with following workaround:
   public override function getMenuAt(index:int):Menu
   {
   var menu:Menu = null;
   
   try
   {
   menu = super.getMenuAt(index);
   }
   catch(e: Error)
   {
   
   }
   if(menu == null) //return a fake menu to avoid 
 TypeError's
   return new Menu();
   else
   return menu;
   }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FLEX-24257) DateField text scrolled when pressing DateField calendar button


[ 
https://issues.apache.org/jira/browse/FLEX-24257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688235#comment-13688235
 ] 

Maurice Amsellem commented on FLEX-24257:
-

I think I understood where the computation error is:

in TextInput, the measured width is :
measuredWidth = textWidth + 8 + paddingLeft + paddingRight
(paddingLeft = 2, and paddingRight = 2)
eg. for 06/19/2013, that gives 62+8+2+2 = 74

Now in DateField, the inner TextInput should receive the same width, but it's 
not the case:
measuredWidth = maxTextWidth + 8 + gap + buttonWidth+ paddingLeft + paddingRight
but here paddingLeft and paddingRight are those of the DateField, not TextInput 
, so they equal 0
measuredWidth= 62 + 8 + 2 + 23 + 0 + 0 = 95;
Then in updateDisplayList, textField receives: 
textInput.setActualSize(w - arrowWidth - gap

As you can see, the TI paddings are missing from the calculations, the widht is 
4 pixels less than what it should be.

What do you think ?


 DateField text scrolled when pressing DateField calendar button
 ---

 Key: FLEX-24257
 URL: https://issues.apache.org/jira/browse/FLEX-24257
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: DateField
Affects Versions: Adobe Flex SDK 3.2 (Release)
 Environment: Affected OS(s): Windows
 Affected OS(s): Windows 7
 Browser: Internet Explorer 8.x
 Language Found: English
Reporter: Adobe JIRA
Assignee: Justin Mclean
 Fix For: Apache Flex 4.10.0

 Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg


 Steps to reproduce:
 1. Click on an editable DateField's calendar button when the DateField 
 doesn't currently have focus.
 2. Observe the text in the DateField's textinput area.
  
  Actual Results:
 The text is automatically highlighted and scrolled to the left such that the 
 beginning part of the date text isn't visible. 
  
  Expected Results:
 The text should not be highlighted or scrolled at all. 
  
  Workaround (if any):
 Click in the textinput area before pressing the button.
  
 Sample app:
 ?xml version=1.0 encoding=utf-8?
 mx:Application xmlns:mx=http://www.adobe.com/2006/mxml; layout=vertical
   mx:DateField editable=true/
 /mx:Application
 I see this on Flex SDK 3.2, 3.4 and 4.0.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Comment Edited] (FLEX-24257) DateField text scrolled when pressing DateField calendar button


[ 
https://issues.apache.org/jira/browse/FLEX-24257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688235#comment-13688235
 ] 

Maurice Amsellem edited comment on FLEX-24257 at 6/19/13 6:06 PM:
--

I think I understood where the computation error is:

in TextInput, the measured width is :
measuredWidth = textWidth + 8 + paddingLeft + paddingRight
(paddingLeft = 2, and paddingRight = 2)
eg. for 06/19/2013, that gives 62+8+2+2 = 74

Now in DateField, the inner TextInput should receive the same width, but it's 
not the case:
measuredWidth = maxTextWidth + 8 + gap + buttonWidth+ paddingLeft + paddingRight
but here paddingLeft and paddingRight are those of the DateField, not TextInput 
, so they equal 0
measuredWidth= 62 + 8 + 2 + 23 + 0 + 0 = 95;
Then in updateDisplayList, textField receives: 
textInput.setActualSize(w - arrowWidth - gap
95 - 23 - 2 = 70 instead of 74

As you can see, the TI paddings are missing from the calculations, the widht is 
4 pixels less than what it should be.

What do you think ?


  was (Author: mamsellem):
I think I understood where the computation error is:

in TextInput, the measured width is :
measuredWidth = textWidth + 8 + paddingLeft + paddingRight
(paddingLeft = 2, and paddingRight = 2)
eg. for 06/19/2013, that gives 62+8+2+2 = 74

Now in DateField, the inner TextInput should receive the same width, but it's 
not the case:
measuredWidth = maxTextWidth + 8 + gap + buttonWidth+ paddingLeft + paddingRight
but here paddingLeft and paddingRight are those of the DateField, not TextInput 
, so they equal 0
measuredWidth= 62 + 8 + 2 + 23 + 0 + 0 = 95;
Then in updateDisplayList, textField receives: 
textInput.setActualSize(w - arrowWidth - gap

As you can see, the TI paddings are missing from the calculations, the widht is 
4 pixels less than what it should be.

What do you think ?

  
 DateField text scrolled when pressing DateField calendar button
 ---

 Key: FLEX-24257
 URL: https://issues.apache.org/jira/browse/FLEX-24257
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: DateField
Affects Versions: Adobe Flex SDK 3.2 (Release)
 Environment: Affected OS(s): Windows
 Affected OS(s): Windows 7
 Browser: Internet Explorer 8.x
 Language Found: English
Reporter: Adobe JIRA
Assignee: Justin Mclean
 Fix For: Apache Flex 4.10.0

 Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg


 Steps to reproduce:
 1. Click on an editable DateField's calendar button when the DateField 
 doesn't currently have focus.
 2. Observe the text in the DateField's textinput area.
  
  Actual Results:
 The text is automatically highlighted and scrolled to the left such that the 
 beginning part of the date text isn't visible. 
  
  Expected Results:
 The text should not be highlighted or scrolled at all. 
  
  Workaround (if any):
 Click in the textinput area before pressing the button.
  
 Sample app:
 ?xml version=1.0 encoding=utf-8?
 mx:Application xmlns:mx=http://www.adobe.com/2006/mxml; layout=vertical
   mx:DateField editable=true/
 /mx:Application
 I see this on Flex SDK 3.2, 3.4 and 4.0.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Path issues with Linux

Hi,

Here's my rough notes from the other week.

Application 1 error -  height different in one test
collections 0 errors
CompiletimeLocalization - fails to compile
components - fails to compile
containers - JPG path/case issues
 [java] =
 [java] Passes: 2440
 [java] Fails: 138
 [java] =

containers/Accordian
 [java] =
 [java] Passes: 302
 [java] Fails: 32
 [java] =
containers/ApplicaipnControlBar - 0 errors
containers/Box - 0 errors
containers/Canvas - heights off by 0.5 pixels
 [java] =
 [java] Passes: 208
 [java] Fails: 2
 [java] =
containers/ControlBar - 0 errors
containers/DividedBox - path issue???
 [java] =
 [java] Passes: 47
 [java] Fails: 4
 [java] =
containers/form - 0 errors
containers/FormHeading - file path issues
 [java] =
 [java] Passes: 6
 [java] Fails: 3
 [java] =
containers/FormItem
 [java] =
 [java] Passes: 82
 [java] Fails: 2
 [java] =
containers/Grid - 0 errors
containers/H_V_Box - bitmap compare fails
 [java] =
 [java] Passes: 6
 [java] Fails: 7
 [java] =
containers/Panel - path and other issues
 [java] =
 [java] Passes: 423
 [java] Fails: 36
 [java] =
containers/tabnavigator - mostly bitmap compare fails
 [java] =
 [java] Passes: 242
 [java] Fails: 32
 [java] =
containers/tile - 1 test fails
containers/TitleWindow
 [java] =
 [java] Passes: 64
 [java] Fails: 19
 [java] =
containers/ViewStack
 [java] =
 [java] Passes: 21
 [java] Fails: 2
 [java] =
DownloadProgressBar 0 errors
Embed  0 errors
experimental 0 errors
formatters 0 errors
Graphics 0 errors
GraphicsTags 1 error
gumbo - fails to compile
itemRenders - passible JPG path/case issue a few broken images
 [java] =
 [java] Passes: 292
 [java] Fails: 18
 [java] =
LangPacks - does this run in OSX/Windows?
 [java] =
 [java] Passes: 2823
 [java] Fails: 1018
 [java] =
listDatEffect - 0 errors
Managers - fails to compile path issue
MarshelPlan - fails to compile
Mirroring
 [java] =
 [java] Passes: 13
 [java] Fails: 2
 [java] =
Modules - height different in one test
 [java] =
 [java] Passes: 172
 [java] Fails: 1
 [java] =
mx/binding - 0 erorrs
mx/collections - 0 errors
mx/controls - 0 errors
mx/effects - compile fails path issue
mx/graphics 
 [java] =
 [java] Passes: 40
 [java] Fails: 17
 [java] =
mx/states - 0 errors
mx/styles - 0 errors
mx/utils - path issues
 [java] =
 [java] Passes: 15
 [java] Fails: 4
 [java] =
PerModuelStles - fails to compile path issue
Printing - fails to compile
resources - fails to compile
rpc - 0 errors
RunTimeLocilization - fails to compile path issues
SkinningImprovments - fails to compile
SkinStats - fails to compile path issues
spark/collections - fails to compiel path issues
spark/components - fails
 [java] =
 [java] Passes: 533
 [java] Fails: 173
 [java]

Re: Path issues with Linux

Hi,

And while it would be nice to get all the test to pass I think having them 
compile and the obvious path issues fixed is probably good enough for an 
initial release.

There still one or open build questions as well eg What do we do about the 
Pixel Blender files?

Hopefully someone with more recent Linux experience (last time I used it full 
time was when 16Mb of memory cost more than $1000) can help out.

Thanks,
Justin

[jira] [Commented] (FLEX-24257) DateField text scrolled when pressing DateField calendar button

[
https://issues.apache.org/jira/browse/FLEX-24257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688267#comment-13688267
]

Justin Mclean commented on FLEX-24257:
--

Thanks that looks like a viable fix I'll double check and check it in tomorrow
for you.

DateField text scrolled when pressing DateField calendar button
---

Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg

Steps to reproduce:
1. Click on an editable DateField's calendar button when the DateField
doesn't currently have focus.
2. Observe the text in the DateField's textinput area.

Actual Results:
The text is automatically highlighted and scrolled to the left such that the
beginning part of the date text isn't visible.

Expected Results:
The text should not be highlighted or scrolled at all.

Workaround (if any):
Click in the textinput area before pressing the button.

Re: Jenkins build is back to normal : flex-sdk_mustella #177

2013-06-19 Thread Alex Harui

I just tried it on my Mac.

20 minutes for AIR.
82 minutes for mobile.
Add more for -failures runs if needed.

I got a lot of bitmap failures that I'm looking into now.  Which reminded
me that if a check-in goes bad and generates a lot of bitmap failures that
slows things down (all the bad pngs have to be written to disk).  Is there
any way to set up jenkins to wait N minutes after a job completes before
starting the next job?  What would happen if we run every 12 hours but
sometimes a job doesn't complete in those 12 hours?

-Alex

On 6/19/13 7:28 AM, Erik de Bruin e...@ixsoftware.nl wrote:

Can you give me an indication how long a run of each type takes?

EdB



On Wednesday, June 19, 2013, Alex Harui wrote:

 For AIR it should be ./mini_run.sh -apollo tests/apollo

 For mobile you'll need to swap in a different local.properties before
 running mini_run on the mobile directory.  See the wiki page for how to
 set that up.

 -Alex

 On 6/19/13 2:48 AM, Erik de Bruin e...@ixsoftware.nl javascript:;
 wrote:

 11.1, indeed.
 
 And I guess not on the AIR and mobile tests... what ant
 targets/switches make that happen?
 
 EdB
 
 
 
 On Wed, Jun 19, 2013 at 11:41 AM, Justin Mclean
jmcl...@apache.orgjavascript:;
 
 wrote:
  Hi,
 
  Cool, we had a clean run!!!
 
  What version of FP was being used? (Windows and 11.1)
 
  And you'll probably hate me for bringing this up but did we run the
 mobile or AIR tests?
 
  Thanks,
  Justin
 
 
 
 --
 Ix Multimedia Software
 
 Jan Luykenstraat 27
 3521 VB Utrecht
 
 T. 06-51952295
 I. www.ixsoftware.nl



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

[jira] [Commented] (FLEX-24257) DateField text scrolled when pressing DateField calendar button

[
https://issues.apache.org/jira/browse/FLEX-24257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688361#comment-13688361
]

Maurice Amsellem commented on FLEX-24257:
-

That's cool. Thank you.

DateField text scrolled when pressing DateField calendar button
---

Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg

Steps to reproduce:
1. Click on an editable DateField's calendar button when the DateField
doesn't currently have focus.
2. Observe the text in the DateField's textinput area.

Actual Results:
The text is automatically highlighted and scrolled to the left such that the
beginning part of the date text isn't visible.

Expected Results:
The text should not be highlighted or scrolled at all.

Workaround (if any):
Click in the textinput area before pressing the button.

Lining up the ducks for a 4.10 release

2013-06-19 Thread OmPrakash Muppirala

Here are some things we want to start prepping:

1.  Build and test SDK release artifacts
2.  Build and test Installer release artifacts
3.  Update the website
4.  PR efforts (blog post, Apache wide announcements, PR release, Twitter,
Facebook)
(Anything else, please add to this list)

It would be great if we use this thread to track these line items.  Any
volunteers want to pick items from this list and start working on them?

I pick (2) - Build and test Installer release artifacts.

Thanks,
Om

Re: Lining up the ducks for a 4.10 release