from:"Justin Mclean \(JIRA\)"

[jira] [Updated] (FLEX-14602) mx:Zoom does not work correctly in mx:Sequence or mx:Parallel with other effects

2013-06-24 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-14602:
-

Labels: easytest  (was: )

 mx:Zoom does not work correctly in mx:Sequence or mx:Parallel with other 
 effects
 

 Key: FLEX-14602
 URL: https://issues.apache.org/jira/browse/FLEX-14602
 Project: Apache Flex
  Issue Type: Bug
  Components: Effects
Affects Versions: Adobe Flex SDK 3.0 (Release)
 Environment: Affected OS(s): Windows
 Affected OS(s): Windows XP
 Browser: Firefox 2.x
 Language Found: English
Reporter: Adobe JIRA
  Labels: easytest

 ?xml version=1.0 encoding=utf-8?
 mx:Application xmlns:mx=http://www.adobe.com/2006/mxml; layout=absolute
   mx:Canvas width=400 height=400 horizontalScrollPolicy=off 
 verticalScrollPolicy=off
   mx:Image id=image1 
 source=http://www.adobe.com/images/store/product_boxshots/150x150/box_flexbuilderstandard3_150x150.jpg;
  x=0 y=0 width=100% height=100% creationCompleteEffect={loop1} 
 autoLoad=true/
   /mx:Canvas
   !-- same problem with mx:Parallel --
   mx:Sequence id=loop1 repeatCount=0 
   mx:Zoom duration=2000 zoomWidthFrom=0.1 
 zoomHeightFrom=0.1 zoomWidthTo=2.0 zoomHeightTo=2.0/
   
   !-- uncomment this to get some unwanted nasty effects, same 
 problem with other mx:Effects
   mx:Pause duration=1000/
   --
   /mx:Sequence
 /mx:Application
 Steps to reproduce:
 1. uncomment the mx:Pause effect in above source code
  
  Actual Results:
 image center shifts to 0,0 of canvas for no reason
  
  Expected Results:
  same as with mx:Pause commented out, that is zoom effect working correctly
  
  Workaround (if any):
 don't use effects

--
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-23746) NumericStepper as itemRenders in DataGrid don't work as expected with labelFunctions

2013-06-24 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-23746:
-

Labels: easytest  (was: )

 NumericStepper as itemRenders in DataGrid don't work as expected with 
 labelFunctions
 

 Key: FLEX-23746
 URL: https://issues.apache.org/jira/browse/FLEX-23746
 Project: Apache Flex
  Issue Type: Bug
  Components: Formatters
Affects Versions: Adobe Flex SDK 3.5 (Release)
 Environment: Affected OS(s): All OS Platforms
 Affected OS(s): All OS Platforms
 Browser: Firefox 3.x
 Language Found: English
Reporter: Adobe JIRA
  Labels: easytest

 Steps to reproduce:
 1. Compile attached app
 2. Run app
 3. Enter 5 (without quotes) as the new price of the item in the top 
 datagrid by clicking in it, typing numbers and clicking outside DG again
 4. Click the new formatted price
  
  Actual Results:
 item editor displays '50' in numeric stepper 
  
  Expected Results:
 item editor displays '5' in numeric stepper 
 It appears the item editor gets the value to edit from the labelFunction not 
 the dataProvider, and so is choking on the comma.
 This is unexpected.
  
  Workaround (if any):
 Replace labelFunction with simple itemRender, as in the second data grid
 mx:DataGridColumn dataField=Price editorDataField=value
 mx:itemRenderer
 mx:Component
 mx:Label 
 text={outerDocument._moneyFormatter.format( data.Price )}/
 /mx:Component
 /mx:itemRenderer
 mx:itemEditor
 mx:Component
 mx:NumericStepper stepSize=0.01 maximum=99/
 /mx:Component
 /mx:itemEditor
 /mx:DataGridColumn

--
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-25932) PopUpManager.addPopUp disables binding

2013-06-24 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-25932:
-

Labels: easyfix easytest  (was: )

 PopUpManager.addPopUp disables binding
 --

 Key: FLEX-25932
 URL: https://issues.apache.org/jira/browse/FLEX-25932
 Project: Apache Flex
  Issue Type: Bug
  Components: PopUp Manager
Affects Versions: Adobe Flex SDK 4.1 (Release)
 Environment: Affected OS(s): Windows
 Affected OS(s): Windows XP
 Browser: Firefox 3.x
 Language Found: English
Reporter: Adobe JIRA
  Labels: easyfix, easytest

   Steps to reproduce:
 Create simple component with binding between selected item of combobox and 
 text :
 mx:VBox xmlns:fx=http://ns.adobe.com/mxml/2009; 
xmlns:s=library://ns.adobe.com/flex/spark 
xmlns:mx=library://ns.adobe.com/flex/mx
   mx:ComboBox id=cb labelField=name
   mx:dataProvider
   s:ArrayCollection
   fx:Object name=item1/
   fx:Object name=item2/
   fx:Object name=item3/
   fx:Object name=item4/
   /s:ArrayCollection
   /mx:dataProvider
   /mx:ComboBox
   mx:Text text={cb.selectedItem.name}/
 /mx:VBox
 Create an application using the component, and pop up the component when 
 button is clicked :
 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 
  xmlns:component=component.*
   fx:Script
   ![CDATA[
   import mx.managers.PopUpManager;
   ]]
   
   /fx:Script
   
   mx:VBox id=container
   component:TestBindPopup id=popUp/
   mx:Button label=click click={PopUpManager.addPopUp(popUp, 
 this);}/
   /mx:VBox
 /s:Application
  
  Actual Results:
  
 Binding is correct when component is not popped up, but after the addPopUp 
 binding is disabled.
 When the addPopUp is called, SystemManager does an addChild which calls a 
 removeChild on component container. During removeChild the container 
 disables all binding of the component. 
  
  Expected Results:
 Binding is enabled after the addPopup like in Flex 3.
  
  
  Workaround (if any):
  
 Call BindingManager.setEnabled(popUp, true) after the addPopup.
 

--
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-20726) Only dispatchEvent if [Bindable] hasEventListener

2013-06-24 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-20726:
-

Labels: easyfix easytext  (was: )

 Only dispatchEvent if [Bindable] hasEventListener
 -

 Key: FLEX-20726
 URL: https://issues.apache.org/jira/browse/FLEX-20726
 Project: Apache Flex
  Issue Type: Improvement
  Components: Spark: Effects
Affects Versions: Adobe Flex SDK Previous
 Environment: Affected OS(s): All OS Platforms
 Affected OS(s): All OS Platforms
 Browser: Safari
 Language Found: English
Reporter: Adobe JIRA
  Labels: easyfix, easytext

 Steps to reproduce:
 1. Animate x, y, width, height, or alpha
 2. Don't bind to any of those properties
 3. 
  
  Actual Results:
  Every frame it dispatches a ton of events because in the setters you have 
 dispatchEvent(new Event(xChanged)) or whatever.  This should be more 
 like: dispatchPropertyChangeEvent(xChanged);
 function dispatchPropertyChangeEvent(type:String):void {
  if (hasEventListener(type)) dispatchEvent(new Event(type));
 } 
  
  Expected Results:
  Don't dispatch events if I'm not binding.
  
  Workaround (if any):
  None, unless we change the source.

--
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-13414) Fade Effects Don't Work When Duration is Set to 0

2013-06-24 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-13414:
-

Labels: easytest  (was: )

 Fade Effects Don't Work When Duration is Set to 0
 -

 Key: FLEX-13414
 URL: https://issues.apache.org/jira/browse/FLEX-13414
 Project: Apache Flex
  Issue Type: Bug
  Components: Effects
Affects Versions: Adobe Flex SDK 2.0.1 (Release)
 Environment: Affected OS(s): Windows
 Affected OS(s): Windows XP
 Language Found: English
Reporter: Adobe JIRA
  Labels: easytest

 Steps to reproduce:
 1.  Run attached MXML application
 2.  Click on the 'Toggle Visibility' button twice
 3.  Notice that after the second button click, only the text from the List 
 items is visible
  
  Actual Results:
 Fade effect does not execute completely causing the component to only be 
 partially visible
  
  Expected Results:
 Fade effect should completely execute
  
  
  Workaround (if any):
 Don't set the Fade effect duration to 0.  Interestingly, the effect executes 
 correctly if the duration is set to negative values, but not 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] [Updated] (FLEX-18832) List control with verticalscrollbar and glow effect in scrollbar's style - throws error during effect

2013-06-24 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-18832:
-

Labels: easyfix easytest  (was: )

 List control with verticalscrollbar and glow effect in scrollbar's style - 
 throws error during effect
 -

 Key: FLEX-18832
 URL: https://issues.apache.org/jira/browse/FLEX-18832
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: List
Affects Versions: Adobe Flex SDK 3.2 (Release)
 Environment: Affected OS(s): Windows
 Affected OS(s): Windows XP
 Language Found: English
Reporter: Adobe JIRA
  Labels: easyfix, easytest

 Steps to reproduce:
 1. Create mxml application
 2. Put mx:list id=list1
 3. Specify vertical scrollbar style with rollOverEffect
 4. Specify listverticalScrollPolicy=on
 5. Put a button, on click bind list1.dataProvider = new Array()  (important 
 to bind array with less elements, than needed to show thumb on vertical 
 scrollbar)
 6. Run application
 7. Move mouse over vertical scrollbar 
 8. Before glow effect finished - click button to rebind dataProvider
 9. See error thrown
 mxml application listing:
 ?xml version=1.0 encoding=utf-8?
 mx:Application xmlns:mx=http://www.adobe.com/2006/mxml; layout=absolute 
 xmlns:ns1=com.turbostool.client.rides.* width=570 height=500 
 xmlns:text=flash.text.*
   
   mx:Style
 .myScrollStyle
 {
   rollOverEffect: buttonGlowIn;
 }
   /mx:Style  
   mx:List id=list1 verticalScrollPolicy=on width=200 height=200
 verticalScrollBarStyleName=myScrollStyle
 
   /mx:List
   mx:Button label=rebind error click=list1.dataProvider=new Array() 
 y=208  x=106/

   mx:Glow id=buttonGlowIn color=0xee alphaFrom=0.1 alphaTo=0.5 
 duration=100 blurYFrom=0 blurXFrom=0
  blurYTo=10 blurXTo=10/
   
 /mx:Application
  Actual Results:
 TypeError: Error #1009: Cannot access a property or method of a null object 
 reference.
   at 
 mx.controls.scrollClasses::ScrollBar/updateDisplayList()[C:\autobuild\3.2.0\frameworks\projects\framework\src\mx\controls\scrollClasses\ScrollBar.as:1050]
   at 
 mx.core::UIComponent/validateDisplayList()[C:\autobuild\3.2.0\frameworks\projects\framework\src\mx\core\UIComponent.as:6351]
   at 
 mx.managers::LayoutManager/validateDisplayList()[C:\autobuild\3.2.0\frameworks\projects\framework\src\mx\managers\LayoutManager.as:622]
   at 
 mx.managers::LayoutManager/doPhasedInstantiation()[C:\autobuild\3.2.0\frameworks\projects\framework\src\mx\managers\LayoutManager.as:695]
   at Function/http://adobe.com/AS3/2006/builtin::apply()
   at 
 mx.core::UIComponent/callLaterDispatcher2()[C:\autobuild\3.2.0\frameworks\projects\framework\src\mx\core\UIComponent.as:8628]
   at 
 mx.core::UIComponent/callLaterDispatcher()[C:\autobuild\3.2.0\frameworks\projects\framework\src\mx\core\UIComponent.as:8568]
  
  Expected Results:
  
 Must not throw error, must fill list with data even during visual effect on 
 scrollbar, even if thumb will not appear yet
  
  Workaround (if any):
  
 Remove effects from scrollbar style

--
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-25372) Error with MenuBar

2013-06-20 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-25372:
-

Labels: easytest  (was: )

 Error with MenuBar
 --

 Key: FLEX-25372
 URL: https://issues.apache.org/jira/browse/FLEX-25372
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: Menu Bar
Affects Versions: Adobe Flex SDK 3.5 (Release)
 Environment: Affected OS(s): Windows
 Affected OS(s): Windows 7
 Browser: Firefox 3.x
 Language Found: English
Reporter: Adobe JIRA
  Labels: easytest

 Steps to reproduce:
   mx:MenuBar width=100% labelField=@label id=MyMenuBar
   mx:XMLList
   menuitem label=Father1
   menuitem label=Son1
   menuitem label=Grandson1
   menuitem 
 label=GreatGrandson1 data=teste1/
   menuitem 
 label=GreatGrandson2 data=teste2/
   menuitem 
 label=GreatGrandson3 data=teste3/
   /menuitem
   /menuitem
   /menuitem
   /mx:XMLList
   /mx:MenuBar
  
  Actual Results:
  The following menu appears:
  Father1 - Son1 - Great Grandson1
  - Great Grandson2
  - Great Grandson3
  
  Expected Results:
  The following menu was expected:
  Father1 - Son1 - Grandson1 - Great Grandson1
   - Great Grandson2
   - Great Grandson3
  
  Workaround (if any):
  Not found yet.

--
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-19434) When MenuBar is updated with keyboard event instead of mouse event, it causes RTE.

2013-06-20 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-19434:
-

Labels: easytest  (was: )

 When MenuBar is updated with keyboard event instead of mouse event, it causes 
 RTE.
 --

 Key: FLEX-19434
 URL: https://issues.apache.org/jira/browse/FLEX-19434
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: Menu Bar
Affects Versions: Adobe Flex SDK 3.3 (Release)
 Environment: Affected OS(s): All OS Platforms
 Affected OS(s): All OS Platforms
 Language Found: English
Reporter: Adobe JIRA
Priority: Minor
  Labels: easytest

 Steps to reproduce:
 1. Run the attached MenuSample.mxml application
 2. Click on menu2
 3. Use the keyboard down key to subMenu21
 4. Hit Enter
  
  Actual Results:
 Cause null object RTE.
  
  Expected Results:
 No RTE 
  
  Workaround (if any):

--
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-24088) SystemManager RangeError via SystemChildrenList

2013-06-20 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-24088:
-

Labels: easyfix easytest  (was: )

 SystemManager RangeError via SystemChildrenList
 ---

 Key: FLEX-24088
 URL: https://issues.apache.org/jira/browse/FLEX-24088
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: Menu Bar
Affects Versions: Adobe Flex SDK 3.5 (Release)
 Environment: Affected OS(s): All OS Platforms
 Language Found: English
Reporter: Adobe JIRA
  Labels: easyfix, easytest

 Steps to reproduce in SDK 3.5.0.12683: 
 1. Open a panel with a MenuBar instance in a PopUp using 
 PopUpManager.addPopUp(panel, this, false, PopUpManagerChildList.POPUP);
 2. Actuate the menu a few times
 3. Watch the explosion on your console.
  
  Actual Results:
  RangeError: Error #2006: The supplied index is out of bounds.
   at flash.display::DisplayObjectContainer/addChildAt()
   at 
 mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::rawChildren_addChildAt()[C:\autobuild\3.5.0\frameworks\projects\framework\src\mx\managers\SystemManager.as:2179]
   at 
 mx.managers::SystemChildrenList/addChild()[C:\autobuild\3.5.0\frameworks\projects\framework\src\mx\managers\SystemChildrenList.as:111]
   at 
 mx.managers::PopUpManagerImpl/addPopUp()[C:\autobuild\3.5.0\frameworks\projects\framework\src\mx\managers\PopUpManagerImpl.as:309]
   at 
 mx.managers::PopUpManager$/addPopUp()[C:\autobuild\3.5.0\frameworks\projects\framework\src\mx\managers\PopUpManager.as:169]
   at 
 mx.controls::MenuBar/showMenu()[C:\autobuild\3.5.0\frameworks\projects\framework\src\mx\controls\MenuBar.as:1681]
   at 
 mx.controls::MenuBar/mouseDownHandler()[C:\autobuild\3.5.0\frameworks\projects\framework\src\mx\controls\MenuBar.as:1898]
  
  Expected Results:
  No RTE
  
  Workaround (if any):
  There are 3 possible fixes for this bug.  
   1. SystemManager.as - line 1811, the contains() method is excluding 
 children with an index below the current value of the noTopMostIndex 
 property when the popupChildren IChildList's children start at this value.  
 This prevents any interested objects from using the contains() method on the 
 SystemManager to check for popupChildren existence (@see MenuBar.as line 
 1679).
   2. SystemChildrenList.as - line 110 and 121, addChild() and addChildAt() 
 methods fail to check if the DisplayObject being added is already a child of 
 owner before incrementing the upperBoundReference.  This causes subsequent 
 calls to those methods throw a RangeError.
   3. PopupManagerImpl.as - line 307 fails to check whether or not the 
 displayObject being popped up is already a child of the IChildList instance 
 before calling addChild().
 Any of the fixes mentioned above would solve this problem but for brevity, I 
 have attached a monkey patch for the SystemChildrenList.as with the repro 
 project.

--
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-14064) Menu Bar crash

2013-06-20 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-14064:
-

Labels: easytest  (was: )

 Menu Bar crash
 --

 Key: FLEX-14064
 URL: https://issues.apache.org/jira/browse/FLEX-14064
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: Menu Bar
Affects Versions: Adobe Flex SDK Previous
 Environment: Affected OS(s): Windows
 Affected OS(s): Windows XP
 Browser: Firefox 2.x
 Language Found: English
Reporter: Adobe JIRA
  Labels: easytest

 Steps to reproduce:
 1. Create an application with two states, each one containing a menu bar with 
 different number of menus 
 2. Switch programatically between states, or change the menu
 3. Observe results
  
  Actual Results:
  Crash when the number of menus is decreased (menu bar's content changes)
  
  Expected Results:
 Menu Bar change without any crashes
  
  Workaround (if any):
  In MenuBar::styleChanged() call commitProperties() or 
  In the code changing the menu call getMenuAt(0), so MenuBar will refresh 
 correctly it's inner data.

--
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-32728) After selectedIndices was updated, it can not be selected with ShiftKey

2013-06-20 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-32728:
-

Labels: easyfix easytest  (was: )

 After selectedIndices was updated, it can not be selected with ShiftKey
 ---

 Key: FLEX-32728
 URL: https://issues.apache.org/jira/browse/FLEX-32728
 Project: Apache Flex
  Issue Type: Bug
  Components: Advanced Data Grid
Affects Versions: Adobe Flex SDK 3.0 (Release)
 Environment: Affected OS(s): Windows
 Affected OS(s): Windows XP
 Language Found: Japanese
Reporter: Adobe JIRA
Priority: Minor
  Labels: easyfix, easytest

 Steps to reproduce:
 1. run the attached source
 2. click update indices button
 3. click a row with shift-key
  
  Actual Results:
  it can't be selected
  
  Expected Results:
  it should be selected
  
  Workaround (if any):

--
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

2013-06-19 Thread Justin Mclean (JIRA)

[
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] [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 Justin Mclean (JIRA)

[
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

2013-06-19 Thread Justin Mclean (JIRA)

[
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

2013-06-19 Thread Justin Mclean (JIRA)


[ 
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-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 Justin Mclean (JIRA)

[
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.

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

2013-06-19 Thread Justin Mclean (JIRA)


[ 
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

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

2013-06-19 Thread Justin Mclean (JIRA)


[ 
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

2013-06-19 Thread Justin Mclean (JIRA)


 [ 
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

2013-06-19 Thread Justin Mclean (JIRA)


 [ 
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

2013-06-19 Thread Justin Mclean (JIRA)


[ 
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

2013-06-19 Thread Justin Mclean (JIRA)


[ 
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

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

2013-06-19 Thread Justin Mclean (JIRA)

[
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
---

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.

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

2013-06-19 Thread Justin Mclean (JIRA)

[
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.

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

2013-06-19 Thread Justin Mclean (JIRA)


[ 
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-24257) DateField text scrolled when pressing DateField calendar button

2013-06-19 Thread Justin Mclean (JIRA)

[
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.

[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-18 Thread Justin Mclean (JIRA)

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

Justin Mclean commented on FLEX-29002:
--

Any chance you could provide some sample code that demonstrates the issue.

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
---

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] [Reopened] (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 Win

2013-06-18 Thread Justin Mclean (JIRA)

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

Justin Mclean reopened FLEX-29002:
--

Assignee: (was: Carol Frampton)

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
---

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-24257) DateField text scrolled when pressing DateField calendar button

2013-06-18 Thread Justin Mclean (JIRA)

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

Justin Mclean commented on FLEX-24257:
--

Part of the issue is that in the French locale the french locale the default
date format in DD MMM not MM/DD/ like some other locales.

DateField text scrolled when pressing DateField calendar button
---

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

2013-06-18 Thread Justin Mclean (JIRA)

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

Justin Mclean commented on FLEX-24257:
--

Width is calculated in measure via this var bigDate:Date = new Date(2004, 12,
31); it assumes that 31 dec 2004 will always be the widest date which may or
may not be the case.

DateField text scrolled when pressing DateField calendar button
---

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] [Assigned] (FLEX-24257) DateField text scrolled when pressing DateField calendar button

2013-06-18 Thread Justin Mclean (JIRA)

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

Justin Mclean reassigned FLEX-24257:

Assignee: Justin Mclean

DateField text scrolled when pressing DateField calendar button
---

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

2013-06-18 Thread Justin Mclean (JIRA)

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

Justin Mclean commented on FLEX-24257:
--

en_US will give the same width as it uses teh date format MM/DD/ by default
and all months are the same width with 2 digits.

DateField text scrolled when pressing DateField calendar button
---

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] [Comment Edited] (FLEX-24257) DateField text scrolled when pressing DateField calendar button

2013-06-18 Thread Justin Mclean (JIRA)

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

Justin Mclean edited comment on FLEX-24257 at 6/18/13 10:57 AM:

en_US will give the same width as it uses the date format MM/DD/ by default
and all months are the same width with 2 digits.

was (Author: jmclean):
en_US will give the same width as it uses teh date format MM/DD/ by
default and all months are the same width with 2 digits.

DateField text scrolled when pressing DateField calendar button
---

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

2013-06-18 Thread Justin Mclean (JIRA)

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

Justin Mclean commented on FLEX-24257:
--

Fixed and code checked into develop branch.

DateField text scrolled when pressing DateField calendar button
---

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] [Resolved] (FLEX-24257) DateField text scrolled when pressing DateField calendar button

2013-06-18 Thread Justin Mclean (JIRA)

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

Justin Mclean resolved FLEX-24257.
--

Resolution: Fixed
Fix Version/s: Apache Flex 4.10.0

DateField text scrolled when pressing DateField calendar button
---

Attachments: screenshot-1.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

2013-06-18 Thread Justin Mclean (JIRA)

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

Justin Mclean commented on FLEX-24257:
--

Also should of mentioned it's an issue in Apache Flex 4.9.

DateField text scrolled when pressing DateField calendar button
---

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

2013-06-18 Thread Justin Mclean (JIRA)

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

Justin Mclean reopened FLEX-24257:
--

DateField text scrolled when pressing DateField calendar button
---

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-19842) DateField size measured too small

2013-06-18 Thread Justin Mclean (JIRA)

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

Justin Mclean commented on FLEX-19842:
--

Fixed in Apache Flex 4.10

DateField size measured too small
-

Key: FLEX-19842
URL: https://issues.apache.org/jira/browse/FLEX-19842
Project: Apache Flex
Issue Type: Bug
Components: mx: DateField
Affects Versions: Adobe Flex SDK 3.2 (Release)
Environment: Affected OS(s): All OS Platforms
Affected OS(s): All OS Platforms
Language Found: English
Reporter: Adobe JIRA
Assignee: Adobe JIRA
Priority: Minor

DateField.measure() has two problems:
1. It is a few pixels too small, causing the text field inside it to scroll.
To reproduce:
* Create an editable DateField mx:DateField editable=true /.
* Choose a date (say, 01/01/2009).
* Click somewhere else to move the focus out
* Click in the DateField again, at the end (to the right of the 9)
Result: the start of the date scrolls away
Fix: make it 4 pixels wider (in DateField.measure, add an extra +4 to the
measuredMinWidth = measuredWidth = ...
2. It tries to use 31/12/2004 as a sample date to measure the width, but it
does new Date(2004, 12, 31), and months are 0-based there, so it actually
uses 31/01/2005. With a date format where the month can be shown as 1
character, this causes the DateField to be one character too small.
This can be reproduced in Flex 3.2 by having a labelFunction that formats the
date like that, or (didn't test) since SDK-15386 the DateField itself also
supports formatStrings like D/M/YY.
Fix: replace it by new Date(2004, 11, 31)
Workaround for both: override DateField.measure in a subclass, copying the
implementation but adding an extra +4 and fixing the month in the date.

[jira] [Reopened] (FLEX-16716) Confusing behavior when using left/right arrow keys with DateField

2013-06-18 Thread Justin Mclean (JIRA)


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

Justin Mclean reopened FLEX-16716:
--


Still an issue in Apache Flex 4.9/Apache Flex develop branch.

 Confusing behavior when using left/right arrow keys with DateField
 --

 Key: FLEX-16716
 URL: https://issues.apache.org/jira/browse/FLEX-16716
 Project: Apache Flex
  Issue Type: Improvement
  Components: mx: DateField
Affects Versions: Adobe Flex SDK 3.2 (Release)
 Environment: Affected OS(s): All OS Platforms
 Language Found: English
Reporter: Adobe JIRA
Assignee: Adobe JIRA
Priority: Minor

 We'd like you to stop moving both the date itself on a calendar and cursor 
 position on TextField, when left/right arrow key is pressed with DataChooser 
 visible in an editable DateField.
 Description:
 When left/right arrow key is pressed with DataChooser visible in an editable 
 DateField, both of listed below move:
 * date on a calendar
 * cursor position on TextField
 Could you make it, so that only a date on a calendar moves when DataChooser 
 is shown, while only a cursor position on TextField moves when DataChoose is 
 not shown? 
  
 Workarounds: 
 1) derive a new class using DateField
 2) declare two additional variables
 3) overwrite keyDownHandler, keyUpHandler event handlers

--
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-16716) Confusing behavior when using left/right arrow keys with DateField

2013-06-18 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-16716:
-

Assignee: (was: Adobe JIRA)

 Confusing behavior when using left/right arrow keys with DateField
 --

 Key: FLEX-16716
 URL: https://issues.apache.org/jira/browse/FLEX-16716
 Project: Apache Flex
  Issue Type: Improvement
  Components: mx: DateField
Affects Versions: Adobe Flex SDK 3.2 (Release)
 Environment: Affected OS(s): All OS Platforms
 Language Found: English
Reporter: Adobe JIRA
Priority: Minor
  Labels: easyfix

 We'd like you to stop moving both the date itself on a calendar and cursor 
 position on TextField, when left/right arrow key is pressed with DataChooser 
 visible in an editable DateField.
 Description:
 When left/right arrow key is pressed with DataChooser visible in an editable 
 DateField, both of listed below move:
 * date on a calendar
 * cursor position on TextField
 Could you make it, so that only a date on a calendar moves when DataChooser 
 is shown, while only a cursor position on TextField moves when DataChoose is 
 not shown? 
  
 Workarounds: 
 1) derive a new class using DateField
 2) declare two additional variables
 3) overwrite keyDownHandler, keyUpHandler event handlers

--
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-16716) Confusing behavior when using left/right arrow keys with DateField

2013-06-18 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-16716:
-

Labels: easyfix  (was: )

 Confusing behavior when using left/right arrow keys with DateField
 --

 Key: FLEX-16716
 URL: https://issues.apache.org/jira/browse/FLEX-16716
 Project: Apache Flex
  Issue Type: Improvement
  Components: mx: DateField
Affects Versions: Adobe Flex SDK 3.2 (Release)
 Environment: Affected OS(s): All OS Platforms
 Language Found: English
Reporter: Adobe JIRA
Assignee: Adobe JIRA
Priority: Minor
  Labels: easyfix

 We'd like you to stop moving both the date itself on a calendar and cursor 
 position on TextField, when left/right arrow key is pressed with DataChooser 
 visible in an editable DateField.
 Description:
 When left/right arrow key is pressed with DataChooser visible in an editable 
 DateField, both of listed below move:
 * date on a calendar
 * cursor position on TextField
 Could you make it, so that only a date on a calendar moves when DataChooser 
 is shown, while only a cursor position on TextField moves when DataChoose is 
 not shown? 
  
 Workarounds: 
 1) derive a new class using DateField
 2) declare two additional variables
 3) overwrite keyDownHandler, keyUpHandler event handlers

--
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-24671) Allow up/down arrows to change value of a closed datefield control

2013-06-18 Thread Justin Mclean (JIRA)

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

Justin Mclean commented on FLEX-24671:
--

No longer an issue in Apache Flex 4.10.

Allow up/down arrows to change value of a closed datefield control
--

Key: FLEX-24671
URL: https://issues.apache.org/jira/browse/FLEX-24671
Project: Apache Flex
Issue Type: Bug
Components: mx: DateField
Affects Versions: Adobe Flex SDK 4.0 (Release)
Environment: Affected OS(s): Windows
Affected OS(s): Windows
Language Found: English
Reporter: Adobe JIRA
Assignee: Adobe JIRA
Priority: Trivial

Steps to reproduce:
1. Run attached sample.
2. Focus the datefield control.
3. Attempt to use up/down arrows to change the value without opening the
control.

Actual Results:
Nothing happens.

Expected Results:
* If no date is selected, start with today's date on first up or down arrow.
* If a date is selected, move back or forward one day based on which arrow
key was pressed.
* Alternatively, implement more keys for navigating a closed datefield
control. Suggestions: left/right arrows move by day, up/down by week, page
up/down by month, ctrl+page up/down by year (if these do not cause conflicts
with Flash/Flex or the browser).
* Allow automatic movement to a new month/year as necessary in either
direction.
Note: This is being entered with component Accessibility because, at this
time, there are accessibility problems with the control when it it is open.
This change would at least allow simple navigation through dates with
assistive technology.

Workaround (if any):

[jira] [Updated] (FLEX-977) Using arrow keys to navigate DateField always starts on the 2nd of the month

2013-06-18 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-977:
---

Labels: easyfix  (was: )

 Using arrow keys to navigate DateField always starts on the 2nd of the month
 

 Key: FLEX-977
 URL: https://issues.apache.org/jira/browse/FLEX-977
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: DateField
Affects Versions: Adobe Flex SDK Previous
 Environment: Affected OS(s): All OS Platforms
 Affected OS(s): All OS Platforms
 Language Found: English
Reporter: Adobe JIRA
Priority: Minor
  Labels: easyfix
 Fix For: Adobe Flex SDK Previous


 Reproduction:
 1. Compile  run the following:
 ?xml version=1.0 encoding=iso-8859-1?
 mx:Application xmlns:mx=http://www.adobe.com/2006/mxml; width=600 
 height=600
 mx:DateField /
 /mx:Application
 2. Click on the DateField *Notice none of the days have a blue highlight
 3. Hit the right arrow key
 Actual Results:
 The 2nd of the month is now highlighted.
 Expected Results:
 Either the 1st of the month should be highlighted after step 2. or the 1st of 
 the month should be highlighted after hitting the right arrow key.
 Workaround:

--
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] [Reopened] (FLEX-977) Using arrow keys to navigate DateField always starts on the 2nd of the month

2013-06-18 Thread Justin Mclean (JIRA)


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

Justin Mclean reopened FLEX-977:


  Assignee: (was: Adobe JIRA)

Can reproduce in Apache Flex 4.10 develop branch.

 Using arrow keys to navigate DateField always starts on the 2nd of the month
 

 Key: FLEX-977
 URL: https://issues.apache.org/jira/browse/FLEX-977
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: DateField
Affects Versions: Adobe Flex SDK Previous
 Environment: Affected OS(s): All OS Platforms
 Affected OS(s): All OS Platforms
 Language Found: English
Reporter: Adobe JIRA
Priority: Minor
 Fix For: Adobe Flex SDK Previous


 Reproduction:
 1. Compile  run the following:
 ?xml version=1.0 encoding=iso-8859-1?
 mx:Application xmlns:mx=http://www.adobe.com/2006/mxml; width=600 
 height=600
 mx:DateField /
 /mx:Application
 2. Click on the DateField *Notice none of the days have a blue highlight
 3. Hit the right arrow key
 Actual Results:
 The 2nd of the month is now highlighted.
 Expected Results:
 Either the 1st of the month should be highlighted after step 2. or the 1st of 
 the month should be highlighted after hitting the right arrow key.
 Workaround:

--
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-32365) 强制转换类型失败:无法将 1975-09-17 转换为 Date

2013-06-18 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-32365:
-

Labels: easy easytest fix  (was: )

 强制转换类型失败:无法将 1975-09-17 转换为 Date
 --

 Key: FLEX-32365
 URL: https://issues.apache.org/jira/browse/FLEX-32365
 Project: Apache Flex
  Issue Type: Bug
  Components: ADG:Display
Affects Versions: Adobe Flex SDK 3.3 (Release)
 Environment: Affected OS(s): All OS Platforms
 Affected OS(s): All OS Platforms
 Language Found: English
Reporter: Adobe JIRA
Assignee: Adobe JIRA
Priority: Minor
  Labels: easy, easytest, fix

 Steps to reproduce:
 1.formatString -MM-DD
 2. in AdvancedDataGrid
 3.
  
 TypeError: Error #1034: 强制转换类型失败:无法将 1975-09-17 转换为 Date。
   at mx.controls::DateField/set 
 data()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\controls\DateField.as:735]
   at 
 mx.controls::AdvancedDataGridBaseEx/itemEditorItemEditBeginHandler()[C:\Work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\AdvancedDataGridBaseEx.as:6417]
   at flash.events::EventDispatcher/dispatchEventFunction()
   at flash.events::EventDispatcher/dispatchEvent()
   at 
 mx.core::UIComponent/dispatchEvent()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:9051]
   at 
 mx.controls::AdvancedDataGridBaseEx/commitEditedItemPosition()[C:\Work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\AdvancedDataGridBaseEx.as:4463]
   at 
 mx.controls::AdvancedDataGridBaseEx/updateDisplayList()[C:\Work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\AdvancedDataGridBaseEx.as:1807]
   at 
 mx.controls::AdvancedDataGrid/updateDisplayList()[C:\Work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\AdvancedDataGrid.as:5924]
   at 
 mx.controls.listClasses::AdvancedListBase/validateDisplayList()[C:\Work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\listClasses\AdvancedListBase.as:3071]
   at 
 mx.managers::LayoutManager/validateDisplayList()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:602]
   at 
 mx.managers::LayoutManager/doPhasedInstantiation()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:675]
   at Function/http://adobe.com/AS3/2006/builtin::apply()
   at 
 mx.core::UIComponent/callLaterDispatcher2()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:8460]
   at 
 mx.core::UIComponent/callLaterDispatcher()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:8403]

--
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-32365) 强制转换类型失败:无法将 1975-09-17 转换为 Date

2013-06-18 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-32365:
-

Labels: easyfix easytest  (was: easy easytest fix)

 强制转换类型失败:无法将 1975-09-17 转换为 Date
 --

 Key: FLEX-32365
 URL: https://issues.apache.org/jira/browse/FLEX-32365
 Project: Apache Flex
  Issue Type: Bug
  Components: ADG:Display
Affects Versions: Adobe Flex SDK 3.3 (Release)
 Environment: Affected OS(s): All OS Platforms
 Affected OS(s): All OS Platforms
 Language Found: English
Reporter: Adobe JIRA
Assignee: Adobe JIRA
Priority: Minor
  Labels: easyfix, easytest

 Steps to reproduce:
 1.formatString -MM-DD
 2. in AdvancedDataGrid
 3.
  
 TypeError: Error #1034: 强制转换类型失败:无法将 1975-09-17 转换为 Date。
   at mx.controls::DateField/set 
 data()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\controls\DateField.as:735]
   at 
 mx.controls::AdvancedDataGridBaseEx/itemEditorItemEditBeginHandler()[C:\Work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\AdvancedDataGridBaseEx.as:6417]
   at flash.events::EventDispatcher/dispatchEventFunction()
   at flash.events::EventDispatcher/dispatchEvent()
   at 
 mx.core::UIComponent/dispatchEvent()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:9051]
   at 
 mx.controls::AdvancedDataGridBaseEx/commitEditedItemPosition()[C:\Work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\AdvancedDataGridBaseEx.as:4463]
   at 
 mx.controls::AdvancedDataGridBaseEx/updateDisplayList()[C:\Work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\AdvancedDataGridBaseEx.as:1807]
   at 
 mx.controls::AdvancedDataGrid/updateDisplayList()[C:\Work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\AdvancedDataGrid.as:5924]
   at 
 mx.controls.listClasses::AdvancedListBase/validateDisplayList()[C:\Work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\listClasses\AdvancedListBase.as:3071]
   at 
 mx.managers::LayoutManager/validateDisplayList()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:602]
   at 
 mx.managers::LayoutManager/doPhasedInstantiation()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:675]
   at Function/http://adobe.com/AS3/2006/builtin::apply()
   at 
 mx.core::UIComponent/callLaterDispatcher2()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:8460]
   at 
 mx.core::UIComponent/callLaterDispatcher()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:8403]

--
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] [Reopened] (FLEX-32365) 强制转换类型失败:无法将 1975-09-17 转换为 Date

2013-06-18 Thread Justin Mclean (JIRA)


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

Justin Mclean reopened FLEX-32365:
--


May of been fixed in Apache Flex 4.10 develop branch.

 强制转换类型失败:无法将 1975-09-17 转换为 Date
 --

 Key: FLEX-32365
 URL: https://issues.apache.org/jira/browse/FLEX-32365
 Project: Apache Flex
  Issue Type: Bug
  Components: ADG:Display
Affects Versions: Adobe Flex SDK 3.3 (Release)
 Environment: Affected OS(s): All OS Platforms
 Affected OS(s): All OS Platforms
 Language Found: English
Reporter: Adobe JIRA
Assignee: Adobe JIRA
Priority: Minor

 Steps to reproduce:
 1.formatString -MM-DD
 2. in AdvancedDataGrid
 3.
  
 TypeError: Error #1034: 强制转换类型失败:无法将 1975-09-17 转换为 Date。
   at mx.controls::DateField/set 
 data()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\controls\DateField.as:735]
   at 
 mx.controls::AdvancedDataGridBaseEx/itemEditorItemEditBeginHandler()[C:\Work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\AdvancedDataGridBaseEx.as:6417]
   at flash.events::EventDispatcher/dispatchEventFunction()
   at flash.events::EventDispatcher/dispatchEvent()
   at 
 mx.core::UIComponent/dispatchEvent()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:9051]
   at 
 mx.controls::AdvancedDataGridBaseEx/commitEditedItemPosition()[C:\Work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\AdvancedDataGridBaseEx.as:4463]
   at 
 mx.controls::AdvancedDataGridBaseEx/updateDisplayList()[C:\Work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\AdvancedDataGridBaseEx.as:1807]
   at 
 mx.controls::AdvancedDataGrid/updateDisplayList()[C:\Work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\AdvancedDataGrid.as:5924]
   at 
 mx.controls.listClasses::AdvancedListBase/validateDisplayList()[C:\Work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\listClasses\AdvancedListBase.as:3071]
   at 
 mx.managers::LayoutManager/validateDisplayList()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:602]
   at 
 mx.managers::LayoutManager/doPhasedInstantiation()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:675]
   at Function/http://adobe.com/AS3/2006/builtin::apply()
   at 
 mx.core::UIComponent/callLaterDispatcher2()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:8460]
   at 
 mx.core::UIComponent/callLaterDispatcher()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:8403]

--
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-9645) Inconsistancy in date selection with keyboard and mouse. Selection of date is different while using mouse and keyboard.

2013-06-18 Thread Justin Mclean (JIRA)

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

Justin Mclean commented on FLEX-9645:
-

Selection no longer toggles in Apache Flex 4.9 - however same issue exists with
command click.

Inconsistancy in date selection with keyboard and mouse. Selection of date is
different while using mouse and keyboard.
---

Key: FLEX-9645
URL: https://issues.apache.org/jira/browse/FLEX-9645
Project: Apache Flex
Issue Type: Bug
Components: mx: DateField
Affects Versions: Adobe Flex SDK Previous
Environment: Affected OS(s): Windows
Affected OS(s): Windows
Language Found: English
Reporter: Adobe JIRA
Assignee: Adobe JIRA
Priority: Minor
Fix For: Adobe Flex SDK Previous

Reproduction:
1. Run the below sample piece of code.
?xml version=1.0 encoding=iso-8859-1?
mx:Application xmlns:mx=http://www.adobe.com/2006/mxml;
mx:DateField/
mx:DateChooser id=dc/
mx:TextInput text={dc.selectedDate}/
/mx:Application
2. Open the datefield and select the date from the datechooser window,
selected date will be shown in the datefield.
3. Open the datefield again and select the date selected in the previous
step, now the date field will be empty. So the togglling happens when the
same date is selected using mouse.
4. Open the datefield using the keyboard and select a date by hitting enter
key, selected date will be shown in the datefield.
5. Open the datefield again and select the date selected in the previous step
using keyboard.
Notice that the date is still shown in the date field.
Note : This behaviour is seen in dateChooser also.
Actual Results: Inconsistancy in date selection with keyboard and mouse
Expected Results: Should unselect the date when the selected date is selected
again using keyboard.
Workaround: none

[jira] [Reopened] (FLEX-9645) Inconsistancy in date selection with keyboard and mouse. Selection of date is different while using mouse and keyboard.

2013-06-18 Thread Justin Mclean (JIRA)

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

Justin Mclean reopened FLEX-9645:
-

Assignee: (was: Adobe JIRA)

Inconsistancy in date selection with keyboard and mouse. Selection of date is
different while using mouse and keyboard.
---

[jira] [Reopened] (FLEX-16008) Enhance DateFormatter to support custom string like YY Years MM Months DD Days

2013-06-18 Thread Justin Mclean (JIRA)


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

Justin Mclean reopened FLEX-16008:
--

  Assignee: (was: Adobe JIRA)

Still an issue in Apache Flex 4.10 develop branch.

 Enhance DateFormatter to support custom string like YY Years MM Months DD 
 Days
 

 Key: FLEX-16008
 URL: https://issues.apache.org/jira/browse/FLEX-16008
 Project: Apache Flex
  Issue Type: Bug
  Components: Formatters
Affects Versions: Adobe Flex SDK 3.0 (Release)
 Environment: Affected OS(s): All OS Platforms
 Language Found: English
Reporter: Adobe JIRA
Priority: Minor

 Run the following application, Pick a date in the date field, you will see 
 the label output will be something like 08 years 10 months 22 days
 Notice the format string is YY years MM months DD days. However, if we 
 change this to YY Years MM Months DD Days, the dateformatter will fail to 
 output anything.
 ?xml version=1.0 encoding=utf-8?
 !-- Simple example to demonstrate the DateField control. --
 mx:Application xmlns:mx=http://www.adobe.com/2006/mxml;
  
  mx:DateFormatter id=df formatString=YY years MM months DD days/
 mx:Panel title=DateField Control Example height=75% width=75%
 paddingTop=10 paddingLeft=10 paddingRight=10
 mx:Label text=Disable dates on or before June 1, 2006./
 mx:DateField id=dateField2 yearNavigationEnabled=true
 disabledRanges={[ {rangeEnd: new Date(2006, 5, 1)} ]} /
 mx:Label color=blue text=Date selected: 
 {df.format(dateField2.selectedDate)}/
 /mx:Panel
 /mx:Application

--
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-16008) Enhance DateFormatter to support custom string like YY Years MM Months DD Days

2013-06-18 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-16008:
-

Labels: easyfix  (was: )

 Enhance DateFormatter to support custom string like YY Years MM Months DD 
 Days
 

 Key: FLEX-16008
 URL: https://issues.apache.org/jira/browse/FLEX-16008
 Project: Apache Flex
  Issue Type: Bug
  Components: Formatters
Affects Versions: Adobe Flex SDK 3.0 (Release)
 Environment: Affected OS(s): All OS Platforms
 Language Found: English
Reporter: Adobe JIRA
Priority: Minor
  Labels: easyfix

 Run the following application, Pick a date in the date field, you will see 
 the label output will be something like 08 years 10 months 22 days
 Notice the format string is YY years MM months DD days. However, if we 
 change this to YY Years MM Months DD Days, the dateformatter will fail to 
 output anything.
 ?xml version=1.0 encoding=utf-8?
 !-- Simple example to demonstrate the DateField control. --
 mx:Application xmlns:mx=http://www.adobe.com/2006/mxml;
  
  mx:DateFormatter id=df formatString=YY years MM months DD days/
 mx:Panel title=DateField Control Example height=75% width=75%
 paddingTop=10 paddingLeft=10 paddingRight=10
 mx:Label text=Disable dates on or before June 1, 2006./
 mx:DateField id=dateField2 yearNavigationEnabled=true
 disabledRanges={[ {rangeEnd: new Date(2006, 5, 1)} ]} /
 mx:Label color=blue text=Date selected: 
 {df.format(dateField2.selectedDate)}/
 /mx:Panel
 /mx:Application

--
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-19842) DateField size measured too small

2013-06-18 Thread Justin Mclean (JIRA)

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

Justin Mclean resolved FLEX-19842.
--

Resolution: Fixed
Fix Version/s: Apache Flex 4.10.0

DateField size measured too small
-

[jira] [Reopened] (FLEX-19842) DateField size measured too small

2013-06-18 Thread Justin Mclean (JIRA)

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

Justin Mclean reopened FLEX-19842:
--

Assignee: Justin Mclean (was: Adobe JIRA)

DateField size measured too small
-

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

2013-06-18 Thread Justin Mclean (JIRA)

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

Justin Mclean commented on FLEX-24257:
--

On OSX with locale set to fr_FR I get 68 as the maxWidth (for September,
November and December). Values for each month vary form 62 to 68.

DateField text scrolled when pressing DateField calendar button
---

Attachments: screenshot-1.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

2013-06-18 Thread Justin Mclean (JIRA)

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

Justin Mclean commented on FLEX-24257:
--

Issue is with the DateField measure method not TextInput from what I can see.
May be other fixes/changes in ApacheFlex develop branch that are contributing
as there's been quite a few fixes involving dates in the 4.10 branch. You could
try the next build (#100 just about done) from Jenkins to see if it fixes the
issue (https://builds.apache.org/job/flex-sdk/) but it's not actually that hard
to compile the SDK.

DateField text scrolled when pressing DateField calendar button
---

Attachments: screenshot-1.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] [Created] (FLEX-33589) Make installer run on Linux

2013-06-17 Thread Justin Mclean (JIRA)

Justin Mclean created FLEX-33589:


 Summary: Make installer run on Linux
 Key: FLEX-33589
 URL: https://issues.apache.org/jira/browse/FLEX-33589
 Project: Apache Flex
  Issue Type: Sub-task
Reporter: Justin Mclean




--
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-33589) Make installer run on Linux

2013-06-17 Thread Justin Mclean (JIRA)


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

Justin Mclean commented on FLEX-33589:
--

Build script changed to work on Linux.

Need to change deb package to be more informative (by adding description and 
screen shot) and improve installation experience. Need to try and remove This 
package is of poor quality message.

 Make installer run on Linux
 ---

 Key: FLEX-33589
 URL: https://issues.apache.org/jira/browse/FLEX-33589
 Project: Apache Flex
  Issue Type: Sub-task
Reporter: Justin Mclean



--
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-33587) Web FTP connection issue

2013-06-13 Thread Justin Mclean (JIRA)


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

Justin Mclean commented on FLEX-33587:
--

Try using passive FTP (as opposed to active) if you can that may solve the 
issue.

 Web FTP connection issue
 

 Key: FLEX-33587
 URL: https://issues.apache.org/jira/browse/FLEX-33587
 Project: Apache Flex
  Issue Type: Bug
Affects Versions: Adobe Flex SDK 4.0 (Release)
 Environment: Window 7 (64 bit)
Reporter: Bharat
Assignee: Alex Harui
  Labels: as, flex, flex4.0, socket
 Fix For: Adobe Flex SDK 4.0 (Release)

   Original Estimate: 12h
  Remaining Estimate: 12h

 I am creating an web ftp example using flex 4.0, when i run the application 
 from development environment (from flex) its connecting ftp server perfectly 
 and working fine. But when trying to connect FTP server from release build 
 version of application. Its not working.
  
 What could be the possible reason to stop connecting FTP server from flex web 
 ftp request?
  
 On FTP connection request receive error:
  
 Command socket error: [SecurityErrorEvent type=securityError bubbles=false 
 cancelable=false eventPhase=2 text=Error #2048: Security sandbox violation: 
 http://localhost/YemoWebFTP/WebFTP.swf cannot load data from 10.0.2.197:21]
  
 Also using crossdomain.xml as follow:
  
 ?xml version=1.0?
 !DOCTYPE cross-domain-policy SYSTEM /xml/dtds/cross-domain-policy.dtd
 !-- Policy file for xmlsocket://socks.example.com --
 cross-domain-policy  
  
site-control permitted-cross-domain-policies=all/ 
  
!-- Instead of setting to-ports=*,administrators can use ranges and 
 commas --
 allow-access-from domain=* secure=true to-ports=21,80, 843, 
 1024-3000 /
  
   allow-http-request-headers-from domain=* headers=*/
  
 /cross-domain-policy
  
  
 And from application before connection request to FTP server
  
 Security.loadPolicyFile(http://10.0.2.197/crossdomain.xml;);
  
 Additionaly, also tried:
  
 Security.allowDomain(*);
 Security.loadPolicyFile(xmlsocket://10.0.2.197); 
  
 Thanks in advance.
  
 Bharat

--
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-13423) DateChooser selectedRanges gives selectedRange start+1 day [if selectedRanges.rangeStart is same as selectableRange.rangeStart]

2013-06-10 Thread Justin Mclean (JIRA)


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

Justin Mclean resolved FLEX-13423.
--

Resolution: Fixed

Can't reproduce issue as described but fix 2 other minor issues and checked 
into develop branch.
1. RTE when control click removes first selection of many.
2. Shift selecting multiple days and then control clicking multiple days out of 
the middle of the selection would sometime give incorrect election.

 DateChooser selectedRanges gives selectedRange start+1 day [if 
 selectedRanges.rangeStart is same as selectableRange.rangeStart]
 ---

 Key: FLEX-13423
 URL: https://issues.apache.org/jira/browse/FLEX-13423
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: DateChooser
Affects Versions: Adobe Flex SDK Previous
 Environment: Affected OS(s): Windows
 Affected OS(s): Windows XP
 Language Found: English
Reporter: Adobe JIRA
Assignee: Justin Mclean
Priority: Minor
  Labels: easyfix, easytest
 Fix For: Apache Flex 4.10.0


   Steps to reproduce:
 1. Compile and run the below sample piece of code
 ?xml version=1.0 encoding=iso-8859-1? 
 mx:Application xmlns:mx=http://www.adobe.com/2006/mxml;
   mx:DateChooser id=dc selectableRange={{rangeStart: new 
 Date(2007,11,11), rangeEnd: new Date(2007,11,19)}} 
 allowMultipleSelection=true /
   mx:Button label=Selected Range click=run()/
   mx:Script
   ![CDATA[
   public function run():void{
   for(var 
 i:int=0;idc.selectedRanges.length;i++)
   {
   
 trace(dc.selectedRanges[i].rangeStart);
   
 trace(dc.selectedRanges[i].rangeEnd);
   }
   }
   ]]
   
   /mx:Script
 /mx:Application
 2. Notice that selectable range is in between 11-December to 19-December
 3. Select all the dates 
 4. Click on the button 'Selected Range'. Notice that in the trace selected 
 range start shows 12-December.
  Actual Results: DateChooser selectedRanges gives selectedRange start+1 day.
  
  
  Expected Results: selectedRange start date should be 11-December.
  
  
  Workaround (if any): none
 

--
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-13423) DateChooser selectedRanges gives selectedRange start+1 day [if selectedRanges.rangeStart is same as selectableRange.rangeStart]

2013-06-09 Thread Justin Mclean (JIRA)


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

Justin Mclean commented on FLEX-13423:
--

Unable to reproduce in develop branch. Can you describe the steps to reproduce 
it with this code?


?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

s:layout
s:VerticalLayout /
/s:layout

fx:Script
![CDATA[
import mx.events.CalendarLayoutChangeEvent;

protected function 
changed(event:CalendarLayoutChangeEvent):void
{
var length:int = dc.selectedRanges.length;
var selected:String = ;

for (var i:int; i  length; i++) {
selected +=   + 
dc.selectedRanges[i].rangeStart +  -  + dc.selectedRanges[i].rangeEnd;
}

l.text = selected;
}

]]
/fx:Script
mx:DateChooser id=dc change=changed(event) 
allowMultipleSelection=true /

s:Label id=l /

/s:Application

As far a sI can see removeRangeFromSelection doesn't contain code above.

mx_internal function removeRangeFromSelection(startDate:Date, 
endDate:Date):void
{
var rangeEnd:Date;
var rangeStart:Date;

if (endDate  startDate)
return;

for (var n:int = 0; n  selectedRangeCount; n++)
{
rangeStart = _selectedRanges[n].rangeStart;
rangeEnd = _selectedRanges[n].rangeEnd;

// ignore selection range outsie of date range
if (endDate  rangeStart || startDate  rangeEnd)
continue;

// remove selection range inside of date range
if (startDate = rangeStart  endDate = rangeEnd)
{
_selectedRanges[n] = null;
}
// split selection range if date range inside selection 
range
else if (startDate  rangeStart  endDate  rangeEnd)
{
var temp:Date = _selectedRanges[n].rangeEnd;

_selectedRanges[n].rangeEnd = 
addSubtractDays(startDate, -1);

_selectedRanges[selectedRangeCount] = {};
_selectedRanges[selectedRangeCount].rangeStart 
= addSubtractDays(endDate, +1);
_selectedRanges[selectedRangeCount].rangeEnd = 
temp;

selectedRangeCount++;
}
// move selection start date if end overlaps
else if (endDate = rangeStart)
{
_selectedRanges[n].rangeStart = 
addSubtractDays(endDate, +1);   
}
// move selection end date if start overlaps
else if (startDate = rangeEnd)
{
_selectedRanges[n].rangeEnd = 
addSubtractDays(startDate, -1);   
}   
}

// clean up any removed selections
for (n = selectedRangeCount -1; n  0; n--)
{
if (_selectedRanges[n] == null)
{
_selectedRanges.splice(n,1);
selectedRangeCount--;
}
}
}


 DateChooser selectedRanges gives selectedRange start+1 day [if 
 selectedRanges.rangeStart is same as selectableRange.rangeStart]
 ---

 Key: FLEX-13423
 URL: https://issues.apache.org/jira/browse/FLEX-13423
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: DateChooser
Affects Versions: Adobe Flex SDK Previous

[jira] [Reopened] (FLEX-13423) DateChooser selectedRanges gives selectedRange start+1 day [if selectedRanges.rangeStart is same as selectableRange.rangeStart]

2013-06-07 Thread Justin Mclean (JIRA)


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

Justin Mclean reopened FLEX-13423:
--

  Assignee: Justin Mclean

 DateChooser selectedRanges gives selectedRange start+1 day [if 
 selectedRanges.rangeStart is same as selectableRange.rangeStart]
 ---

 Key: FLEX-13423
 URL: https://issues.apache.org/jira/browse/FLEX-13423
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: DateChooser
Affects Versions: Adobe Flex SDK Previous
 Environment: Affected OS(s): Windows
 Affected OS(s): Windows XP
 Language Found: English
Reporter: Adobe JIRA
Assignee: Justin Mclean
Priority: Minor
  Labels: easyfix, easytest
 Fix For: Apache Flex 4.10.0


   Steps to reproduce:
 1. Compile and run the below sample piece of code
 ?xml version=1.0 encoding=iso-8859-1? 
 mx:Application xmlns:mx=http://www.adobe.com/2006/mxml;
   mx:DateChooser id=dc selectableRange={{rangeStart: new 
 Date(2007,11,11), rangeEnd: new Date(2007,11,19)}} 
 allowMultipleSelection=true /
   mx:Button label=Selected Range click=run()/
   mx:Script
   ![CDATA[
   public function run():void{
   for(var 
 i:int=0;idc.selectedRanges.length;i++)
   {
   
 trace(dc.selectedRanges[i].rangeStart);
   
 trace(dc.selectedRanges[i].rangeEnd);
   }
   }
   ]]
   
   /mx:Script
 /mx:Application
 2. Notice that selectable range is in between 11-December to 19-December
 3. Select all the dates 
 4. Click on the button 'Selected Range'. Notice that in the trace selected 
 range start shows 12-December.
  Actual Results: DateChooser selectedRanges gives selectedRange start+1 day.
  
  
  Expected Results: selectedRange start date should be 11-December.
  
  
  Workaround (if any): none
 

--
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-33083) Flash builder report An internal build error has occurred. See the error log for more information.

2013-06-06 Thread Justin Mclean (JIRA)


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

Justin Mclean commented on FLEX-33083:
--

Changed license message to be more generic and checked into develop. Need other 
language translations.

 Flash builder report An internal build error has occurred. See the error log 
 for more information. 
 -

 Key: FLEX-33083
 URL: https://issues.apache.org/jira/browse/FLEX-33083
 Project: Apache Flex
  Issue Type: Bug
  Components: Project Management
 Environment: Flash builder 4.6  , sdk 4.8.0  
Reporter: Alex Harui
Assignee: Alex Harui
  Labels: easyfix
 Attachments: flex installer change.png, mxmlc.jar, swfutils.jar, 
 weborb.codegen.test.zip


 1. download the source kit from 
 https://svn.apache.org/repos/asf/incubator/flex/trunk
 2. run ant release 
 3. extract apache-flex-sdk-4.8.0-incubating-bin.zip to new folder 
 4. extract AIR Integration Kit.zip to folder 
 5 copy additional files for Flash Ide ( frameworks/libs\player\* and 
 frameworks\*-config.xm)
 6.create a simple project with reference to RemoteObject  
 private var remote:RemoteObject;
 remote = new RemoteObject;
 flash builder log file :
 !ENTRY com.adobe.flexbuilder.project 4 43 2012-06-08 18:27:39.112
 !MESSAGE Uncaught exception in compiler
 !STACK 0
 java.lang.NullPointerException
   at flex2.compiler.CompilerAPI.getMessagingClasses(CompilerAPI.java:1730)
   at flex2.compiler.CompilerAPI.compile(CompilerAPI.java:1538)
   at flex2.tools.oem.Application.compile(Application.java:1357)
   at flex2.tools.oem.Application.recompile(Application.java:1295)
   at flex2.tools.oem.Application.compile(Application.java:894)
   at 
 flex2.tools.flexbuilder.BuilderApplication.compile(BuilderApplication.java:367)
   at 
 com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder$MyBuilder.mybuild(ASApplicationBuilder.java:319)
   at 
 com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.build(ASApplicationBuilder.java:129)
   at 
 com.adobe.flexbuilder.multisdk.compiler.internal.ASBuilder.build(ASBuilder.java:198)
   at 
 com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.build(ASItemBuilder.java:70)
   at 
 com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.buildItem(FlexProjectBuilder.java:607)
   at 
 com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.build(FlexProjectBuilder.java:382)
   at 
 com.adobe.flexbuilder.project.compiler.internal.FlexIncrementalBuilder.build(FlexIncrementalBuilder.java:187)
   at 
 org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
   at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
   at 
 org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
   at 
 org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
   at 
 org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
   at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
   at 
 org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
   at 
 org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
   at 
 org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
   at 
 org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
   at 
 org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
   at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

--
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-33583) Context3D::setSamplerStateAt parameters missing in API

2013-06-05 Thread Justin Mclean (JIRA)


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

Justin Mclean resolved FLEX-33583.
--

Resolution: Won't Fix

Sorry but this is a Flash Player issue not an Apache Flex SDK issue and we are 
unable to fix it. Please report the bug in Adobe bug base at 
https://bugbase.adobe.com

 Context3D::setSamplerStateAt parameters missing in API
 --

 Key: FLEX-33583
 URL: https://issues.apache.org/jira/browse/FLEX-33583
 Project: Apache Flex
  Issue Type: Bug
  Components: 3D Support
Affects Versions: Adobe Flex SDK 4.6 (Release)
 Environment: All environments
Reporter: Gary Paluk
  Labels: api-change, incomplete, sampler, states
 Fix For: Adobe Flex SDK 4.6 (Release)


 Their are missing parameters Context3D::setSamplerStateAt API
 When looking at the general parameters sent as sampler state using AGAL, you 
 will notice 5 possible parameters that define the state.
 cube,linear,mipnearest,clamp,dxt1
 The current setSamplerStateAt() API signature is as follows:
 public function setSamplerStateAt(sampler:int, wrap:String, filter:String, 
 mipfilter:String):void
 Without all of the necessary state parameters, it deems the functionality as 
 incomplete and unable to perform required functions needed to decouple and 
 manage sampler state at runtime. Having this functionality would be in line 
 with standard practices and provide the ability to reuse shaders for 
 different texture types and allow for samplers to be derived after the the 
 texture type has been derived, both of which are assumed fundamental to 
 sampler state management.

--
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-33529) Change build scripts to create Linux source and release packages

2013-06-05 Thread Justin Mclean (JIRA)


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

Justin Mclean commented on FLEX-33529:
--

Flash Player error causes checkin tests to fail. Tests run correctly.  

  [mxmlc] 
/home/justinmclean/sdk/frameworks/tests/basicTests/spark/views/HelloWorld.swf 
(60848 bytes)
 [echo] launching player and swf
 [exec] 
 [exec] (flashplayerdebugger:4046): GLib-GObject-WARNING **: instance of 
invalid non-instantiatable type `(null)'
 [exec] 
 [exec] (flashplayerdebugger:4046): GLib-GObject-CRITICAL **: 
g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE 
(instance)' failed

Changing failonerorr to be false in build file gets around this error:
echo message=launching player and swf/
exec executable=${flash.player} dir=${basedir}/frameworks 
failonerror=false
arg value=${basedir}/frameworks/tests/basicTests/BasicTests.swf/
/exec
!-- halt if there was an error --
antcall target=mustellaresultsparser/



 Change build scripts to create Linux source and release packages
 

 Key: FLEX-33529
 URL: https://issues.apache.org/jira/browse/FLEX-33529
 Project: Apache Flex
  Issue Type: Sub-task
Reporter: Justin Mclean
 Attachments: pb.tar.gz




--
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-14181) DividedBox call to getDividerAt(num) encounters null reference when no dividers are present

2013-06-05 Thread Justin Mclean (JIRA)


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

Justin Mclean resolved FLEX-14181.
--

   Resolution: Fixed
Fix Version/s: Apache Flex 4.10.0

Fixed and checked into develop branch.

 DividedBox call to getDividerAt(num) encounters null reference when no 
 dividers are present
 ---

 Key: FLEX-14181
 URL: https://issues.apache.org/jira/browse/FLEX-14181
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: DividedBox
Affects Versions: Adobe Flex SDK 3.0 (Release)
 Environment: Affected OS(s): Windows
 Affected OS(s): Windows XP
 Browser: Firefox 2.x
 Language Found: English
Reporter: Adobe JIRA
  Labels: easyfix, easytest
 Fix For: Apache Flex 4.10.0


 What I am doing is programatically adding items to an HDividedBox.  There may 
 or may not be any components added to the dividerbox.  Then later when I make 
 a call to getDividerAt(i) I get the exception.  I believe the member 
 dividedLayer of DividedBox is null since nothing was added to it.
 Steps to reproduce:
 1. Create a DividedBox, or in my case an HDividedBox
 2. Make a call to the divider.getDividerAt(some number) 
 3. It blows up with a null reference.  The null reference actually being the 
 dividerLayer. 
  
  Actual Results:
  TypeError: Error #1009: Cannot access a property or method of a null object 
 reference.
   at 
 mx.containers::DividedBox/getDividerAt()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\containers\DividedBox.as:697]
   at 
 components::DataContainer/commitProperties()[C:\development\workspace\Components\src\components\DataContainerHelper.as:111]
   at 
 mx.core::UIComponent/validateProperties()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:5670]
   at 
 mx.managers::LayoutManager/validateProperties()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:519]
   at 
 mx.managers::LayoutManager/doPhasedInstantiation()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:639]
   at Function/http://adobe.com/AS3/2006/builtin::apply()
   at 
 mx.core::UIComponent/callLaterDispatcher2()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:8460]
   at 
 mx.core::UIComponent/callLaterDispatcher()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:8403]
  
  Expected Results:
  I would expect to get a null value returned to me if either there was no 
 dividerLayer or the item at the index was null.
  
  Workaround (if any):
  From what I can tell there is no getDividerCount method to check before 
 making the call.

--
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-14181) DividedBox call to getDividerAt(num) encounters null reference when no dividers are present

2013-06-05 Thread Justin Mclean (JIRA)


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

Justin Mclean commented on FLEX-14181:
--

Code to reproduce.

?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 
initialize=init(event)
fx:Script
![CDATA[
import mx.containers.HBox;
import mx.containers.HDividedBox;
import mx.events.FlexEvent;

protected function init(event:FlexEvent):void
{
var box:HDividedBox = new HDividedBox();
box.addChild(new HBox());
box.addChild(new HBox());
box.addChild(new HBox());
var divider:Object = box.getDividerAt(10);
}
]]
/fx:Script

/s:Application


 DividedBox call to getDividerAt(num) encounters null reference when no 
 dividers are present
 ---

 Key: FLEX-14181
 URL: https://issues.apache.org/jira/browse/FLEX-14181
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: DividedBox
Affects Versions: Adobe Flex SDK 3.0 (Release)
 Environment: Affected OS(s): Windows
 Affected OS(s): Windows XP
 Browser: Firefox 2.x
 Language Found: English
Reporter: Adobe JIRA
  Labels: easyfix, easytest

 What I am doing is programatically adding items to an HDividedBox.  There may 
 or may not be any components added to the dividerbox.  Then later when I make 
 a call to getDividerAt(i) I get the exception.  I believe the member 
 dividedLayer of DividedBox is null since nothing was added to it.
 Steps to reproduce:
 1. Create a DividedBox, or in my case an HDividedBox
 2. Make a call to the divider.getDividerAt(some number) 
 3. It blows up with a null reference.  The null reference actually being the 
 dividerLayer. 
  
  Actual Results:
  TypeError: Error #1009: Cannot access a property or method of a null object 
 reference.
   at 
 mx.containers::DividedBox/getDividerAt()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\containers\DividedBox.as:697]
   at 
 components::DataContainer/commitProperties()[C:\development\workspace\Components\src\components\DataContainerHelper.as:111]
   at 
 mx.core::UIComponent/validateProperties()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:5670]
   at 
 mx.managers::LayoutManager/validateProperties()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:519]
   at 
 mx.managers::LayoutManager/doPhasedInstantiation()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:639]
   at Function/http://adobe.com/AS3/2006/builtin::apply()
   at 
 mx.core::UIComponent/callLaterDispatcher2()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:8460]
   at 
 mx.core::UIComponent/callLaterDispatcher()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:8403]
  
  Expected Results:
  I would expect to get a null value returned to me if either there was no 
 dividerLayer or the item at the index was null.
  
  Workaround (if any):
  From what I can tell there is no getDividerCount method to check before 
 making the call.

--
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-11930) Inproper condition for IF statement

2013-06-05 Thread Justin Mclean (JIRA)


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

Justin Mclean resolved FLEX-11930.
--

   Resolution: Fixed
Fix Version/s: Apache Flex 4.10.0

Fixed and checked into develop branch.

 Inproper condition for IF statement
 ---

 Key: FLEX-11930
 URL: https://issues.apache.org/jira/browse/FLEX-11930
 Project: Apache Flex
  Issue Type: Bug
  Components: .Unspecified - Framework
Affects Versions: Adobe Flex SDK 3.0 (Release)
 Environment: Affected OS(s): All OS Platforms
 Language Found: English
Reporter: Adobe JIRA
  Labels: easytest
 Fix For: Apache Flex 4.10.0


 In file mx.containers.utilityClasses.CanvasLayout.as, the condition for an IF 
 statement is identical to its ELSE IF statement.  This causes the ELSE IF 
 block can never be executed.
 private function applyAnchorStylesDuringUpdateDisplayList(
availableWidth:Number,
availableHeight:Number,
child:IUIComponent = null):void
 { 
 ...
   if (!parentBoundariesLR)
  {
  ...
   }
   else if (!parentBoundariesLR)
  {
//The left, right or horizontalCenter style has been set to
//a non-parent region, but no columns were declared 
message = resourceManager.getString(
 containers, noColumnsFound);
throw new ConstraintError(message);
   }
  
  ...
 }

--
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-28976) Placing list item renderers on certain negative z coordinates results in a Flash Player crash.

2013-06-05 Thread Justin Mclean (JIRA)

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

Justin Mclean updated FLEX-28976:
-

Labels: easytest (was: )

Placing list item renderers on certain negative z coordinates results in a
Flash Player crash.
--

Key: FLEX-28976
URL: https://issues.apache.org/jira/browse/FLEX-28976
Project: Apache Flex
Issue Type: Bug
Components: 3D Support
Affects Versions: Adobe Flex SDK 4.5.1 (Release)
Environment: Affected OS(s): Windows
Affected OS(s): Windows 7
Browser: Firefox 3.x
Language Found: English
Reporter: Adobe JIRA
Labels: easytest

The issue is related to applying custom 3d layouts on a Spark list. If the
layout sets a negative z coordinate to a list item, FP crashes. The crash
occurs only for certain coordinates that appear to be related to the
perspective projection's focal length. E.g. for a focal length of 480, if z
coordinate = -457, app crashes, otherwise not. Another example is for focal
length of 200 and a limit of -190 on z.
Note that the crash only occurs when setting the layout on a Spark list with
an item renderer containing an Image control(Spark or MX; a simple Spark
BitmapImage doesn't seem to trigger the crash).
Also, the crash occurs only on machines that have fp 11.1.102.55 installed
(Chrome, Firefox, IE9, release and debugger). On 11.0.1.152 and previous
versions, the crash doesn't happen. The app was compiled with
playerglobal.swc for both 10.3 and 11, with the same results.
I've attached a simple test case that illustrates this behavior.

[jira] [Updated] (FLEX-18795) Improper Measuring in (at least) Button

2013-06-05 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-18795:
-

Labels: easytest  (was: )

 Improper Measuring in (at least) Button
 ---

 Key: FLEX-18795
 URL: https://issues.apache.org/jira/browse/FLEX-18795
 Project: Apache Flex
  Issue Type: Bug
  Components: Layout - General
Affects Versions: Adobe Flex SDK Previous
 Environment: Affected OS(s): All OS Platforms
 Affected OS(s): All OS Platforms
 Language Found: English
Reporter: Adobe JIRA
  Labels: easytest

 Steps to reproduce:
 1. Make container scaleX = .7 and scaleY = .7
 2. Button Width to 300 
 3. Button Height to 25
 4. Button Font Size 18 
 5. Button Label to Label
  
  Actual Results:
 Label gets cut off with a ...
  
  
  Expected Results:
  
 See the full label
  
  Workaround (if any):
  
  None that I can find, any would be appreciated!!

--
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-22912) test attachments

2013-06-05 Thread Justin Mclean (JIRA)


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

Justin Mclean resolved FLEX-22912.
--

Resolution: Incomplete

 test attachments
 

 Key: FLEX-22912
 URL: https://issues.apache.org/jira/browse/FLEX-22912
 Project: Apache Flex
  Issue Type: Bug
  Components: Legacy/Deprecated
Affects Versions: Adobe Flex SDK Previous
 Environment: Affected OS(s): All OS Platforms
 Language Found: English
Reporter: Adobe JIRA

 Steps to reproduce:
 1.
 2.
 3.
  
  Actual Results:
  
  
  Expected Results:
  
  
  Workaround (if any):

--
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-20953) Test Bug for BugQuash jira integration. Just Ignore

2013-06-05 Thread Justin Mclean (JIRA)


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

Justin Mclean resolved FLEX-20953.
--

Resolution: Invalid

 Test Bug for BugQuash jira integration. Just Ignore
 ---

 Key: FLEX-20953
 URL: https://issues.apache.org/jira/browse/FLEX-20953
 Project: Apache Flex
  Issue Type: Improvement
  Components: mx: Application
Affects Versions: Adobe Flex SDK Previous
 Environment: Language Found: English
Reporter: Adobe JIRA

 Test Issue

--
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-16069) Scroller stepSize is not updated when Scroller and viewport are changed

2013-06-05 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-16069:
-

Labels: easyfix easytest  (was: )

 Scroller stepSize is not updated when Scroller and viewport are changed
 ---

 Key: FLEX-16069
 URL: https://issues.apache.org/jira/browse/FLEX-16069
 Project: Apache Flex
  Issue Type: Bug
  Components: Spark: Scroller
Affects Versions: Adobe Flex SDK Previous
 Environment: Affected OS(s): All OS Platforms
 Language Found: English
Reporter: Adobe JIRA
Assignee: Adobe JIRA
Priority: Minor
  Labels: easyfix, easytest

 Steps to reproduce:
 1. Run atached file
 2. Click Tab to focus on the Scroller
 3. Click DOWN Key. 
  
  Actual Results:
  Click StepSize button to see stepSize=1
  Click Value button to see value=200
  Expected Results:
  I believe stepSize should be updated to 200.
 Current behavior is inconsistent between calling step() function and clicking 
 down key
  
  Workaround (if any):

--
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] [Reopened] (FLEX-16069) Scroller stepSize is not updated when Scroller and viewport are changed

2013-06-05 Thread Justin Mclean (JIRA)


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

Justin Mclean reopened FLEX-16069:
--


Still an issue.

 Scroller stepSize is not updated when Scroller and viewport are changed
 ---

 Key: FLEX-16069
 URL: https://issues.apache.org/jira/browse/FLEX-16069
 Project: Apache Flex
  Issue Type: Bug
  Components: Spark: Scroller
Affects Versions: Adobe Flex SDK Previous
 Environment: Affected OS(s): All OS Platforms
 Language Found: English
Reporter: Adobe JIRA
Assignee: Adobe JIRA
Priority: Minor

 Steps to reproduce:
 1. Run atached file
 2. Click Tab to focus on the Scroller
 3. Click DOWN Key. 
  
  Actual Results:
  Click StepSize button to see stepSize=1
  Click Value button to see value=200
  Expected Results:
  I believe stepSize should be updated to 200.
 Current behavior is inconsistent between calling step() function and clicking 
 down key
  
  Workaround (if any):

--
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-13030) Vertical Scroll Size should default to ~25 pixels to match HTML browser scroll size

2013-06-05 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-13030:
-

Labels: easyfix easytest  (was: )

 Vertical Scroll Size should default to ~25 pixels to match HTML browser 
 scroll size
 ---

 Key: FLEX-13030
 URL: https://issues.apache.org/jira/browse/FLEX-13030
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: Application
Affects Versions: Adobe Flex SDK Previous
 Environment: Affected OS(s): Windows
 Affected OS(s): Windows XP
 Language Found: English
Reporter: Adobe JIRA
  Labels: easyfix, easytest

 A Flex app feels sort of sluggish when using the scroll arrows. Setting the 
 verticalScrollSize to 25 makes it more responsive and matches the default 
 scroll size in the browser. 
 Steps to reproduce:
 1.
 2.
 3.
  
  Actual Results:
  
  
  Expected Results:
  
  
  Workaround (if any):

--
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-21915) horizontalAlign and verticalAlign Layout problem

2013-06-05 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-21915:
-

Labels: easyfix easytest  (was: )

 horizontalAlign and verticalAlign Layout problem
 

 Key: FLEX-21915
 URL: https://issues.apache.org/jira/browse/FLEX-21915
 Project: Apache Flex
  Issue Type: Bug
  Components: mx: Box View
Affects Versions: Adobe Flex SDK 3.0 (Release)
 Environment: Affected OS(s): All OS Platforms
 Affected OS(s): All OS Platforms
 Language Found: English
Reporter: Adobe JIRA
Priority: Minor
  Labels: easyfix, easytest

 Steps to reproduce:
 1. Create a HBox or VBox with border style solid, borderThickness 2, 
 borderColor red, horizontal Align right, and width and height to 100.
 2. Then add a button having more that parent(HBox, VBox) width.
 3. Use the following code for the same.
  mx:VBox width=100 height=100 borderColor=red id=nnk1 
 paddingTop=10 
   borderStyle=solid borderThickness=2 
 horizontalAlign=right verticalAlign=middle
   mx:Button label=nitin/
   mx:Button label=kalaskar click=nnk.width=100 width=150/
  /mx:VBox
  
  Actual Results:
  Scroll bars not appearing and partial button is displayed..
  
  Expected Results:
 Scroll bars should appear with paddingLeft, and paddingRight
  
  Workaround (if any):
 Check mx.containers.utilityClasses.BoxLayout updateDisplayList function.

--
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-14805) When compiling on a shared environment (Linux), a common directory, /tmp/Adobe, is created which causes compilation conflicts and permission issues.

2013-06-05 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-14805:
-

Labels: easyfix easytest  (was: )

 When compiling on a shared environment (Linux), a  common directory, 
 /tmp/Adobe, is created which causes compilation conflicts  and permission 
 issues.
 --

 Key: FLEX-14805
 URL: https://issues.apache.org/jira/browse/FLEX-14805
 Project: Apache Flex
  Issue Type: Bug
  Components: .Unspecified - Compiler, Runtime Localization
Affects Versions: Adobe Flex SDK 3.0 (Release)
 Environment: Affected OS(s): Linux
 Affected OS(s): Linux RedHat
 Language Found: English
Reporter: Adobe JIRA
  Labels: easyfix, easytest

 Steps to reproduce:
 Some Java class file involved in the generation of a dynamic resource bundle 
 SFW file creates this directory:
  
 /tmp/Adobe/Flex/GeneratedResourceModules
  
 It places some temporary files in that directory and then deletes when the 
 SWF is generated.
 here is a sample of the compile command:
  
 /bin/mxmlc -locale=en_US 
  -source-path=MY_SOURCE_DIR/rss_showviewer/resources/en_US 
  
 -include-resource-bundles=collections,containers,controls,core,effects,resources,skins,styles
  
  
 -output=MY_HOME_DIR/app/resources/en_US/showViewerResources_en_US.swf 
  
  Actual Results:
 The actual directory does NOT get deleted.   The owner of the directory is 
 the Linux user account who started the resource SWF compile.  No other users 
 have write permissions to that directory.  As a result, another user who then 
 attempts to compile the SWFs will get some java Null Pointer exception 
 stemming from the fact that the compiler was unable to create a file in that 
 directory.
  
  Expected Results:
 The directory should get deleted. 
  
  Workaround (if any):
  The workaround is to manually delete the directory or grant the necessary 
 read and write permissions to the appropriate user accounts.

--
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-28668) ViewStack with one NavigatorContent RTEs when the NavigatorContent is removed.

2013-06-05 Thread Justin Mclean (JIRA)


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

Justin Mclean resolved FLEX-28668.
--

Resolution: Cannot Reproduce

Probably fixed in earlier version of SDK.

 ViewStack with one NavigatorContent RTEs when the NavigatorContent is removed.
 --

 Key: FLEX-28668
 URL: https://issues.apache.org/jira/browse/FLEX-28668
 Project: Apache Flex
  Issue Type: Bug
  Components: Spark: ViewStack
Affects Versions: Adobe Flex SDK Next
 Environment: Affected OS(s): All OS Platforms
 Affected OS(s): All OS Platforms
 Language Found: English
Reporter: Adobe JIRA
  Labels: easytest

   I found this bug while fixing another one. I confirmed that this is not 
 a regression.
 Steps to reproduce:
 Run this code:
 ?xml version=1.0 encoding=utf-8?
 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
minWidth=955 minHeight=600
backgroundColor=#FF
 fx:Script
 ![CDATA[
 import spark.layouts.supportClasses.LayoutBase;
 
 public function removeElementAtHandler():void
 {
 mainViewStack.removeElementAt(0);
 }
 ]]
   
 /fx:Script
 
 s:layout
 s:VerticalLayout/
 /s:layout
 
 s:Button id=btn1 label=removeElementAt 
 click=removeElementAtHandler()/
 
 s:ViewStack id=mainViewStack
 s:NavigatorContent id=view1 label=View 1
 s:TextInput text=view1 width=60 /
 /s:NavigatorContent
 /s:ViewStack
 /s:WindowedApplication
  
  Actual Results:
 RTE:
 RangeError: Index 0 is out of range.
   at 
 spark.components::Group/checkForRangeError()[/Users/mvujovic/Documents/FlexSources/trunk6/frameworks/projects/spark/src/spark/components/Group.as:1355]
   at 
 spark.components::Group/getElementAt()[/Users/mvujovic/Documents/FlexSources/trunk6/frameworks/projects/spark/src/spark/components/Group.as:1336]
   at 
 spark.components::SkinnableContainer/getElementAt()[/Users/mvujovic/Documents/FlexSources/trunk6/frameworks/projects/spark/src/spark/components/SkinnableContainer.as:814]
   at spark.components::ViewStack/get 
 selectedElement()[/Users/mvujovic/Documents/FlexSources/trunk6/frameworks/projects/spark/src/spark/components/ViewStack.as:357]
   at 
 spark.components::ViewStack/instantiateSelectedChild()[/Users/mvujovic/Documents/FlexSources/trunk6/frameworks/projects/spark/src/spark/components/ViewStack.as:1001]
   at 
 spark.components::ViewStack/commitProperties()[/Users/mvujovic/Documents/FlexSources/trunk6/frameworks/projects/spark/src/spark/components/ViewStack.as:488]
   at 
 mx.core::UIComponent/validateProperties()[/Users/mvujovic/Documents/FlexSources/trunk6/frameworks/projects/framework/src/mx/core/UIComponent.as:8347]
   at 
 mx.managers::LayoutManager/validateProperties()[/Users/mvujovic/Documents/FlexSources/trunk6/frameworks/projects/framework/src/mx/managers/LayoutManager.as:597]
   at 
 mx.managers::LayoutManager/doPhasedInstantiation()[/Users/mvujovic/Documents/FlexSources/trunk6/frameworks/projects/framework/src/mx/managers/LayoutManager.as:813]
   at 
 mx.managers::LayoutManager/doPhasedInstantiationCallback()[/Users/mvujovic/Documents/FlexSources/trunk6/frameworks/projects/framework/src/mx/managers/LayoutManager.as:1180]
  
  Expected Results:
  No RTE.
  
  Workaround (if any):
  None
 

--
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-28962) Misordered {Key, Value} pairs in Metadata

2013-06-05 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-28962:
-

Labels: easytest  (was: )

 Misordered {Key, Value} pairs in Metadata
 -

 Key: FLEX-28962
 URL: https://issues.apache.org/jira/browse/FLEX-28962
 Project: Apache Flex
  Issue Type: Bug
  Components: .Unspecified - Compiler
Affects Versions: Adobe Flex SDK 4.5.1 (Release)
 Environment: Affected OS(s): Windows
 Affected OS(s): Windows XP
 Browser: Internet Explorer 8.x
 Language Found: English
Reporter: Adobe JIRA
  Labels: easytest

 Steps to reproduce:
 Create a simple function like this :
 [Meta(Key1 = Value1, Key2 = Value2)]
 public function foo():void 
 {...}
 Actual Results:
 After decompilation metadata becomes
 [Meta(Key1 = Key2, Value1 = Value2)]
 public function foo():void 
 {...}

--
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-14994) The offset parameter of Base64Encoder.encodeBytes doesn't work if it's not zero.

2013-06-05 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-14994:
-

Labels: easytest  (was: )

 The offset parameter of Base64Encoder.encodeBytes doesn't work if it's not 
 zero.
 

 Key: FLEX-14994
 URL: https://issues.apache.org/jira/browse/FLEX-14994
 Project: Apache Flex
  Issue Type: Bug
  Components: .Unspecified - Framework
Affects Versions: Adobe Flex SDK Previous
 Environment: Affected OS(s): Windows
 Affected OS(s): 
 Browser: Firefox 2.x
 Language Found: Japanese
Reporter: Adobe JIRA
  Labels: easytest

 Steps to reproduce:
 1. run attached mxml application
 2. click test button
 3. check debug console in FlexBuilder
  
  Actual Results:
  I can't get encoded text if offset is not zero.
  
  Expected Results:
  I can get encoded text if offset is not zero.
  
  
  Workaround (if any):
  creating another small bytearray between offset and length
  
  How to fix
 // see encodeBytes in Base64Encoder.as
 /* original code is below. This is wrong I think.
 var plainIndex:uint = offset;
 while (plainIndex  length)
 */
 /* This should be below.
 var plainIndex:uint = offset;
 while (plainIndex  offset + length)
 */

--
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-33083) Flash builder report An internal build error has occurred. See the error log for more information.

2013-06-05 Thread Justin Mclean (JIRA)


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

Justin Mclean commented on FLEX-33083:
--

The steps 1-6 as described above is not the recommended way to install the SDK. 
Not sure what is an easy way to resolver the issue, but a warning along the 
lines of Missing remote object library in getMessagingClasses would probably 
be the best solution. i.e. Change the MXMLC compiler.

 Flash builder report An internal build error has occurred. See the error log 
 for more information. 
 -

 Key: FLEX-33083
 URL: https://issues.apache.org/jira/browse/FLEX-33083
 Project: Apache Flex
  Issue Type: Bug
  Components: Project Management
 Environment: Flash builder 4.6  , sdk 4.8.0  
Reporter: Alex Harui
  Labels: easyfix

 1. download the source kit from 
 https://svn.apache.org/repos/asf/incubator/flex/trunk
 2. run ant release 
 3. extract apache-flex-sdk-4.8.0-incubating-bin.zip to new folder 
 4. extract AIR Integration Kit.zip to folder 
 5 copy additional files for Flash Ide ( frameworks/libs\player\* and 
 frameworks\*-config.xm)
 6.create a simple project with reference to RemoteObject  
 private var remote:RemoteObject;
 remote = new RemoteObject;
 flash builder log file :
 !ENTRY com.adobe.flexbuilder.project 4 43 2012-06-08 18:27:39.112
 !MESSAGE Uncaught exception in compiler
 !STACK 0
 java.lang.NullPointerException
   at flex2.compiler.CompilerAPI.getMessagingClasses(CompilerAPI.java:1730)
   at flex2.compiler.CompilerAPI.compile(CompilerAPI.java:1538)
   at flex2.tools.oem.Application.compile(Application.java:1357)
   at flex2.tools.oem.Application.recompile(Application.java:1295)
   at flex2.tools.oem.Application.compile(Application.java:894)
   at 
 flex2.tools.flexbuilder.BuilderApplication.compile(BuilderApplication.java:367)
   at 
 com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder$MyBuilder.mybuild(ASApplicationBuilder.java:319)
   at 
 com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.build(ASApplicationBuilder.java:129)
   at 
 com.adobe.flexbuilder.multisdk.compiler.internal.ASBuilder.build(ASBuilder.java:198)
   at 
 com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.build(ASItemBuilder.java:70)
   at 
 com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.buildItem(FlexProjectBuilder.java:607)
   at 
 com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.build(FlexProjectBuilder.java:382)
   at 
 com.adobe.flexbuilder.project.compiler.internal.FlexIncrementalBuilder.build(FlexIncrementalBuilder.java:187)
   at 
 org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
   at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
   at 
 org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
   at 
 org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
   at 
 org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
   at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
   at 
 org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
   at 
 org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
   at 
 org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
   at 
 org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
   at 
 org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
   at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

--
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-33558) CameraUI slow return to flex application on certain devices

2013-06-05 Thread Justin Mclean (JIRA)

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

Justin Mclean commented on FLEX-33558:
--

mpLoader.loadFilePromise(mediaPromise) is a method in AIR and not the Apache
Flex SDK There's probably very little that Apache Flex can do about this issue
as it looks to be an AIR runtime issue or and issue with non SDK code (eg
JPEGEncoder). Different versions of AIR on different phones perform
differently - are you using captive runtime?

CameraUI slow return to flex application on certain devices
---

Key: FLEX-33558
URL: https://issues.apache.org/jira/browse/FLEX-33558
Project: Apache Flex
Issue Type: Bug
Affects Versions: Apache Flex 4.9.0
Environment: See below
Reporter: Jesse Hellyer
Labels: camera, cameraui
Attachments: JPEGEncoder.as, KPMMobileApplication-app.xml,
MobileData2.as, SDK_4.9.1-testing.fxp, _Super_MobileData2.as,
ViewExistingRegistrationRequests.mxml, ViewProductRegistrationIOS.mxml

I have been having very slow results with the CameraUI in flex. Initially,
I was using version 3.1 which was VERY buggy, and I was running into erroring
out returning from the CameraUI, and very slow speeds.
I have since downloaded and installed the newest Apache Flex framework,
4.9.1. The CameraUI returns VERY fast on our Samsung Tab 7.1 that we bought
a few months ago. On an older Droid Charge phone, that is up to date with
updates, it takes 30-40 seconds to return from the CameraUI into my code.
Same with an iPhone 4 running iOS 6.1.
The line in question is marked in yellow below:
mpLoader.loadFilePromise(mediaPromise);
Essentially, I call the cameraUI when the user hits a button. The native
camera interface opens up right away. A picture is taken. On iOS and
Android both, you have to “save” or “use” the picture. Once you click that
button in the native UI, the camera holds on a black screen for a long time
(up to 30 seconds or so). That’s where the error seems to be,
mpLoader.loadFilePromise(mediaPromise);
You can see in the code I have put output statements to a label showing where
the code is hanging. It hangs right after it writes out -16
Here is the code:
https://gist.github.com/MrJesse34/5577978
And here is the XML config file:
https://gist.github.com/MrJesse34/5627336
Here is a video of the behavior on my iPhone:
http://www.youtube.com/watch?v=_QufH1ElqXo
the issue starts at :30 and ends around :50
you can see the busy indicator stops spinning for that time
Note the delay of the busy indicator - it happens right as the
mpLoader.loadFilePromise(mediaPromise); code is ran.

[jira] [Commented] (FLEX-33558) CameraUI slow return to flex application on certain devices

2013-06-05 Thread Justin Mclean (JIRA)


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

Justin Mclean commented on FLEX-33558:
--

AIR methods they are marked with an air symbol in the documentation. The 
package also gives you a good clue if it a Flex SDK class or not.
http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/display/Loader.html

 CameraUI slow return to flex application on certain devices
 ---

 Key: FLEX-33558
 URL: https://issues.apache.org/jira/browse/FLEX-33558
 Project: Apache Flex
  Issue Type: Bug
Affects Versions: Apache Flex 4.9.0
 Environment: See below
Reporter: Jesse Hellyer
  Labels: camera, cameraui
 Attachments: JPEGEncoder.as, KPMMobileApplication-app.xml, 
 MobileData2.as, SDK_4.9.1-testing.fxp, _Super_MobileData2.as, 
 ViewExistingRegistrationRequests.mxml, ViewProductRegistrationIOS.mxml


 I have been having very slow results with the CameraUI in flex.   Initially, 
 I was using version 3.1 which was VERY buggy, and I was running into erroring 
 out returning from the CameraUI, and very slow speeds.
 I have since downloaded and installed the newest Apache Flex framework, 
 4.9.1.   The CameraUI returns VERY fast on our Samsung Tab 7.1 that we bought 
 a few months ago.  On an older Droid Charge phone, that is up to date with 
 updates, it takes 30-40 seconds to return from the CameraUI into my code.  
 Same with an iPhone 4 running iOS 6.1.   
 The line in question is marked in yellow below:  
 mpLoader.loadFilePromise(mediaPromise);
 Essentially, I call the cameraUI when the user hits a button.   The native 
 camera interface opens up right away.  A picture is taken.  On iOS and 
 Android both, you have to “save” or “use” the picture.   Once you click that 
 button in the native UI, the camera holds on a black screen for a long time 
 (up to 30 seconds or so).   That’s where the error seems to be, 
 mpLoader.loadFilePromise(mediaPromise);
 You can see in the code I have put output statements to a label showing where 
 the code is hanging.  It hangs right after it writes out -16
 Here is the code:
 https://gist.github.com/MrJesse34/5577978
 And here is the XML config file:
 https://gist.github.com/MrJesse34/5627336
 Here is a video of the behavior on my iPhone:  
 http://www.youtube.com/watch?v=_QufH1ElqXo
 the issue starts at :30 and ends around :50
 you can see the busy indicator stops spinning for that time
 Note the delay of the busy indicator - it happens right as the  
 mpLoader.loadFilePromise(mediaPromise); code is ran.

--
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-33529) Change build scripts to create Linux source and release packages

2013-06-04 Thread Justin Mclean (JIRA)


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

Justin Mclean commented on FLEX-33529:
--

Fixed issued above so ant main and ant source-release work.

 Change build scripts to create Linux source and release packages
 

 Key: FLEX-33529
 URL: https://issues.apache.org/jira/browse/FLEX-33529
 Project: Apache Flex
  Issue Type: Sub-task
Reporter: Justin Mclean
 Attachments: pb.tar.gz




--
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-32994) Label missing when resizing bar chart.

2013-06-04 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-32994:
-

Labels: easytest  (was: )

 Label missing  when resizing bar chart.
 ---

 Key: FLEX-32994
 URL: https://issues.apache.org/jira/browse/FLEX-32994
 Project: Apache Flex
  Issue Type: Bug
  Components: ADG:Display
Affects Versions: Adobe Flex SDK Previous
 Environment: Affected OS(s): Windows
 Affected OS(s): Windows
 Language Found: English
Reporter: Adobe JIRA
  Labels: easytest

 Steps to reproduce:
 1.Create a bar chart inside a HDivided box. 
 2.Continously resize the chart by dragging the HDivided box.
 3.Sometimes the data inside the chart goes missing(Screenshot attached).
  
  Actual Results:
  When we resize the bar chart continously, sometimes some of the data in the 
 chart goes missing
  
  Expected Results:
  All the data inside the chart should show in every resize.
  
  Workaround (if any):

--
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-33529) Change build scripts to create Linux source and release packages

2013-06-03 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-33529:
-

Attachment: pizelbender.gz

gzip of required PB files to compile on linux

 Change build scripts to create Linux source and release packages
 

 Key: FLEX-33529
 URL: https://issues.apache.org/jira/browse/FLEX-33529
 Project: Apache Flex
  Issue Type: Sub-task
Reporter: Justin Mclean
 Attachments: pizelbender.gz




--
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-33529) Change build scripts to create Linux source and release packages

2013-06-03 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-33529:
-

Attachment: (was: pizelbender.gz)

 Change build scripts to create Linux source and release packages
 

 Key: FLEX-33529
 URL: https://issues.apache.org/jira/browse/FLEX-33529
 Project: Apache Flex
  Issue Type: Sub-task
Reporter: Justin Mclean



--
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-33529) Change build scripts to create Linux source and release packages

2013-06-03 Thread Justin Mclean (JIRA)


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

Justin Mclean updated FLEX-33529:
-

Attachment: pb.tar.gz

Gziped archive of all compiled pixel bender files.

 Change build scripts to create Linux source and release packages
 

 Key: FLEX-33529
 URL: https://issues.apache.org/jira/browse/FLEX-33529
 Project: Apache Flex
  Issue Type: Sub-task
Reporter: Justin Mclean
 Attachments: pb.tar.gz




--
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-33052) Runtime error when using a chart in a module in an app that is also using charts

2013-06-01 Thread Justin Mclean (JIRA)

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

Justin Mclean commented on FLEX-33052:
--

Can you supply a simple project that replicates this?

Runtime error when using a chart in a module in an app that is also using
charts

Key: FLEX-33052
URL: https://issues.apache.org/jira/browse/FLEX-33052
Project: Apache Flex
Issue Type: Bug
Components: Charts
Affects Versions: Adobe Flex SDK Previous
Environment: Affected OS(s): All OS Platforms
Language Found: English
Reporter: Adobe JIRA

This is a regression in 4.6. It doesn't matter if the modules are Spark or
not. Works fine in 4.5.1 and below.
See attached FB project.
Steps to reproduce:
1. Create an app that uses a chart and create a module that also uses a chart.

Actual Results:

TypeError: Error #1009: Cannot access a property or method of a null object
reference.
at
mx.charts.chartClasses::ChartBase/initStyles()[E:\dev\4.y\frameworks\projects\charts\src\mx\charts\chartClasses\ChartBase.as:1862]

Expected Results:

No error and chart loads fine.

Workaround (if any):

Copy chart styles from module's parent styleManager into the module's own
styleManager.

[jira] [Commented] (FLEX-33547) Fix any JIRA bugs we want to see in this release

2013-06-01 Thread Justin Mclean (JIRA)


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

Justin Mclean commented on FLEX-33547:
--

Perhaps also 
FLEX-33052


 Fix any JIRA bugs we want to see in this release
 

 Key: FLEX-33547
 URL: https://issues.apache.org/jira/browse/FLEX-33547
 Project: Apache Flex
  Issue Type: Sub-task
Reporter: Justin Mclean

 Fix any bug we want to see in this release in particular regression issues.

--
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] [Reopened] (FLEX-21488) [TLF 2458351] TextFlow class marked as final

2013-05-31 Thread Justin Mclean (JIRA)


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

Justin Mclean reopened FLEX-21488:
--


Reported as an issue and now TLF is part of Flex we can change.

 [TLF 2458351]  TextFlow class marked as final
 -

 Key: FLEX-21488
 URL: https://issues.apache.org/jira/browse/FLEX-21488
 Project: Apache Flex
  Issue Type: Improvement
  Components: .Unspecified - Framework
Affects Versions: Adobe Flex SDK 4.1 (Release)
 Environment: Language Found: English
Reporter: Adobe JIRA
Assignee: Adobe JIRA

 Steps to reproduce:
 Look into TextFlow, ParagraphElement, LinkElement, etc
  
  Actual Results: Key TLF classes are marked as final 
  
  Expected Results: Key TLF classes shouldn't be marked as final
  
  
  Workaround (if any):
 http://forums.adobe.com/thread/505209

--
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-33529) Change build scripts to create Linux source and release packages

2013-05-30 Thread Justin Mclean (JIRA)


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

Justin Mclean commented on FLEX-33529:
--

Issues for ant main are currently:
1. Main build file checks for pixel bender. Easy fix.
2. Unable to compile the 20 odd pixel bender files. Can copy compile files from 
elsewhere to fix and make pixelbender_clean tasks do nothing.
3. Spark AIR line inint.renderMode = _renderMode; fails to compile. Easy fix.
4. StylableStageText.as fails to compile. Can be conditionally removed from 
MobileComponentClasses?
5. StageTextSkinBase.as, StageTextAreaSkin.as and StageTextInputSkin.as fail to 
compile. Can be conditionally removed from MobileThemeClasses.as?
6. Javascript target fails - missing code. Can remove javascript target from 
framework build.xml file but probably better way of fixing this. Why is code 
missing?

With above mode ant source-release works although may require some 
modifications.

 Change build scripts to create Linux source and release packages
 

 Key: FLEX-33529
 URL: https://issues.apache.org/jira/browse/FLEX-33529
 Project: Apache Flex
  Issue Type: Sub-task
Reporter: Justin Mclean



--
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-33529) Change build scripts to create Linux source and release packages

2013-05-30 Thread Justin Mclean (JIRA)


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

Justin Mclean commented on FLEX-33529:
--

Was compiled on Ubuntu Desktop 12.04 LTS.

Using Ant version:
Apache Ant(TM) version 1.8.2 compiled on December 3 2011

And JDK version:
java version 1.7.0_21
OpenJDK Runtime Environment (IcedTea 2.3.9) (7u21-2.3.9-0ubuntu0.12.04.1)
OpenJDK Client VM (build 23.7-b01, mixed mode, sharing)



 Change build scripts to create Linux source and release packages
 

 Key: FLEX-33529
 URL: https://issues.apache.org/jira/browse/FLEX-33529
 Project: Apache Flex
  Issue Type: Sub-task
Reporter: Justin Mclean



--
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-33529) Change build scripts to create Linux source and release packages

2013-05-30 Thread Justin Mclean (JIRA)

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

Justin Mclean edited comment on FLEX-33529 at 5/31/13 1:04 AM:
---

Issues for ant main are currently:
1. Main build file checks for pixel bender. Easy fix.
2. Unable to compile the 20 odd pixel bender files. Can copy compile files from
elsewhere to fix and make pixelbender_clean tasks do nothing.
3. Spark AIR line inint.renderMode = _renderMode; fails to compile. Easy fix.
4. StylableStageText.as fails to compile. Can be conditionally removed from
MobileComponentClasses?
5. StageTextSkinBase.as, StageTextAreaSkin.as and StageTextInputSkin.as fail to
compile. Can be conditionally removed from MobileThemeClasses.as?
6. Javascript target fails - missing code. Can remove javascript target from
framework build.xml file but probably better way of fixing this. Why is code
missing?

With above modifications ant main and ant source-release succeed although
may be some modifications required.

was (Author: jmclean):
Issues for ant main are currently:
1. Main build file checks for pixel bender. Easy fix.
2. Unable to compile the 20 odd pixel bender files. Can copy compile files from
elsewhere to fix and make pixelbender_clean tasks do nothing.
3. Spark AIR line inint.renderMode = _renderMode; fails to compile. Easy fix.
4. StylableStageText.as fails to compile. Can be conditionally removed from
MobileComponentClasses?
5. StageTextSkinBase.as, StageTextAreaSkin.as and StageTextInputSkin.as fail to
compile. Can be conditionally removed from MobileThemeClasses.as?
6. Javascript target fails - missing code. Can remove javascript target from
framework build.xml file but probably better way of fixing this. Why is code
missing?

With above mode ant source-release works although may require some
modifications.

Change build scripts to create Linux source and release packages

Key: FLEX-33529
URL: https://issues.apache.org/jira/browse/FLEX-33529
Project: Apache Flex
Issue Type: Sub-task
Reporter: Justin Mclean

[jira] [Commented] (FLEX-33529) Change build scripts to create Linux source and release packages

2013-05-30 Thread Justin Mclean (JIRA)


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

Justin Mclean commented on FLEX-33529:
--

ant checkintests runs (and looks like it's correct) but reports failure. 
Probably just bitmap differences?

 Change build scripts to create Linux source and release packages
 

 Key: FLEX-33529
 URL: https://issues.apache.org/jira/browse/FLEX-33529
 Project: Apache Flex
  Issue Type: Sub-task
Reporter: Justin Mclean



--
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-33529) Change build scripts to create Linux source and release packages

2013-05-30 Thread Justin Mclean (JIRA)


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

Justin Mclean commented on FLEX-33529:
--

With above modifications all sub targets of ant binaryrelease except ant 
checkintests work.

 Change build scripts to create Linux source and release packages
 

 Key: FLEX-33529
 URL: https://issues.apache.org/jira/browse/FLEX-33529
 Project: Apache Flex
  Issue Type: Sub-task
Reporter: Justin Mclean



--
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-33529) Change build scripts to create Linux source and release packages

2013-05-30 Thread Justin Mclean (JIRA)


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

Justin Mclean commented on FLEX-33529:
--

Ant checkintests is failing on a test - not sure why.

mustellaresultsparser:
 [java] test case 
sparkDataGridTest1result=failelapsed=5004phase=bodystarted=1369969428947extraInfo=nullmsg=DispatchMouseClickEvent(body:step
 failed
 [java] test case 
MXSortresult=failelapsed=1phase=bodystarted=1369969434705extraInfo=nullmsg=AssertMethodValue
 failed
 [java] results: FAILED


 Change build scripts to create Linux source and release packages
 

 Key: FLEX-33529
 URL: https://issues.apache.org/jira/browse/FLEX-33529
 Project: Apache Flex
  Issue Type: Sub-task
Reporter: Justin Mclean



--
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-33531) Run Mustella tests against Linux version of SDK

2013-05-30 Thread Justin Mclean (JIRA)


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

Justin Mclean commented on FLEX-33531:
--

Issue with path to Flash player in build file - fixed.
Not all tests currently compile due to path issues eg 
Assets/Images/ButtonImages/play.GIF vs Assets/Images/ButtonImages/play.gif.
Missing tests to exclude list - fixed.

Now able to run tests some tests fail.

For example tests/components/Button:

 [java] =
 [java] Passes: 331
 [java] Fails: 52
 [java] =

Other sets of test pass.

tests/components/Label:

 [java] =
 [java] Passes: 255
 [java] Fails: 0
 [java] =

tests/components/Formatters
 [java] =
 [java] Passes: 82
 [java] Fails: 0
 [java] =





 Run Mustella tests against Linux version of SDK
 ---

 Key: FLEX-33531
 URL: https://issues.apache.org/jira/browse/FLEX-33531
 Project: Apache Flex
  Issue Type: Sub-task
Reporter: Justin Mclean



--
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-33529) Change build scripts to create Linux source and release packages

2013-05-30 Thread Justin Mclean (JIRA)


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

Justin Mclean commented on FLEX-33529:
--

Looks like a timing error:
TestCase Start: DataGridTestScript$sparkDataGridTest1
RESULT: 
scriptName=spark.scripts::DataGridTestScriptid=sparkDataGridTest1result=failelapsed=4079phase=bodystarted=1369972795751extraInfo=nullmsg=DispatchMouseClickEvent(body:step
 18)  Timeout waiting for selectionChange from sparkDataGridTests.testdg
testComplete

And a sorting order issue:
TestCase Start: SortTestScript$MXSort
RESULT: 
scriptName=spark.scripts::SortTestScriptid=MXSortresult=failelapsed=1phase=bodystarted=1369972800591extraInfo=nullmsg=AssertMethodValue
 (method cannot be shown)(body:step 1)  method returned cote,côte,coté,côté,川 
(U+5DDD),水 (U+6C34),海 (U+6D77),雨 (U+96E8), expected cote,coté,côte,côté,川 
(U+5DDD),水 (U+6C34),海 (U+6D77),雨 (U+96E8)

 Change build scripts to create Linux source and release packages
 

 Key: FLEX-33529
 URL: https://issues.apache.org/jira/browse/FLEX-33529
 Project: Apache Flex
  Issue Type: Sub-task
Reporter: Justin Mclean



--
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-32721) Border skin sometimes dissappears from AdvancedDataGrid

2013-05-29 Thread Justin Mclean (JIRA)


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

Justin Mclean commented on FLEX-32721:
--

Confirmed still an issue in Apache Flex 4.9.1 and that suggested fix solves the 
issue.

As layoutChrome is fairly lightweight it it seem to be called almost every time 
I think we can do without the check.

 Border skin sometimes dissappears from AdvancedDataGrid
 ---

 Key: FLEX-32721
 URL: https://issues.apache.org/jira/browse/FLEX-32721
 Project: Apache Flex
  Issue Type: Bug
  Components: Advanced Data Grid
Affects Versions: Adobe Flex SDK Previous
 Environment: Affected OS(s): Windows
 Affected OS(s): Windows XP
 Language Found: English
Reporter: Adobe JIRA
Assignee: Justin Mclean
Priority: Minor

 Steps to reproduce:
 1. compile attached mxml
 2. show and hide dataGrid
  
  Actual Results:
  Border goes missing when component re-added to the stage
  
  Expected Results:
  Border does not go missing
  
  Workaround (if any):
 override protected function layoutChrome(unscaledWidth:Number, 
 unscaledHeight:Number):void
 {
   super.layoutChrome( unscaledWidth, unscaledHeight );
   
   _layoutChromeCalled = true;
 }
 override protected function updateDisplayList( w : Number, h : Number ) : void
 {
   _layoutChromeCalled = false;
   
   super.updateDisplayList( w, h );
   
   if( !_layoutChromeCalled )layoutChrome( w, h )
 }
 Explanation:
 When the ADG is re-added to the stage ScrollControlBase.styleChanged is 
 called with styleProp == null. This throws away the border and creates a new 
 one. createBorder calls invalidateDisplayList.
 When updateDisplayList is called AdvancedListBase.updateDisplayList returns 
 without calling super.updateDisplayList as the size of the component has not 
 changed and none of the other conditions evaluate to true. 
 ScrollControlBase.updateDisplayList, which is not called in this case would 
 call layoutChrome which would correctly size the border.

--
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] [Reopened] (FLEX-32571) ADG border disappears on state transition

2013-05-29 Thread Justin Mclean (JIRA)


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

Justin Mclean reopened FLEX-32571:
--

  Assignee: Justin Mclean  (was: Adobe JIRA)

 ADG border disappears on state transition
 -

 Key: FLEX-32571
 URL: https://issues.apache.org/jira/browse/FLEX-32571
 Project: Apache Flex
  Issue Type: Bug
  Components: ADG:Display, ADG:Formatting, Advanced Data Grid
Affects Versions: Adobe Flex SDK Previous
 Environment: Affected OS(s): Windows
 Affected OS(s): Windows
 Language Found: English
Reporter: Adobe JIRA
Assignee: Justin Mclean
Priority: Minor

 (We're using Flex Builder with Flex 3.2.0, also verified on Flex 3.4)
 Removing and then adding an AdvancedDataGrid using states causes border of 
 the AdvancedDataGrid to disappear.
 To reproduce, this app and click on the 'hide' button, then click on the 
 button.  The ADG's border will be gone.  Sorting or resizing a column will 
 cause the border to draw again.

--
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

1 2 3 4 5 6 7 8 9 >

1 - 100 of 878 matches

Mail list logo