[jira] [Resolved] (FLEX-23464) Setting selectedDate in closed handler of DateField doesn't update selectedDate
[ https://issues.apache.org/jira/browse/FLEX-23464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-23464. -- Resolution: Fixed Fix Version/s: Apache Flex 4.10.0 Fixed in previous version or in Apche Flex develop branch > Setting selectedDate in closed handler of DateField doesn't update > selectedDate > --- > > Key: FLEX-23464 > URL: https://issues.apache.org/jira/browse/FLEX-23464 > Project: Apache Flex > Issue Type: Bug > Components: mx: DateField >Affects Versions: Adobe Flex SDK 3.5 (Release) > Environment: Affected OS(s): Windows > Affected OS(s): Windows XP > Browser: Internet Explorer 7.x > Language Found: English >Reporter: Adobe JIRA > Fix For: Apache Flex 4.10.0 > > > Steps to reproduce: > 1. Run attached example (or create your own example, being: datefield with > closed handler, inside the closed handler overwrite the selectedDate of the > datefield). > 2. Click the DateField and select a date (when using attached example: > selected date not being today) > 3. See that the SelectedDate from the closed handler doesn't get reflected > > Actual Results: > The date set in the closed handler is not set to the date field. The date > from the handler is only used when the date chooser is opened and no date is > selected (click outside the date chooser). > The handler is called both times. > > Expected Results: > The date set in the closed handler to be reflected in the date field. > > Workaround (if any): > Add a "validateNow()" call after setting the selectedDate: > > http://www.adobe.com/2006/mxml";> > > >> > > > > > > > > > > -- 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-23834) mx.controls.DateField with editable=true and DataGrid itemEditor
[ https://issues.apache.org/jira/browse/FLEX-23834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-23834. -- Resolution: Fixed Fix Version/s: Apache Flex 4.10.0 Checked into develop branch > mx.controls.DateField with editable=true and DataGrid itemEditor > > > Key: FLEX-23834 > URL: https://issues.apache.org/jira/browse/FLEX-23834 > Project: Apache Flex > Issue Type: Bug > Components: mx: DateField >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 > Fix For: Apache Flex 4.10.0 > > > Steps to reproduce: > > > > > >dataField="date" editorDataField="selectedDate" > itemEditor="mx.controls.DateField" /> >dataField="date" editorDataField="selectedDate" > > > > > > > > > > > Actual Results: > When you start editing "correct" column(in example above) and press Escape, > editing is cancelled. But when you start editing "incorrect" column and press > Escape nothing happens and editing continues. > > Expected Results: > Editing should be cancelled in both cases. > > > Workaround (if any): > mx.controls.DateField class overrides keyDownHandler and checks for Escape > key. But the problem is it calls event.stopPropagation() which prevents > DataGrid to get Escape key down event inorder to cancel editing mode. > Workaround is to comment that one line or extend DateField class, override > keyDownHandler and not call super.keyDownHandler. In this case you loose key > navigation in DateField but get editing cancellation in case of DataGrid item > editor. -- 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] [Assigned] (FLEX-33542) mx:AdvancedDataGrid header column separators display embedded SWF on mouseover
[ https://issues.apache.org/jira/browse/FLEX-33542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean reassigned FLEX-33542: Assignee: Alex Harui > mx:AdvancedDataGrid header column separators display embedded SWF on mouseover > -- > > Key: FLEX-33542 > URL: https://issues.apache.org/jira/browse/FLEX-33542 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Framework >Affects Versions: Apache Flex 4.9.0 >Reporter: Edward Trochim >Assignee: Alex Harui > Attachments: AdvDataGridBugTest.zip > > > The mx:AdvancedDataGrid control in Flex 4.9.1 is acting very oddly when the > application has an embedded SWF. When a user mouses over the header column > separators in the AdvancedDataGrid the SWF will display on top of the mouse > cursor. A demonstration of this behavior can be found here: > https://dl.dropboxusercontent.com/u/11780410/AdvDataGridBugTest/AdvDataGridBugTest.html -- 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-33542) mx:AdvancedDataGrid header column separators display embedded SWF on mouseover
[ https://issues.apache.org/jira/browse/FLEX-33542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13651579#comment-13651579 ] Justin Mclean commented on FLEX-33542: -- And also with s:Image (inside or outside a declaration block) rather than mx:SWFLoader. > mx:AdvancedDataGrid header column separators display embedded SWF on mouseover > -- > > Key: FLEX-33542 > URL: https://issues.apache.org/jira/browse/FLEX-33542 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Framework >Affects Versions: Apache Flex 4.9.0 >Reporter: Edward Trochim > Attachments: AdvDataGridBugTest.zip > > > The mx:AdvancedDataGrid control in Flex 4.9.1 is acting very oddly when the > application has an embedded SWF. When a user mouses over the header column > separators in the AdvancedDataGrid the SWF will display on top of the mouse > cursor. A demonstration of this behavior can be found here: > https://dl.dropboxusercontent.com/u/11780410/AdvDataGridBugTest/AdvDataGridBugTest.html -- 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-33542) mx:AdvancedDataGrid header column separators display embedded SWF on mouseover
[ https://issues.apache.org/jira/browse/FLEX-33542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13651568#comment-13651568 ] Justin Mclean commented on FLEX-33542: -- And also spark data grid - so more likely an issue with Cursors or SWFLoader? > mx:AdvancedDataGrid header column separators display embedded SWF on mouseover > -- > > Key: FLEX-33542 > URL: https://issues.apache.org/jira/browse/FLEX-33542 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Framework >Affects Versions: Apache Flex 4.9.0 >Reporter: Edward Trochim > Attachments: AdvDataGridBugTest.zip > > > The mx:AdvancedDataGrid control in Flex 4.9.1 is acting very oddly when the > application has an embedded SWF. When a user mouses over the header column > separators in the AdvancedDataGrid the SWF will display on top of the mouse > cursor. A demonstration of this behavior can be found here: > https://dl.dropboxusercontent.com/u/11780410/AdvDataGridBugTest/AdvDataGridBugTest.html -- 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-33542) mx:AdvancedDataGrid header column separators display embedded SWF on mouseover
[ https://issues.apache.org/jira/browse/FLEX-33542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13651565#comment-13651565 ] Justin Mclean commented on FLEX-33542: -- Also happens with mx:Datagrid. > mx:AdvancedDataGrid header column separators display embedded SWF on mouseover > -- > > Key: FLEX-33542 > URL: https://issues.apache.org/jira/browse/FLEX-33542 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Framework >Affects Versions: Apache Flex 4.9.0 >Reporter: Edward Trochim > Attachments: AdvDataGridBugTest.zip > > > The mx:AdvancedDataGrid control in Flex 4.9.1 is acting very oddly when the > application has an embedded SWF. When a user mouses over the header column > separators in the AdvancedDataGrid the SWF will display on top of the mouse > cursor. A demonstration of this behavior can be found here: > https://dl.dropboxusercontent.com/u/11780410/AdvDataGridBugTest/AdvDataGridBugTest.html -- 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-33542) mx:AdvancedDataGrid header column separators display embedded SWF on mouseover
[ https://issues.apache.org/jira/browse/FLEX-33542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13651561#comment-13651561 ] Justin Mclean commented on FLEX-33542: -- Confirmed - doesn't happen in Adobe Flex 4.6 either. > mx:AdvancedDataGrid header column separators display embedded SWF on mouseover > -- > > Key: FLEX-33542 > URL: https://issues.apache.org/jira/browse/FLEX-33542 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Framework >Affects Versions: Apache Flex 4.9.0 >Reporter: Edward Trochim > Attachments: AdvDataGridBugTest.zip > > > The mx:AdvancedDataGrid control in Flex 4.9.1 is interacting very oddly when > the application has an embedded SWF. When a user mouses over the header > column separators in the AdvancedDataGrid the SWF will display on top of the > mouse cursor. A demonstration of this behavior can be found here: > https://dl.dropboxusercontent.com/u/11780410/AdvDataGridBugTest/AdvDataGridBugTest.html -- 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-33542) mx:AdvancedDataGrid header column separators display embedded SWF on mouseover
[ https://issues.apache.org/jira/browse/FLEX-33542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13650987#comment-13650987 ] Justin Mclean edited comment on FLEX-33542 at 5/7/13 3:57 PM: -- Can you provide sample code showing this issue? It will be easier to fix if we have code to look at. was (Author: jmclean): Can you provide a sample code showing this issue? It will be easier to fix if we have code to look at. > mx:AdvancedDataGrid header column separators display embedded SWF on mouseover > -- > > Key: FLEX-33542 > URL: https://issues.apache.org/jira/browse/FLEX-33542 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Framework >Affects Versions: Apache Flex 4.9.0 >Reporter: Edward Trochim > > The mx:AdvancedDataGrid control in Flex 4.9.1 is interacting very oddly when > the application has an embedded SWF. When a user mouses over the header > column separators in the AdvancedDataGrid the SWF will display on top of the > mouse cursor. A demonstration of this behavior can be found here: > https://dl.dropboxusercontent.com/u/11780410/AdvDataGridBugTest/AdvDataGridBugTest.html -- 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-33542) mx:AdvancedDataGrid header column separators display embedded SWF on mouseover
[ https://issues.apache.org/jira/browse/FLEX-33542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13650987#comment-13650987 ] Justin Mclean commented on FLEX-33542: -- Can you provide a sample code showing this issue? It will be easier to fix if we have code to look at. > mx:AdvancedDataGrid header column separators display embedded SWF on mouseover > -- > > Key: FLEX-33542 > URL: https://issues.apache.org/jira/browse/FLEX-33542 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Framework >Affects Versions: Apache Flex 4.9.0 >Reporter: Edward Trochim > > The mx:AdvancedDataGrid control in Flex 4.9.1 is interacting very oddly when > the application has an embedded SWF. When a user mouses over the header > column separators in the AdvancedDataGrid the SWF will display on top of the > mouse cursor. A demonstration of this behavior can be found here: > https://dl.dropboxusercontent.com/u/11780410/AdvDataGridBugTest/AdvDataGridBugTest.html -- 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-16334) VBox: maxVerticalScrollPosition == 0 if VBox has scrollbar and heigth has value in percent
[ https://issues.apache.org/jira/browse/FLEX-16334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-16334: - Labels: easytest (was: ) > VBox: maxVerticalScrollPosition == 0 if VBox has scrollbar and heigth has > value in percent > -- > > Key: FLEX-16334 > URL: https://issues.apache.org/jira/browse/FLEX-16334 > Project: Apache Flex > Issue Type: Bug > Components: mx: Box View >Affects Versions: Adobe Flex SDK 3.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 example > 2.Click on "ClickMe" button > 3.Click on "ClickMe" button again > 4.Click .. click ... click :) > > Actual Results: > Text box has 0 value instead of real maxVerticalScrollPosition > > Expected Results: > Real maxVerticalScrollPosition > > Workaround (if any): > Doesn't use width in percent -- 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-28657) mx:TabNavigator text truncation stopped working in 22797
[
https://issues.apache.org/jira/browse/FLEX-28657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-28657:
-
Labels: easytest (was: )
> mx:TabNavigator text truncation stopped working in 22797
>
>
> Key: FLEX-28657
> URL: https://issues.apache.org/jira/browse/FLEX-28657
> Project: Apache Flex
> Issue Type: Bug
> Components: mx: Tab Navigator
>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. Create a new Flex application with the halo theme using this code:
>
> xmlns:mx="http://www.adobe.com/2006/mxml";
> backgroundColor="0xFF">
> heightTo="177" duration="250" target="{uiComponent}" />
>
> layout="absolute"
> width="400"
> height="300"
> title="Test Panel" >
>
> width="143"
> height="150" selectedIndex="1">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> 2. Click Play
> 3.
>
> Actual Results:
>
> The text in the tabs is no longer truncated after the effect.
>
> Expected Results:
> The text in the tabs should be truncated
>
> 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-27468) The TextArea's bounds are reported as starting at local coordinates of -18,-18 instead of 0,0!
[
https://issues.apache.org/jira/browse/FLEX-27468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-27468:
-
Labels: easytest (was: )
> The TextArea's bounds are reported as starting at local coordinates of
> -18,-18 instead of 0,0!
> --
>
> Key: FLEX-27468
> URL: https://issues.apache.org/jira/browse/FLEX-27468
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark: TextArea
>Affects Versions: Adobe Flex SDK 4.5 (Release)
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Language Found: English
>Reporter: Adobe JIRA
> Labels: easytest
>
> Steps to reproduce:
>
> 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" creationComplete="init()">
>
> private function init(event:Event=null):void {
> var bounds:Rectangle = test2.getBounds(test2);
> trace(bounds); //reports (x=-18, y=-18, w=206, h=169)
> }
>
>
>
>
>
>
>
> Actual Results:
> (x=-18, y=-18, w=206, h=169)
>
> Expected Results:
> (x=0, y=0, w=206, h=169)
--
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-27768) DateField formatString doesn't display month name as expected
[ https://issues.apache.org/jira/browse/FLEX-27768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-27768. -- Resolution: Fixed Fixed and checked into develop branch > DateField formatString doesn't display month name as expected > - > > Key: FLEX-27768 > URL: https://issues.apache.org/jira/browse/FLEX-27768 > Project: Apache Flex > Issue Type: Bug > Components: mx: DateField >Affects Versions: Adobe Flex SDK 4.5.1 (Release) > Environment: Affected OS(s): Windows > Affected OS(s): Windows 7 > Language Found: English >Reporter: Adobe JIRA > Labels: easyfix > > Steps to reproduce: > 1. Create Adobe AIR Project and insert MX:DateField control > 2. Set formatString to "DD MMM " > 3. Run the application and select a date > > Actual Results: > 30 06062011 > > Expected Results: > 30 Jun 2011 > > Workaround (if any): > The Adobe Help website shows an example where the date appears as "24 Feb > 2004" inside the DateField box, however there's no source code showing how > this has been achieved: > http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7d9b.html#WS2db454920e96a9e51e63e3d11c0bf63b33-7fd4 -- 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-22865) Changing a DateChooser's displayedMonth to X and then immediately changing it back results in it showing month X instead of the original month
[ https://issues.apache.org/jira/browse/FLEX-22865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-22865. -- Resolution: Fixed Fix Version/s: Apache Flex 4.10.0 Fixed and checked into develop branch. > Changing a DateChooser's displayedMonth to X and then immediately changing it > back results in it showing month X instead of the original month > -- > > Key: FLEX-22865 > URL: https://issues.apache.org/jira/browse/FLEX-22865 > Project: Apache Flex > Issue Type: Bug > Components: mx: DateChooser >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 > Fix For: Apache Flex 4.10.0 > > > Steps to reproduce: > 1. Set a DateChooser's "displayedMonth" property to something other than its > current value. > 2. Immediately afterward set the DateChooser's "displayedMonth" back to its > original value. > > Actual Results: > The month displayed on the DateChooser is the intermediate value. > > > Expected Results: > The month displayed on the DateChooser should be it's original value. > > > Workaround (if any): > Monkeypatch! Okay, there are probably other ways of working around it, but > that's how I did it. > Additional Information > See attached file. It's an extremely simple example. > I believe the problem lies in CalendarLayout's "set displayedMonth" function. > It checks the new value against "_displayedMonth" but I believe it should > check the new value against "displayedMonth" (no underscore) or possibly > "_proposedDisplayedMonth". -- 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-20804) Datefield change please remove the the DateChooser control close to check
[ https://issues.apache.org/jira/browse/FLEX-20804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-20804: - Labels: easytest (was: ) > Datefield change please remove the the DateChooser control close to check > -- > > Key: FLEX-20804 > URL: https://issues.apache.org/jira/browse/FLEX-20804 > Project: Apache Flex > Issue Type: Improvement > Components: mx: DateField >Affects Versions: Adobe Flex SDK 3.3 (Release) > Environment: Affected OS(s): All OS Platforms > Affected OS(s): All OS Platforms > Browser: Internet Explorer 6.x > Language Found: English >Reporter: Adobe JIRA > Labels: easytest > > Steps to reproduce: > 1. Create a datefield > 2. Create a validation on it > 3. Create a change function (to run an extra validate function) > 4. make the datefield editable > 5. Change the date it in runtime by typing it in > > Actual Results: > It does not trigger the extra validation function > > Expected Results: > It should trigger the extra validation function > > Workaround (if any): > None. > > Why does this happen. > Because the change event is Dispatched when a date is selected or changed, > and the DateChooser control closes. > > I dont understand why the change event is triggered only when also the > datechooser control closes ? > When I type in a date, it also changes right ? -- 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-21790) setting DateChooser's displayedYear property does not work consistently
[ https://issues.apache.org/jira/browse/FLEX-21790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-21790. -- Resolution: Not A Problem Fix Version/s: Apache Flex 4.10.0 Resolved in previous version of the SDK > setting DateChooser's displayedYear property does not work consistently > --- > > Key: FLEX-21790 > URL: https://issues.apache.org/jira/browse/FLEX-21790 > Project: Apache Flex > Issue Type: Bug > Components: mx: DateChooser >Affects Versions: Adobe Flex SDK 3.3 (Release) > Environment: Affected OS(s): Windows > Affected OS(s): Windows XP > Browser: Firefox 3.x > Language Found: English >Reporter: Adobe JIRA > Fix For: Apache Flex 4.10.0 > > > Steps to reproduce: > 1. select any date from the DataGrid whose year corresponds to the current > year > > Actual Results: > displayedYear in the DateChooser is set to 0 > > Expected Results: > displayedYear in DateChooser should be set to the year of the date selected > from the DataGrid -- 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-13423) DateChooser selectedRanges gives selectedRange start+1 day [if selectedRanges.rangeStart is same as selectableRange.rangeStart]
[ https://issues.apache.org/jira/browse/FLEX-13423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-13423: - Labels: easyfix easytest (was: ) > 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 >Priority: Minor > Labels: easyfix, easytest > Fix For: Adobe Flex SDK 3.0 (Release) > > > Steps to reproduce: > 1. Compile and run the below sample piece of code > > http://www.adobe.com/2006/mxml";> >allowMultipleSelection="true" /> > > > > > > > 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] [Resolved] (FLEX-14153) Unrequired cast of calHeader in DateChooser
[
https://issues.apache.org/jira/browse/FLEX-14153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean resolved FLEX-14153.
--
Resolution: Fixed
Fix Version/s: Apache Flex 4.10.0
fixed and checked into development branch
> Unrequired cast of calHeader in DateChooser
> ---
>
> Key: FLEX-14153
> URL: https://issues.apache.org/jira/browse/FLEX-14153
> Project: Apache Flex
> Issue Type: Improvement
> Components: mx: DateChooser
>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
> Fix For: Apache Flex 4.10.0
>
>
> line 1873 of DateChooser casts calHeader to UIComponent.
> calHeader is declared with the type UIComponent, it's created as a
> UIComponent and therefore this cast is redundant.
> /**
> * @private
> */
> mx_internal var calHeader:UIComponent;
> if (!calHeader)
> {
> calHeader = new UIComponent();
> addChild(calHeader);
>UIComponent(calHeader).styleName = this; <-- cast is
> rundundant
> }
--
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-27652) DateChooser displays incorrect month label
[ https://issues.apache.org/jira/browse/FLEX-27652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-27652. -- Resolution: Fixed Fix Version/s: Apache Flex 4.10.0 Checked into develop branch > DateChooser displays incorrect month label > -- > > Key: FLEX-27652 > URL: https://issues.apache.org/jira/browse/FLEX-27652 > Project: Apache Flex > Issue Type: Bug > Components: mx: DateChooser >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: easyfix, easytest > Fix For: Apache Flex 4.10.0 > > > Steps to reproduce: > 1. Open the attached project and run > 2. Click the button > 3. DateChooser displayed as a popup, current year and calendar correct, but > month label incorrect > 4. Return to project and uncomment line 19, then repeat steps 1-3 > 5. Note now that month displays correctly > > Actual Results: > Instead of the current month displaying in the label, the label displays > "September". This is because September is the longest month in terms of > number of characters, and text fields text property is set to this value > during setMonthWidth, but never reset back to original value. > > Expected Results: > Label displays correct month > > Workaround (if any): > Need to call invalidateDisplayList on the DateChooser at a later time -- 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-20956) [Localization]: DateField should support "MMM" and "MMMM" for formatString
[ https://issues.apache.org/jira/browse/FLEX-20956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-20956. -- Resolution: Fixed Fix Version/s: Apache Flex 4.10.0 Checked into develop branch. > [Localization]: DateField should support "MMM" and "" for formatString > -- > > Key: FLEX-20956 > URL: https://issues.apache.org/jira/browse/FLEX-20956 > Project: Apache Flex > Issue Type: Bug > Components: mx: DateField >Affects Versions: Adobe Flex SDK 3.4 (Release) > 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: Apache Flex 4.10.0 > > > Steps to reproduce: > 1. Compile and run the following application: > > xmlns:mx="http://www.adobe.com/2006/mxml"; > styleName="plain"> > > > formatString="DD--"/> > > > > Actual Results: >field displays "08-0909-2009" > > Expected Results: > field should display "08-September-09" > > Workaround (if any): > Patch static method "dateToString" of DateField by ourselves. -- 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-33541) Update Apache Flex release notes for the next release
[ https://issues.apache.org/jira/browse/FLEX-33541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-33541: - Affects Version/s: Apache Flex 4.9.0 > Update Apache Flex release notes for the next release > - > > Key: FLEX-33541 > URL: https://issues.apache.org/jira/browse/FLEX-33541 > Project: Apache Flex > Issue Type: Improvement >Affects Versions: Apache Flex 4.9.0 >Reporter: Justin Mclean > > Update release note to reflect all changes since the 4.9 release last > december. -- 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-33541) Update Apache Flex release notes for the next release
[ https://issues.apache.org/jira/browse/FLEX-33541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13650615#comment-13650615 ] Justin Mclean commented on FLEX-33541: -- Made a start and checked into develop. > Update Apache Flex release notes for the next release > - > > Key: FLEX-33541 > URL: https://issues.apache.org/jira/browse/FLEX-33541 > Project: Apache Flex > Issue Type: Improvement >Reporter: Justin Mclean > > Update release note to reflect all changes since the 4.9 release last > december. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FLEX-33541) Update Apache Flex release notes for the next release
Justin Mclean created FLEX-33541: Summary: Update Apache Flex release notes for the next release Key: FLEX-33541 URL: https://issues.apache.org/jira/browse/FLEX-33541 Project: Apache Flex Issue Type: Improvement Reporter: Justin Mclean Update release note to reflect all changes since the 4.9 release last december. -- 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-26325) RemoteObject logs too eagerly all sent messages
[
https://issues.apache.org/jira/browse/FLEX-26325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean resolved FLEX-26325.
--
Resolution: Fixed
Fix Version/s: Apache Flex 4.10.0
Added externalToString method to set user defined method to call.
> RemoteObject logs too eagerly all sent messages
> ---
>
> Key: FLEX-26325
> URL: https://issues.apache.org/jira/browse/FLEX-26325
> Project: Apache Flex
> Issue Type: Bug
> Components: RPC: RemoteObject
>Affects Versions: Adobe Flex SDK 4.1 (Release)
> Environment: Affected OS(s): All OS Platforms
> Language Found: English
>Reporter: Adobe JIRA
>Assignee: Justin Mclean
> Labels: easyfix
> Fix For: Apache Flex 4.10.0
>
> Attachments: 2833.patch
>
>
> Steps to reproduce:
> 1. Set debug level on any Logger in the application (not even necessarily on
> mx.rpc.*)
> 2. Call a remote operation with a RemoteObject sending a complex object
> graph, or an object graph containing 'lazy loaded' data, e.g. with LCDS or
> GraniteDS
>
> Actual Results:
> RemoteObject computes the complete debug message in RPCObjectUtils by the
> ultra slow AS3 reflection (even when the message will never be logged at
> all), and consequently triggers all lazy initializations (for example by
> accessing all lazyCollection.length properties on all the object graph).
> See here for more details on the issue:
> http://insideria.com/2010/10/flex-rpc-and-the-broken-mxlogg.html
>
> Expected Results:
> No computation of the debug message should be done when mx.rpc is not in
> debug mode.
> At least provide one of these options :
> - Allow adding manually excluded properties in
> RPCObjectUtils.defaultToStringExcludes (make it public or add a function
> addDefaultExclude)
> - Use existing toString() methods on objects when available instead of always
> relying on AS3 reflection
> - Provide a way to completely override the default RPCObjectUtil.toString,
> i.e.
> public var toStringFunction:Function;
> public static function toString(value:Object,
> namespaceURIs:Array = null,
> exclude:Array = null):String
> {
> if (toStringFunction != null) {
> return toStringFunction(value, namespaceURIs, exclude);
> }
> if (exclude == null)
> {
> exclude = defaultToStringExcludes;
> }
>
> refCount = 0;
> return internalToString(value, 0, null, namespaceURIs, exclude);
> }
>
> Workaround (if any):
>
> Never set any debug level on any Logger.
--
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] [Assigned] (FLEX-26325) RemoteObject logs too eagerly all sent messages
[
https://issues.apache.org/jira/browse/FLEX-26325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean reassigned FLEX-26325:
Assignee: Justin Mclean (was: Adobe JIRA)
> RemoteObject logs too eagerly all sent messages
> ---
>
> Key: FLEX-26325
> URL: https://issues.apache.org/jira/browse/FLEX-26325
> Project: Apache Flex
> Issue Type: Bug
> Components: RPC: RemoteObject
>Affects Versions: Adobe Flex SDK 4.1 (Release)
> Environment: Affected OS(s): All OS Platforms
> Language Found: English
>Reporter: Adobe JIRA
>Assignee: Justin Mclean
> Labels: easyfix
> Attachments: 2833.patch
>
>
> Steps to reproduce:
> 1. Set debug level on any Logger in the application (not even necessarily on
> mx.rpc.*)
> 2. Call a remote operation with a RemoteObject sending a complex object
> graph, or an object graph containing 'lazy loaded' data, e.g. with LCDS or
> GraniteDS
>
> Actual Results:
> RemoteObject computes the complete debug message in RPCObjectUtils by the
> ultra slow AS3 reflection (even when the message will never be logged at
> all), and consequently triggers all lazy initializations (for example by
> accessing all lazyCollection.length properties on all the object graph).
> See here for more details on the issue:
> http://insideria.com/2010/10/flex-rpc-and-the-broken-mxlogg.html
>
> Expected Results:
> No computation of the debug message should be done when mx.rpc is not in
> debug mode.
> At least provide one of these options :
> - Allow adding manually excluded properties in
> RPCObjectUtils.defaultToStringExcludes (make it public or add a function
> addDefaultExclude)
> - Use existing toString() methods on objects when available instead of always
> relying on AS3 reflection
> - Provide a way to completely override the default RPCObjectUtil.toString,
> i.e.
> public var toStringFunction:Function;
> public static function toString(value:Object,
> namespaceURIs:Array = null,
> exclude:Array = null):String
> {
> if (toStringFunction != null) {
> return toStringFunction(value, namespaceURIs, exclude);
> }
> if (exclude == null)
> {
> exclude = defaultToStringExcludes;
> }
>
> refCount = 0;
> return internalToString(value, 0, null, namespaceURIs, exclude);
> }
>
> Workaround (if any):
>
> Never set any debug level on any Logger.
--
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-26048) DateChooser throws #1010 error when selectableRange is empty object
[ https://issues.apache.org/jira/browse/FLEX-26048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-26048. -- Resolution: Fixed Fix Version/s: Apache Flex 4.10.0 Also check in start and end are actually dates. > DateChooser throws #1010 error when selectableRange is empty object > --- > > Key: FLEX-26048 > URL: https://issues.apache.org/jira/browse/FLEX-26048 > Project: Apache Flex > Issue Type: Bug > Components: mx: DateChooser >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 >Priority: Minor > Labels: easyfix, easytest > Fix For: Apache Flex 4.10.0 > > > Steps to reproduce: > 1. Run attached project > 2. Click "Next Month" button > > Actual Results: > Runtime error > > Expected Results: > null range dates should be ignored > > > Workaround (if any): > Don't set any object at all -- 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-13401) format() method in NumbeFormatter should understand numbers in Scientic notation e.g. 1.2E7
[ https://issues.apache.org/jira/browse/FLEX-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-13401. -- Resolution: Fixed Fix Version/s: Apache Flex 4.10.0 Fixed by FLEX-18951 > format() method in NumbeFormatter should understand numbers in Scientic > notation e.g. 1.2E7 > --- > > Key: FLEX-13401 > URL: https://issues.apache.org/jira/browse/FLEX-13401 > Project: Apache Flex > Issue Type: Bug > Components: Formatters >Affects Versions: Adobe Flex SDK 3.0 (Release) > Environment: Affected OS(s): Windows > Browser: Firefox 2.x > Language Found: English >Reporter: Adobe JIRA > Fix For: Apache Flex 4.10.0 > > > Steps to reproduce: > 1. var nf:NumberFormatter = new NumberFormatter(); > 2. nf.precision = 2; > 3. var v:String = nf.format(1.2E7); > > Actual Results: 7 > > > Expected Results: 12,000,000 > > > Workaround (if any): nf.format(1200); -- 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-28401) NumericStepper steps incorrectly with decimal values
[ https://issues.apache.org/jira/browse/FLEX-28401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-28401: - Labels: easyfix easytest (was: easytest) > NumericStepper steps incorrectly with decimal values > > > Key: FLEX-28401 > URL: https://issues.apache.org/jira/browse/FLEX-28401 > Project: Apache Flex > Issue Type: Bug > Components: Spark: NumericStepper >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: easyfix, easytest > > Steps to reproduce: > 1. Run the attached Main.mxml > 2. "Step up" using up arrow the NumericStepper which is first one (fourth > from the bottom) > > Actual Results: > When you "step up" once, it is 1e-7 > When you "step up" twice, it is NaN > > Expected Results: > It should be 0.001 ->0.002 ->0.003 > You can compare with the the NumericStepper which is second from the top > (third from the bottom) > > 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-28401) NumericStepper steps incorrectly with decimal values
[ https://issues.apache.org/jira/browse/FLEX-28401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649481#comment-13649481 ] Justin Mclean commented on FLEX-28401: -- Fixed for mx:NumericStepper and check into develop branch. s:NumericStepper freezes on "0" and up/down don't change values. > NumericStepper steps incorrectly with decimal values > > > Key: FLEX-28401 > URL: https://issues.apache.org/jira/browse/FLEX-28401 > Project: Apache Flex > Issue Type: Bug > Components: Spark: NumericStepper >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. Run the attached Main.mxml > 2. "Step up" using up arrow the NumericStepper which is first one (fourth > from the bottom) > > Actual Results: > When you "step up" once, it is 1e-7 > When you "step up" twice, it is NaN > > Expected Results: > It should be 0.001 ->0.002 ->0.003 > You can compare with the the NumericStepper which is second from the top > (third from the bottom) > > 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-28401) NumericStepper steps incorrectly with decimal values
[ https://issues.apache.org/jira/browse/FLEX-28401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649474#comment-13649474 ] Justin Mclean commented on FLEX-28401: -- In Apache Flex develop no longer show "NaN" and steps correctly but still shows scientific notation. > NumericStepper steps incorrectly with decimal values > > > Key: FLEX-28401 > URL: https://issues.apache.org/jira/browse/FLEX-28401 > Project: Apache Flex > Issue Type: Bug > Components: Spark: NumericStepper >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. Run the attached Main.mxml > 2. "Step up" using up arrow the NumericStepper which is first one (fourth > from the bottom) > > Actual Results: > When you "step up" once, it is 1e-7 > When you "step up" twice, it is NaN > > Expected Results: > It should be 0.001 ->0.002 ->0.003 > You can compare with the the NumericStepper which is second from the top > (third from the bottom) > > 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-23695) CurrencyFormatter.format() gives wrong result if the number has "e" exponent.
[ https://issues.apache.org/jira/browse/FLEX-23695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-23695. -- Resolution: Fixed Fix Version/s: Apache Flex 4.10.0 Fixed by FLEX-18951 > CurrencyFormatter.format() gives wrong result if the number has "e" exponent. > - > > Key: FLEX-23695 > URL: https://issues.apache.org/jira/browse/FLEX-23695 > Project: Apache Flex > Issue Type: Bug > Components: Formatters >Affects Versions: Adobe Flex SDK 3.5 (Release) > Environment: Affected OS(s): Mac > Affected OS(s): Mac OS 10.6 > Browser: Firefox 3.x > Language Found: English >Reporter: Adobe JIRA >Priority: Minor > Fix For: Apache Flex 4.10.0 > > > Steps to reproduce: > 1.Create a CurrencyFormatter > 2.Try format this number (2.277963176590994e-8) > 3.You will get (-8) > > Actual Results: > -8 > > Expected Results: > 2.277963176590994e-8 > > Workaround (if any): > well, override the formatter and make sure to expand the exponent! -- 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-25622) NumberValidator doesn't handle scientific notation
[ https://issues.apache.org/jira/browse/FLEX-25622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-25622. -- Resolution: Fixed Fix Version/s: Apache Flex 4.10.0 Fixed in FLEX-18951 > NumberValidator doesn't handle scientific notation > -- > > Key: FLEX-25622 > URL: https://issues.apache.org/jira/browse/FLEX-25622 > Project: Apache Flex > Issue Type: Bug > Components: Validators >Affects Versions: Adobe Flex SDK 3.2 (Release) > Environment: Affected OS(s): All OS Platforms > Language Found: English >Reporter: Adobe JIRA > Labels: easyfix, easytest > Fix For: Apache Flex 4.10.0 > > > Steps to reproduce: > 1. Using the attached application, if you enter in a number like > 1234567879123400 into the textinput, you will get a validation > error. This is because the scientific notation that is outputted from the > NumberFormatter class isn't able to be handled from by the NumberValidator > class. > 2.Even if you create an instance of a Number using this value, it will fail > as well as the NumberValidator will convert the Number into a string (by > calling the toString() method on the Number class which will return the > number in scientific notation as well). > > Actual Results: > > The NumberValidator states that the value contains invalid characters. > > Expected Results: > > I expected the NumberValidator to be able to handle the output from the > NumberFormatter class as well as the toString() method of the Number class. > Workaround (if any): > > None without extending the NumberValidator class to add support for > scientific notation. -- 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-18951) NumberFormatter.format returns wrong number for some scientific notation values
[ https://issues.apache.org/jira/browse/FLEX-18951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-18951. -- Resolution: Fixed Fix Version/s: Apache Flex 4.10.0 Fixed for both numbers and strings as input to the format function. > NumberFormatter.format returns wrong number for some scientific notation > values > --- > > Key: FLEX-18951 > URL: https://issues.apache.org/jira/browse/FLEX-18951 > Project: Apache Flex > Issue Type: Bug > Components: Formatters >Affects Versions: Adobe Flex SDK 3.2 (Release) > Environment: Affected OS(s): Windows > Affected OS(s): Windows > Browser: Internet Explorer 7.x > Language Found: English >Reporter: Adobe JIRA > Fix For: Apache Flex 4.10.0 > > > Steps to reproduce: > 1.var formatter:NumberFormatter = new NumberFormatter(); > 2.myLabel.text = formatter.format(1.3E-20); > 3. > > Actual Results: > 0.1 > > > Expected Results: > Either "0" or "0.0013" > > Workaround (if any): Create my own numberFormatter class? -- 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-25954) [TLF 2758977] - out of range RTE when color='red' - works when color=
[
https://issues.apache.org/jira/browse/FLEX-25954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-25954:
-
Labels: easytest (was: )
> [TLF 2758977] - out of range RTE when color='red' - works when color=
> --
>
> Key: FLEX-25954
> URL: https://issues.apache.org/jira/browse/FLEX-25954
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark: TextArea
>Affects Versions: Adobe Flex SDK Previous
> Environment: Affected OS(s): All OS Platforms
> Browser: Firefox 3.x
> Language Found: English
>Reporter: Adobe JIRA
>Priority: Minor
> Labels: easytest
> Fix For: Adobe Flex SDK Previous
>
>
> A watson bug has been filed - http://watsonexp.corp.adobe.com/#bug=2758977
> Problem:
> 'red' throws out of range RTE
> Method:
>
>
> http://ns.adobe.com/mxml/2009";
> xmlns:s="library://ns.adobe.com/flex/spark"
> xmlns:mx="library://ns.adobe.com/flex/halo">
>
>
>
>
>
>
>
> Para
>
>
>
>
> Result:
> Expected:
> In Flex SDK in the framework code we do lookup for these string values
> private var colorNames:Object =
> {
> transparent: "transparent",
> black: 0x00,
> blue: 0xFF,
> green: 0x008000,
> gray: 0x808080,
> silver: 0xC0C0C0,
> lime: 0x00FF00,
> olive: 0x808000,
> white: 0xFF,
> yellow: 0x00,
> maroon: 0x80,
> navy: 0x80,
> red: 0xFF,
> purple: 0x800080,
> teal: 0x008080,
> fuchsia: 0xFF00FF,
> aqua: 0x00,
> magenta: 0xFF00FF,
> cyan: 0x00,
>
> // IMPORTANT: Theme colors must also be updated
> // in the Flex compiler's CSS parser
> // (in \src\java\macromedia\css\Descriptor.java)
>
> it is colorNames in StyleManagerImpl
> in the framework directory
> Workaround:
>
> http://ns.adobe.com/mxml/2009";
> xmlns:s="library://ns.adobe.com/flex/spark"
> xmlns:mx="library://ns.adobe.com/flex/halo">
>
>
>
>
>
>
>
> Para
>
>
>
>
--
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-25884) Post Flex SDKs with AIR SDK pre-overlaid
[ https://issues.apache.org/jira/browse/FLEX-25884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649314#comment-13649314 ] Justin Mclean commented on FLEX-25884: -- Apache Flex this is not possible due to Apache/Adobe licensing issue. In Apache Flex scripts now exist for OSX for this (see .sh scripts in ide folder) for Flash Player and AIR. Looking for someone to code up window versions. > Post Flex SDKs with AIR SDK pre-overlaid > > > Key: FLEX-25884 > URL: https://issues.apache.org/jira/browse/FLEX-25884 > Project: Apache Flex > Issue Type: New Feature >Affects Versions: Adobe Flex SDK Previous > Environment: Language Found: English >Reporter: Adobe JIRA > -- 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-27968) Backing bug for #2819924 which is a request for TLF to add option to preserve caret/selection when text is set similiar to how TextField does it
[ https://issues.apache.org/jira/browse/FLEX-27968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649310#comment-13649310 ] Justin Mclean commented on FLEX-27968: -- Do we know if this has been fixed in current version of the Apache Flex SDK? Does anyone know what TLF Build 22 equivalent version number is? > Backing bug for #2819924 which is a request for TLF to add option to preserve > caret/selection when text is set similiar to how TextField does it > > > Key: FLEX-27968 > URL: https://issues.apache.org/jira/browse/FLEX-27968 > Project: Apache Flex > Issue Type: Task > Components: Spark: RichEditableText >Affects Versions: Adobe Flex SDK Previous > Environment: Language Found: English >Reporter: Adobe JIRA > Labels: easytest > > I am going to add the code to do this to RichEditable text. If/when TLF > implements it we should remove the code in RichEditableText and use the code > in TLF. -- 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-27968) Backing bug for #2819924 which is a request for TLF to add option to preserve caret/selection when text is set similiar to how TextField does it
[ https://issues.apache.org/jira/browse/FLEX-27968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-27968: - Labels: easytest (was: ) > Backing bug for #2819924 which is a request for TLF to add option to preserve > caret/selection when text is set similiar to how TextField does it > > > Key: FLEX-27968 > URL: https://issues.apache.org/jira/browse/FLEX-27968 > Project: Apache Flex > Issue Type: Task > Components: Spark: RichEditableText >Affects Versions: Adobe Flex SDK Previous > Environment: Language Found: English >Reporter: Adobe JIRA > Labels: easytest > > I am going to add the code to do this to RichEditable text. If/when TLF > implements it we should remove the code in RichEditableText and use the code > in TLF. -- 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-25986) i18n doesn't work with XML menuBu
[
https://issues.apache.org/jira/browse/FLEX-25986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-25986:
-
Labels: easytest (was: )
> i18n doesn't work with XML menuBu
> -
>
> Key: FLEX-25986
> URL: https://issues.apache.org/jira/browse/FLEX-25986
> Project: Apache Flex
> Issue Type: Bug
> Components: Data Binding
>Affects Versions: Adobe Flex SDK 4.1 (Release)
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Browser: Internet Explorer 7.x
> Language Found: French
>Reporter: Adobe JIRA
> Labels: easytest
>
> Steps to reproduce:
> Create a menu using i18n data binding like in this following code :
> var xmlContent:XML =
>
>state="one"/>
> 'an_other_i18n_title')}
> state="two"/>
>state="three"/>
> ;
> var paymentStack:ItemsForRenderer = new ItemsForRenderer();
> paymentStack.title = resourceManager.getString('i18n',
> 'topBar.firstTitle');
> paymentStack.itemName = "name";
>
> var stack:ItemsForRenderer = new ItemsForRenderer();
> stack.title = resourceManager.getString('i18n', 'topBar.secondTitle');
> stack.xml = xmlContent;
> stack.targetedView = this.uiPart;
> Define an ComboBox somwhere in your application that allows to switch in an
> other language.
>
> Actual Results:
> All the i18n label, button, etc. are updated but never the menu (and all its
> sub-menu).
>
>
> Expected Results:
> All i18n data have to be updated.
>
> Workaround (if any):
> No workaround found ! And that's the problem...
> Note : this bug appears on windows XP for both internet explorer (6 / 7 / 8)
> and firefox 3 versions. No idea for others browsers and OS.
--
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-26412) TLF 2.0: Html Importer fails to recognize as ordered list.
[ https://issues.apache.org/jira/browse/FLEX-26412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-26412: - Labels: easyfix easytest (was: ) > TLF 2.0: Html Importer fails to recognize as ordered list. > --- > > Key: FLEX-26412 > URL: https://issues.apache.org/jira/browse/FLEX-26412 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Framework >Affects Versions: Adobe Flex SDK Previous > Environment: Affected OS(s): All OS Platforms > Affected OS(s): All OS Platforms > Browser: Other (specify version) > Language Found: English >Reporter: Adobe JIRA > Labels: easyfix, easytest > > Steps to reproduce: > Using the Jan 07 2011 build of textLayout.swc (included in the test case > project): > var markup:XML = First ItemSecond Item; > var flow:TextFlow = TextConverter.importToFlow(markup, > TextConverter.TEXT_FIELD_HTML_FORMAT); > trace(flow.mxmlChildren[0].listStyleType); > flow.flowComposer.addController(new ContainerController(this, NaN, NaN)); > flow.flowComposer.updateAllControllers(); > > Actual Results: > The list is parsed and displayed with list.listStyleType == > ListStyleType.DISC. Console output is "disc" > > Expected Results: > The list is parsed and displayed with list.listStyleType == > ListStyleType.DECIMAL. Console output is "decimal" > > Workaround (if any): > TextFieldHtmlImporter.createListFromXML is checking if the element name > is "OL" without ensuring that the name was all caps before. > Changing line 395 in revision 349 of TextFieldHtmlImporter.as from: > var name:String = xmlToParse ? xmlToParse.name().localName : null; > to: > var name:String = xmlToParse ? > xmlToParse.name().localName.toUpperCase() : null; > corrects the issue. > Additionally, using all-caps element names gets around this bug. -- 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-26653) Missing space characters before and after span element (TLF 2 with Flex 4.1)
[ https://issues.apache.org/jira/browse/FLEX-26653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649308#comment-13649308 ] Justin Mclean commented on FLEX-26653: -- Still an issue in Apache Flex 4.9.1 > Missing space characters before and after span element (TLF 2 with Flex 4.1) > > > Key: FLEX-26653 > URL: https://issues.apache.org/jira/browse/FLEX-26653 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Framework >Affects Versions: Adobe Flex SDK 4.1 (Release) > Environment: Affected OS(s): Mac > Language Found: English >Reporter: Adobe JIRA > Labels: easytest > > Steps to reproduce: > 1. View the attached .swf file in a browser. > Actual Results: "spantext" > > Expected Results: "span text" > > (Something else: In "Components" in the bug form I'd like to be able to > select "TLF".) -- 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-26653) Missing space characters before and after span element (TLF 2 with Flex 4.1)
[ https://issues.apache.org/jira/browse/FLEX-26653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649307#comment-13649307 ] Justin Mclean edited comment on FLEX-26653 at 5/5/13 10:31 AM: --- Code to test http://ns.adobe.com/mxml/2009"; xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/mx" creationComplete="init()"> was (Author: jmclean): Code: http://ns.adobe.com/mxml/2009"; xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/mx" creationComplete="init()"> > Missing space characters before and after span element (TLF 2 with Flex 4.1) > > > Key: FLEX-26653 > URL: https://issues.apache.org/jira/browse/FLEX-26653 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Framework >Affects Versions: Adobe Flex SDK 4.1 (Release) > Environment: Affected OS(s): Mac > Language Found: English >Reporter: Adobe JIRA > Labels: easytest > > Steps to reproduce: > 1. View the attached .swf file in a browser. > Actual Results: "spantext" > > Expected Results: "span text" > > (Something else: In "Components" in the bug form I'd like to be able to > select "TLF".) -- 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-26653) Missing space characters before and after span element (TLF 2 with Flex 4.1)
[ https://issues.apache.org/jira/browse/FLEX-26653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649307#comment-13649307 ] Justin Mclean commented on FLEX-26653: -- Code: http://ns.adobe.com/mxml/2009"; xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/mx" creationComplete="init()"> > Missing space characters before and after span element (TLF 2 with Flex 4.1) > > > Key: FLEX-26653 > URL: https://issues.apache.org/jira/browse/FLEX-26653 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Framework >Affects Versions: Adobe Flex SDK 4.1 (Release) > Environment: Affected OS(s): Mac > Language Found: English >Reporter: Adobe JIRA > Labels: easytest > > Steps to reproduce: > 1. View the attached .swf file in a browser. > Actual Results: "spantext" > > Expected Results: "span text" > > (Something else: In "Components" in the bug form I'd like to be able to > select "TLF".) -- 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-26653) Missing space characters before and after span element (TLF 2 with Flex 4.1)
[ https://issues.apache.org/jira/browse/FLEX-26653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-26653: - Labels: easytest (was: ) > Missing space characters before and after span element (TLF 2 with Flex 4.1) > > > Key: FLEX-26653 > URL: https://issues.apache.org/jira/browse/FLEX-26653 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Framework >Affects Versions: Adobe Flex SDK 4.1 (Release) > Environment: Affected OS(s): Mac > Language Found: English >Reporter: Adobe JIRA > Labels: easytest > > Steps to reproduce: > 1. View the attached .swf file in a browser. > Actual Results: "spantext" > > Expected Results: "span text" > > (Something else: In "Components" in the bug form I'd like to be able to > select "TLF".) -- 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-26780) Minor bug in operation of radiusX and radiusY for rectangles
[
https://issues.apache.org/jira/browse/FLEX-26780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649306#comment-13649306
]
Justin Mclean commented on FLEX-26780:
--
Likely because of this code in Rect.as - there's no equiv clause if radiusY !=
0.
else if (radiusX != 0)
{
var rX:Number = radiusX;
var rY:Number = radiusY == 0 ? radiusX : radiusY;
g.drawRoundRect(drawX, drawY, width, height, rX * 2, rY * 2);
}
> Minor bug in operation of radiusX and radiusY for rectangles
>
>
> Key: FLEX-26780
> URL: https://issues.apache.org/jira/browse/FLEX-26780
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark: General Component
>Affects Versions: Adobe Flex SDK 4.5 (Release)
> Environment: Affected OS(s): Windows
> Affected OS(s):
> Browser: Opera
> Language Found: English
>Reporter: Adobe JIRA
>
> I was trying to understand radiusX and radiusY for s:Rect, and it did not
> behave as expected. After working with it for a while, it appears that the X
> property is bleeding over into the Y property. For example, try the code
> below, and a rounded rectangle still forms. But set radiusX="0", and
> radiusY="20", and no rounding occurs.
> If radiusX should truly bleed over into radiusY, this probably should be
> documented. As an aside, I found the Flex documentation on what these
> properties do insufficient to understand them. Finally note this confusion
> came out of the Flex in 1 Week training, in the Day 5 Excercise 5.8
> (Animating Button Components), where they set an X radius on the button but
> no Y value, and it worked fine. Thanks.
> Addendum: note this "bleeding" effect is on the other radius properties as
> well, e.g. topRightRadiusX.
>
>
>
> http://ns.adobe.com/mxml/2009";
>xmlns:s="library://ns.adobe.com/flex/spark">
>
>
>
>
>
>
>
>
>
>
>
--
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-27175) Default Spark Button Skin should have an adjustable minWidth
[
https://issues.apache.org/jira/browse/FLEX-27175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-27175:
-
Labels: easyfix easytest (was: )
> Default Spark Button Skin should have an adjustable minWidth
>
>
> Key: FLEX-27175
> URL: https://issues.apache.org/jira/browse/FLEX-27175
> Project: Apache Flex
> Issue Type: Improvement
> Components: Spark: Button
>Affects Versions: Adobe Flex SDK 4.5 (Release)
> Environment: Language Found: English
>Reporter: Adobe JIRA
> Labels: easyfix, easytest
>
> Per this posting:
> https://prerelease.adobe.com/project/forum/thread.html?cap=b4dd6eba22d848afbd7e0c95bd5eae0c&forid={E8AB0CF6-3479-4F80-96EB-C54C8C3C3919}&topid={066E493F-AF90-4CB2-ACB5-8DB0E5D4C4A5}
>
> The default Spark ButtonSkin.mxml should not have a static minimum width that
> is not associated with the actual ButtonSkin/Button's minWidth. Currently
> the 'border' portion of the default skin has a set width of 69:
> height="20" radiusX="2">
> This means that regardless of changing a button's minimum width, it will not
> get any smaller than 69 without either a re-skin or manually setting the
> width.
> Sample application from the post (image is attached):
>
> xmlns:fx = "http://ns.adobe.com/mxml/2009";
> xmlns:mx = "library://ns.adobe.com/flex/mx"
> xmlns:s = "library://ns.adobe.com/flex/spark">
>
>>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--
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-27315) Scroller Crash On Window Resize
[ https://issues.apache.org/jira/browse/FLEX-27315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-27315: - Labels: easytest (was: ) > Scroller Crash On Window Resize > --- > > Key: FLEX-27315 > URL: https://issues.apache.org/jira/browse/FLEX-27315 > Project: Apache Flex > Issue Type: Bug > Components: Spark: Scroller >Affects Versions: Adobe Flex SDK 4.5 (Release) > Environment: Affected OS(s): Windows > Affected OS(s): Windows 7 > Language Found: English >Reporter: Adobe JIRA > Labels: easytest > > Windows 7 64-bit > Mac OS X 10.6 > Steps to reproduce: > 1. Create a new Air project in Flash Builder 4.5 i6 > 2. Paste in the following code. > > http://ns.adobe.com/mxml/2009"; > > xmlns:s="library://ns.adobe.com/flex/spark" > > xmlns:mx="library://ns.adobe.com/flex/mx" > width="500" height="500" > showStatusBar="false"> > > >horizontalCenter="0" verticalCenter="0"> > > > > > > > > > > 3. Resize the window smaller in any direction. > > Actual Results: > Computer completely freezes and you have to open Task Manager to kill the > process. In Task Manager you can view the process is at 100% CPU usage. > Expected Results: > Window to resize without crashing. > > Workaround (if any): > Don't put a horizontally and vertically centred Group within the Scroller. -- 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-28966) Adobe hosted RSLs always fail due to crossdomain policy
[ https://issues.apache.org/jira/browse/FLEX-28966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-28966. -- Resolution: Won't Fix Or rather can't fix Adobe hosting issue (assuming issue still exist) not Apache Flex issue. > Adobe hosted RSLs always fail due to crossdomain policy > --- > > Key: FLEX-28966 > URL: https://issues.apache.org/jira/browse/FLEX-28966 > Project: Apache Flex > Issue Type: Bug > Components: Runtime Shared Libraries >Affects Versions: Adobe Flex SDK 4.1 (Release) > Environment: Affected OS(s): All OS Platforms > Affected OS(s): All OS Platforms > Language Found: English >Reporter: Adobe JIRA > > Steps to reproduce: > 1. Clear FP cached RSL via > http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager03.html > 2. Run a debug SWF that uses Adobe hosted RSLs > > Actual Results: > Every time I get the following error: Error: Ignoring policy file at > http://fpdownload.adobe.com/pub/swz/crossdomain.xml due to meta-policy > 'by-content-type'. > The Adobe hosted RSLs are not used and so the failover RSLs are always used. > > Expected Results: > I would expect the Adobe hosted RSLs to be used. At least most of the time. > > Workaround (if any): > Having proper failovers does what it's supposed to. > Also I noticed that the master crossdomain file at > http://fpdownload.adobe.com/crossdomain.xml > ...contains: > > And the crossdomain for the RSLs at > http://fpdownload.adobe.com/pub/swz/crossdomain.xml > ... is served with content type "text/xml". According to the docs it should > be served with "text/x-cross-domain-policy". -- 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-17574) SimpleXMLEncoder.encodeValue() should check parentNode=null case
[
https://issues.apache.org/jira/browse/FLEX-17574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-17574:
-
Labels: easyfix easytest (was: )
> SimpleXMLEncoder.encodeValue() should check parentNode=null case
>
>
> Key: FLEX-17574
> URL: https://issues.apache.org/jira/browse/FLEX-17574
> Project: Apache Flex
> Issue Type: Bug
> Components: RPC: General
>Affects Versions: Adobe Flex SDK 3.3 (Release)
> Environment: Affected OS(s): All OS Platforms
> Language Found: English
>Reporter: Adobe JIRA
>Priority: Minor
> Labels: easyfix, easytest
>
> Steps to reproduce:
> 1. pass a null object to SimpleXMLEncoder.encodeValue() call, for example:
> var result:XMLNode = encoder.encodeValue(myXMLDoc,new QName(new
> Namespace("xmlns", "http://www.namespace1.com";),"ns1"),null);
>
>
> Actual Results:
> receives run time error:
> TypeError: Error #1009: Cannot access a property or method of a null object
> reference.
>
> Expected Results:
> add a conditional checking for parentNode=null case.
> should we check qname=null as well?
>
> 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-27476) XMLEncoder.isSimpleValue() method fails to detect decoded simpleContent objects correctly
[
https://issues.apache.org/jira/browse/FLEX-27476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-27476:
-
Labels: easyfix easytest (was: )
> XMLEncoder.isSimpleValue() method fails to detect decoded simpleContent
> objects correctly
> -
>
> Key: FLEX-27476
> URL: https://issues.apache.org/jira/browse/FLEX-27476
> Project: Apache Flex
> Issue Type: Bug
> Components: RPC: General
>Affects Versions: Adobe Flex SDK 4.1 (Release)
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Language Found: English
>Reporter: Adobe JIRA
> Labels: easyfix, easytest
>
> Steps to reproduce:
> 1. Decode and then re-encode an XML file containing an element with
> using XMLDecoder and XMLEncoder.
> The re-encoded XML should match the original source XML.
> (See code example at bottom of description)
>
> Actual Results:
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
>
> Expected Results:
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>bar
>
>
> Workaround (if any):
>
> XMLDecoder uses mx.rpc.xml.SimpleContent internally to decode simple content
> into a dynamic object that behaves like a String (by overriding the valueOf
> and toString methods)
> XMLEncoder.isSimpleValue incorrectly evaluates these objects to false. This
> can be fixed by checking the type against value.valueOf() rather than just
> the value
> public function isSimpleValue(value:*):Boolean
> {
> value:* = value.valueOf();//this is change required
> if (value is String || value is Number || value is Boolean
> || value is Date || value is int || value is uint
> || value is ByteArray)
> {
> return true;
> }
> return false;
> }
> Example Source:
>
>xmlns:fx="http://ns.adobe.com/mxml/2009";
> xmlns:mx="library://ns.adobe.com/flex/mx"
> xmlns:s="library://ns.adobe.com/flex/spark"
> creationComplete="application1_creationCompleteHandler(event)"
> minWidth="955" minHeight="600">
>
> >
>
>
>
>
> xmlns:xs="http://www.w3.org/2001/XMLSchema";
> elementFormDefault="qualified">
>
>
>
>base="xs:string">
>name="id" type="xs:string" />
>
>
>
>
>
>
>
> bar
>
>
>
>
--
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-13695) setting rotation to 0 is broken
[
https://issues.apache.org/jira/browse/FLEX-13695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean resolved FLEX-13695.
--
Resolution: Cannot Reproduce
Can't reproduce with spark or mx components. Checked all set rotation methods
none do anything special with 0.
> setting rotation to 0 is broken
> ---
>
> Key: FLEX-13695
> URL: https://issues.apache.org/jira/browse/FLEX-13695
> Project: Apache Flex
> Issue Type: Bug
> Components: Layout - General
>Affects Versions: Adobe Flex SDK Previous
> Environment: Affected OS(s): All OS Platforms
> Language Found: English
>Reporter: Adobe JIRA
>
> Steps to reproduce:
> 1. create a element
> 2. element.setFocus(true)
> 3. element.rotation = 10
> 4. element.rotation = 0
>
> Actual Results:
> focusBox is still 10 rad rotated
>
> Expected Results:
> focusBox should be not rotated
>
> Workaround (if any):
>
> overwrite rotation function on your element:
> public function set rotation(rot:Number):void {
>if(rot == 0) {
> super.rotation = 0.001;
> }
> super.rotation = rot;
> }
> there seems to be a test if rot is true or != 0 to test if rotation should be
> processed,. however rotation = 0 is still a valid and usefull value and
> should update the internal stats.
> we suspect that this bug also causes the problem that rotated elments cause
> the focusbox to be rotated when the focus switches to a element which has
> rotation 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-27652) DateChooser displays incorrect month label
[ https://issues.apache.org/jira/browse/FLEX-27652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-27652: - Labels: easyfix easytest (was: ) > DateChooser displays incorrect month label > -- > > Key: FLEX-27652 > URL: https://issues.apache.org/jira/browse/FLEX-27652 > Project: Apache Flex > Issue Type: Bug > Components: mx: DateChooser >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: easyfix, easytest > > Steps to reproduce: > 1. Open the attached project and run > 2. Click the button > 3. DateChooser displayed as a popup, current year and calendar correct, but > month label incorrect > 4. Return to project and uncomment line 19, then repeat steps 1-3 > 5. Note now that month displays correctly > > Actual Results: > Instead of the current month displaying in the label, the label displays > "September". This is because September is the longest month in terms of > number of characters, and text fields text property is set to this value > during setMonthWidth, but never reset back to original value. > > Expected Results: > Label displays correct month > > Workaround (if any): > Need to call invalidateDisplayList on the DateChooser at a later time -- 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-27652) DateChooser displays incorrect month label
[ https://issues.apache.org/jira/browse/FLEX-27652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649253#comment-13649253 ] Justin Mclean commented on FLEX-27652: -- Also note September may not be longest month in other locales. > DateChooser displays incorrect month label > -- > > Key: FLEX-27652 > URL: https://issues.apache.org/jira/browse/FLEX-27652 > Project: Apache Flex > Issue Type: Bug > Components: mx: DateChooser >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: easyfix, easytest > > Steps to reproduce: > 1. Open the attached project and run > 2. Click the button > 3. DateChooser displayed as a popup, current year and calendar correct, but > month label incorrect > 4. Return to project and uncomment line 19, then repeat steps 1-3 > 5. Note now that month displays correctly > > Actual Results: > Instead of the current month displaying in the label, the label displays > "September". This is because September is the longest month in terms of > number of characters, and text fields text property is set to this value > during setMonthWidth, but never reset back to original value. > > Expected Results: > Label displays correct month > > Workaround (if any): > Need to call invalidateDisplayList on the DateChooser at a later time -- 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-14450) NumberValidator maxValue/minValue don't work with non-english settings
[ https://issues.apache.org/jira/browse/FLEX-14450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-14450. -- Resolution: Fixed Fix Version/s: Apache Flex 4.10.0 Recent fixes have fixed this. > NumberValidator maxValue/minValue don't work with non-english settings > -- > > Key: FLEX-14450 > URL: https://issues.apache.org/jira/browse/FLEX-14450 > Project: Apache Flex > Issue Type: Bug > Components: Validators >Affects Versions: Adobe Flex SDK 3.0 (Release) > Environment: Affected OS(s): Windows > Affected OS(s): Windows XP > Browser: Internet Explorer 6.x > Language Found: English >Reporter: Adobe JIRA >Priority: Minor > Labels: easyfix, easytest > Fix For: Apache Flex 4.10.0 > > > Steps to reproduce: > 1. Paste this code in an MXML application: > > minValue="500" maxValue="1000" > decimalSeparator="," thousandsSeparator="." /> > 2. Try to enter the values "300" and "1200", and verify that the validator > fails (correctly). > 3. Try to enter the values "300,00" and "1200,00", and verify that the > validator does not fail. > > Actual Results: > The invalid values are allowed. > > Expected Results: > NumberValidator should fail validating "300,00" and "1200,00" with the > decimalSeparator and the thousandsSeparator set like in the example. > > Workaround (if any): > Subclassing the NumberValidator and implementing correctly the check. > > The bug is at line 295 of NumberValidator.as: >var x:Number = Number(input); > This way, the input (which is a String, see line 1054 of the same source > file) get parsed using the dot as the decimal separator. Doing this on a > String like "300,00" or "1200,00" results in a NaN. Subsequent check will > then fail on this value. -- 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-11930) Inproper condition for IF statement
[
https://issues.apache.org/jira/browse/FLEX-11930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649249#comment-13649249
]
Justin Mclean commented on FLEX-11930:
--
Confirmed still an issue in ApacheFlex 4.9.1
Perhaps line should be this?
else if (!parentBoundariesTB)
> 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
>
> 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] [Comment Edited] (FLEX-24764) Applying NumberFormatter.format() to 17.76 returns the incorrect value
[
https://issues.apache.org/jira/browse/FLEX-24764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649247#comment-13649247
]
Justin Mclean edited comment on FLEX-24764 at 5/5/13 2:53 AM:
--
Ouch - how long has this been a bug? Fixed and checked into develop branch.
Mustella formatter tests pass.
Issue was not Number conversion/rounding as this code also produced the error
in both cases tracing "17.77".
var nf:mx.formatters.NumberFormatter = new mx.formatters.NumberFormatter();
nf.precision = 2;
nf.rounding = "up";
var formatted:String = nf.format(17.76);
trace(formatted);
var formatted:String = nf.format("17.76");
trace(formatted);
was (Author: jmclean):
Ouch - how long has this been a bug? Fixed and checked into develop branch.
Mustella formatter tests pass.
Issue was not Number convert ion as this code also produced the error:
var nf:mx.formatters.NumberFormatter = new mx.formatters.NumberFormatter();
nf.precision = 2;
nf.rounding = "up";
var formatted:String = nf.format(17.76);
trace(formatted);
> Applying NumberFormatter.format() to 17.76 returns the incorrect value
> --
>
> Key: FLEX-24764
> URL: https://issues.apache.org/jira/browse/FLEX-24764
> Project: Apache Flex
> Issue Type: Bug
> Components: Formatters
>Affects Versions: Adobe Flex SDK Previous
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Browser: Other (specify version)
> Language Found: English
>Reporter: Adobe JIRA
>Assignee: Justin Mclean
> Fix For: Apache Flex 4.10.0
>
>
> {*** ORIGINALLY POSTED AS ALS-71 ; WAS REQUESTED TO POST IT HERE INSTEAD ***}
> Steps to reproduce:
> 1. setup a new NumberFormatter() instance, setting the precision to 2 and the
> rounding to "up":
> var nf:NumberFormatter = new NumberFormatter();
> nf.precision = 2;
> nf.rounding = "up";
> 2. Create a var to format the number 17.76:
> var num:Number = new Number( nf.format(17.76) );
> 3. Trace the result:
> trace(num);
>
> Actual Results: 17.77
>
> Expected Results: 17.76
> In my application my actual number starts out to a precision of 3 (17.760),
> but either way I get the same result. Other numbers do not seem to have this
> issue. I even tried 18.76, 17.77, 17.75, they all correctly round back to
> themselves (because the 3 digit would be interpreted as a 0 ).
> I have run into other issues where my number was divided by another and the
> result would be something like 13.70001, and even though my interface
> only shows 13.70, the rounded correctly formats it to 13.71. However with
> this 17.76 number that doesn't seem to be the case.
> If this is not a bug, but rather a binary math error please explain why this
> number is specifically having the issue so I can relay that to my client.
> Specs:
> Eclipse 3.4.2
> Flash Builder 4.0 (build 272416) plugin
> Project is using the Flex 3.5 SDK
>
> Workaround (if any):
> Add logic to check to see if the value is 17.76 and not format it if it is
--
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-24764) Applying NumberFormatter.format() to 17.76 returns the incorrect value
[
https://issues.apache.org/jira/browse/FLEX-24764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean resolved FLEX-24764.
--
Resolution: Fixed
Fix Version/s: Apache Flex 4.10.0
Ouch - how long has this been a bug? Fixed and checked into develop branch.
Mustella formatter tests pass.
Issue was not Number convert ion as this code also produced the error:
var nf:mx.formatters.NumberFormatter = new mx.formatters.NumberFormatter();
nf.precision = 2;
nf.rounding = "up";
var formatted:String = nf.format(17.76);
trace(formatted);
> Applying NumberFormatter.format() to 17.76 returns the incorrect value
> --
>
> Key: FLEX-24764
> URL: https://issues.apache.org/jira/browse/FLEX-24764
> Project: Apache Flex
> Issue Type: Bug
> Components: Formatters
>Affects Versions: Adobe Flex SDK Previous
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Browser: Other (specify version)
> Language Found: English
>Reporter: Adobe JIRA
>Assignee: Justin Mclean
> Fix For: Apache Flex 4.10.0
>
>
> {*** ORIGINALLY POSTED AS ALS-71 ; WAS REQUESTED TO POST IT HERE INSTEAD ***}
> Steps to reproduce:
> 1. setup a new NumberFormatter() instance, setting the precision to 2 and the
> rounding to "up":
> var nf:NumberFormatter = new NumberFormatter();
> nf.precision = 2;
> nf.rounding = "up";
> 2. Create a var to format the number 17.76:
> var num:Number = new Number( nf.format(17.76) );
> 3. Trace the result:
> trace(num);
>
> Actual Results: 17.77
>
> Expected Results: 17.76
> In my application my actual number starts out to a precision of 3 (17.760),
> but either way I get the same result. Other numbers do not seem to have this
> issue. I even tried 18.76, 17.77, 17.75, they all correctly round back to
> themselves (because the 3 digit would be interpreted as a 0 ).
> I have run into other issues where my number was divided by another and the
> result would be something like 13.70001, and even though my interface
> only shows 13.70, the rounded correctly formats it to 13.71. However with
> this 17.76 number that doesn't seem to be the case.
> If this is not a bug, but rather a binary math error please explain why this
> number is specifically having the issue so I can relay that to my client.
> Specs:
> Eclipse 3.4.2
> Flash Builder 4.0 (build 272416) plugin
> Project is using the Flex 3.5 SDK
>
> Workaround (if any):
> Add logic to check to see if the value is 17.76 and not format it if it is
--
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-24764) Applying NumberFormatter.format() to 17.76 returns the incorrect value
[
https://issues.apache.org/jira/browse/FLEX-24764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649242#comment-13649242
]
Justin Mclean commented on FLEX-24764:
--
Still an issue in Apache Flex 4.9.1 / develop branch.
> Applying NumberFormatter.format() to 17.76 returns the incorrect value
> --
>
> Key: FLEX-24764
> URL: https://issues.apache.org/jira/browse/FLEX-24764
> Project: Apache Flex
> Issue Type: Bug
> Components: Formatters
>Affects Versions: Adobe Flex SDK Previous
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Browser: Other (specify version)
> Language Found: English
>Reporter: Adobe JIRA
>
> {*** ORIGINALLY POSTED AS ALS-71 ; WAS REQUESTED TO POST IT HERE INSTEAD ***}
> Steps to reproduce:
> 1. setup a new NumberFormatter() instance, setting the precision to 2 and the
> rounding to "up":
> var nf:NumberFormatter = new NumberFormatter();
> nf.precision = 2;
> nf.rounding = "up";
> 2. Create a var to format the number 17.76:
> var num:Number = new Number( nf.format(17.76) );
> 3. Trace the result:
> trace(num);
>
> Actual Results: 17.77
>
> Expected Results: 17.76
> In my application my actual number starts out to a precision of 3 (17.760),
> but either way I get the same result. Other numbers do not seem to have this
> issue. I even tried 18.76, 17.77, 17.75, they all correctly round back to
> themselves (because the 3 digit would be interpreted as a 0 ).
> I have run into other issues where my number was divided by another and the
> result would be something like 13.70001, and even though my interface
> only shows 13.70, the rounded correctly formats it to 13.71. However with
> this 17.76 number that doesn't seem to be the case.
> If this is not a bug, but rather a binary math error please explain why this
> number is specifically having the issue so I can relay that to my client.
> Specs:
> Eclipse 3.4.2
> Flash Builder 4.0 (build 272416) plugin
> Project is using the Flex 3.5 SDK
>
> Workaround (if any):
> Add logic to check to see if the value is 17.76 and not format it if it is
--
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] [Assigned] (FLEX-24764) Applying NumberFormatter.format() to 17.76 returns the incorrect value
[
https://issues.apache.org/jira/browse/FLEX-24764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean reassigned FLEX-24764:
Assignee: Justin Mclean
> Applying NumberFormatter.format() to 17.76 returns the incorrect value
> --
>
> Key: FLEX-24764
> URL: https://issues.apache.org/jira/browse/FLEX-24764
> Project: Apache Flex
> Issue Type: Bug
> Components: Formatters
>Affects Versions: Adobe Flex SDK Previous
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Browser: Other (specify version)
> Language Found: English
>Reporter: Adobe JIRA
>Assignee: Justin Mclean
>
> {*** ORIGINALLY POSTED AS ALS-71 ; WAS REQUESTED TO POST IT HERE INSTEAD ***}
> Steps to reproduce:
> 1. setup a new NumberFormatter() instance, setting the precision to 2 and the
> rounding to "up":
> var nf:NumberFormatter = new NumberFormatter();
> nf.precision = 2;
> nf.rounding = "up";
> 2. Create a var to format the number 17.76:
> var num:Number = new Number( nf.format(17.76) );
> 3. Trace the result:
> trace(num);
>
> Actual Results: 17.77
>
> Expected Results: 17.76
> In my application my actual number starts out to a precision of 3 (17.760),
> but either way I get the same result. Other numbers do not seem to have this
> issue. I even tried 18.76, 17.77, 17.75, they all correctly round back to
> themselves (because the 3 digit would be interpreted as a 0 ).
> I have run into other issues where my number was divided by another and the
> result would be something like 13.70001, and even though my interface
> only shows 13.70, the rounded correctly formats it to 13.71. However with
> this 17.76 number that doesn't seem to be the case.
> If this is not a bug, but rather a binary math error please explain why this
> number is specifically having the issue so I can relay that to my client.
> Specs:
> Eclipse 3.4.2
> Flash Builder 4.0 (build 272416) plugin
> Project is using the Flex 3.5 SDK
>
> Workaround (if any):
> Add logic to check to see if the value is 17.76 and not format it if it is
--
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-27546) "Parameter initializer unknown or is not a compile-time constant" for Number.MIN_VALUE
[ https://issues.apache.org/jira/browse/FLEX-27546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-27546: - Labels: easytest (was: ) > "Parameter initializer unknown or is not a compile-time constant" for > Number.MIN_VALUE > -- > > Key: FLEX-27546 > URL: https://issues.apache.org/jira/browse/FLEX-27546 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Compiler >Affects Versions: Adobe Flex SDK 4.5 (Release) > Environment: Affected OS(s): Windows > Affected OS(s): Windows 7 > Language Found: English >Reporter: Adobe JIRA > Labels: easytest > > Steps to reproduce: > Try to compile just this mxml snippet using the Flex 4.5 SDK: > > http://ns.adobe.com/mxml/2009"; > xmlns:s="library://ns.adobe.com/flex/spark"> >> > > > Actual Results: > Compiler Error: "Parameter initializer unknown or is not a compile-time > constant." > If *just* this mxml application is compiled, this can be reproduced > consistently. However, if other classes/.swcs are added as dependencies, the > same code might actually compile even with the 4.5 SDK. > > Expected Results: > This should compile just fine - it does when using the Flex 4.1 SDK. > > > 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-16885) Math.atan2() arguments are inverted in playerglobal.swc
[ https://issues.apache.org/jira/browse/FLEX-16885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-16885. -- Resolution: Won't Fix Fix Version/s: Apache Flex 4.10.0 Or rather can't fix this is a Flash Player issue not an Apache Flex issue. > Math.atan2() arguments are inverted in playerglobal.swc > --- > > Key: FLEX-16885 > URL: https://issues.apache.org/jira/browse/FLEX-16885 > Project: Apache Flex > Issue Type: Bug > Components: ASDoc Content >Affects Versions: Adobe Flex SDK 3.2 (Release) > Environment: Affected OS(s): Windows > Affected OS(s): Windows XP > Language Found: English >Reporter: Adobe JIRA > Fix For: Apache Flex 4.10.0 > > > Math.atan2() arguments are inverted in playerglobal.swc > //currently is: > final public static function atan2(x : Number, y : Number) : Number; > //should be: > final public static function atan2(y : Number, x : Number) : Number; -- 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-27191) playerglobal.swc for FlashPlayer 10.1 (and 10.2) contains invalid Number.MIN_VALUE
[ https://issues.apache.org/jira/browse/FLEX-27191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-27191. -- Resolution: Won't Fix OR rather can't fix not an old Player Player issue not Apache Flex issue. > playerglobal.swc for FlashPlayer 10.1 (and 10.2) contains invalid > Number.MIN_VALUE > -- > > Key: FLEX-27191 > URL: https://issues.apache.org/jira/browse/FLEX-27191 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Compiler >Affects Versions: Adobe Flex SDK 4.1 (Release) > Environment: Affected OS(s): All OS Platforms > Affected OS(s): All OS Platforms > Language Found: English >Reporter: Adobe JIRA > > Steps to reproduce: > 1. Compile file in attachment with selected FlashPlayer version 10.1(or 10.2) > > Actual Results: > Result is NaN > > Expected Results: >4.9406564584124654e-324 > Affects Flex SDK 4.1 and also 4.5 -- 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-20186) Number multiplication Number
[ https://issues.apache.org/jira/browse/FLEX-20186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-20186. -- Resolution: Not A Problem Fix Version/s: Apache Flex 4.10.0 Number multiplication may not give exact results due to rounding issued - this is a Flash Player issue not an Apache Flex issue. Easy workaround is it use a number formatter. > Number multiplication Number > > > Key: FLEX-20186 > URL: https://issues.apache.org/jira/browse/FLEX-20186 > Project: Apache Flex > Issue Type: Bug > Components: mx: Label >Affects Versions: Adobe Flex SDK 3.3 (Release) > Environment: Affected OS(s): Windows > Affected OS(s): Windows XP > Language Found: Chinese, Simplified >Reporter: Adobe JIRA > Fix For: Apache Flex 4.10.0 > > > Steps to reproduce: > 1. > Actual Results: > the result is 2.0996 > > Expected Results: > the result is 2.1 > > 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-16463) Int instead of Number
[ https://issues.apache.org/jira/browse/FLEX-16463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-16463. -- Resolution: Not A Problem Fix Version/s: Apache Flex 4.10.0 Possibly a Flash Builder issue and if so not an Apache Flex issue. Number behave in ActionScript as you expect (most of the time). eg This displays a number. var num1:Number = 2.3; var num2:Number = 4.7; trace(num1/num2); > Int instead of Number > - > > Key: FLEX-16463 > URL: https://issues.apache.org/jira/browse/FLEX-16463 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Framework >Affects Versions: Adobe Flex SDK 3.2 (Release) > Environment: Affected OS(s): Windows > Affected OS(s): > Browser: Internet Explorer 7.x > Language Found: English >Reporter: Adobe JIRA > Fix For: Apache Flex 4.10.0 > > > Steps to reproduce: > 1.define two numbers, first smaller than second one > 2.debug them, (try divide them in expression watch) > 3.try other combinations... you will receive int on evry step so you have to > fake your compiler if you like to get proper values... > > Actual Results: > Bug in watch, often also in-code calculations > > Expected Results: > Numbers works like floats not intigers > > 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-21501) ObjectUtil.copy fails to copy objects that have key == null (it copies only half of the original object)
[ https://issues.apache.org/jira/browse/FLEX-21501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-21501. -- Resolution: Not A Problem Fix Version/s: Apache Flex 4.10.0 Resolved in previous version of SDK - well almost. obj[''] =null will not be copied but all other keys will be, as it's very unlikely that obj[''] = null means anything and that it's using writeObject/readObject to copy (ie it's a Flash Player issue) I think it's ok to resolve this bug. > ObjectUtil.copy fails to copy objects that have key == null (it copies only > half of the original object) > > > Key: FLEX-21501 > URL: https://issues.apache.org/jira/browse/FLEX-21501 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Framework >Affects Versions: Adobe Flex SDK 3.4 (Release) > Environment: Affected OS(s): All OS Platforms > Affected OS(s): All OS Platforms > Language Found: English >Reporter: Adobe JIRA > Fix For: Apache Flex 4.10.0 > > > hey guys! great work! I love flex/as3 while i just simply never found a way > to comprehend as2. > Germans love to flex. > And i would be glad if i can help make it even better. > I did a crazy thing and ended up having an key null in an object. > now i used ObjectUtil.copy to copy that object to make an independent copy. > but it would only copy all properties until reaching the property 'null' and > then aborts copying. > which results in object-copies that are only half-copied. > i guess many more flex-functions can not handle objects that have key == > null. > attached u will find an example flex-project that reproduces the error and > also shows an workaround that i am currently using. > hope it helps and mostly: get's the job done! ;) > keep it up. -- 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-20030) ObjectUtil.copy() does not copy a string property
[
https://issues.apache.org/jira/browse/FLEX-20030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-20030:
-
Summary: ObjectUtil.copy() does not copy a string property (was:
ObjectUtil.cop() does not copy a string property)
> ObjectUtil.copy() does not copy a string property
> -
>
> Key: FLEX-20030
> URL: https://issues.apache.org/jira/browse/FLEX-20030
> Project: Apache Flex
> Issue Type: Bug
> Components: Runtime Exceptions
>Affects Versions: Adobe Flex SDK 3.3 (Release)
> Environment: Affected OS(s): Windows
> Affected OS(s): Windows XP
> Browser: Internet Explorer 7.x
> Language Found: English
>Reporter: Adobe JIRA
>
> I am facing a intermittent cloning problem. I am using the ObjectUtil.copy()
> method to clone my object. It is not a deep object. It has some string and
> boolean values. No nested object.
> I have noticed that one of the property called "nameT" does not copy over
> into the cloned object. I am seeing this behavior once in 7-8 times. I have
> never seen such a behavior in the past. It is difficult to reproduce this
> problem but I went into the debug mode and I have attached a screen shot.
> I understand it is difficult to help in a scenario where I cannot provide any
> sample app. But can you guys at Adobe guess what must be causing this issue?
> BTW, these are the 2 lines of code which are also part of my class ...
> registerClassAlias("FilterCode", com.FilterCode);
> public var nameT:String = "";
--
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-26325) RemoteObject logs too eagerly all sent messages
[
https://issues.apache.org/jira/browse/FLEX-26325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649057#comment-13649057
]
Justin Mclean commented on FLEX-26325:
--
No problem the code in the debug toString could use a little care anyway -
there are some obvious minor speed ups.
> RemoteObject logs too eagerly all sent messages
> ---
>
> Key: FLEX-26325
> URL: https://issues.apache.org/jira/browse/FLEX-26325
> Project: Apache Flex
> Issue Type: Bug
> Components: RPC: RemoteObject
>Affects Versions: Adobe Flex SDK 4.1 (Release)
> Environment: Affected OS(s): All OS Platforms
> Language Found: English
>Reporter: Adobe JIRA
>Assignee: Adobe JIRA
> Labels: easyfix
>
> Steps to reproduce:
> 1. Set debug level on any Logger in the application (not even necessarily on
> mx.rpc.*)
> 2. Call a remote operation with a RemoteObject sending a complex object
> graph, or an object graph containing 'lazy loaded' data, e.g. with LCDS or
> GraniteDS
>
> Actual Results:
> RemoteObject computes the complete debug message in RPCObjectUtils by the
> ultra slow AS3 reflection (even when the message will never be logged at
> all), and consequently triggers all lazy initializations (for example by
> accessing all lazyCollection.length properties on all the object graph).
> See here for more details on the issue:
> http://insideria.com/2010/10/flex-rpc-and-the-broken-mxlogg.html
>
> Expected Results:
> No computation of the debug message should be done when mx.rpc is not in
> debug mode.
> At least provide one of these options :
> - Allow adding manually excluded properties in
> RPCObjectUtils.defaultToStringExcludes (make it public or add a function
> addDefaultExclude)
> - Use existing toString() methods on objects when available instead of always
> relying on AS3 reflection
> - Provide a way to completely override the default RPCObjectUtil.toString,
> i.e.
> public var toStringFunction:Function;
> public static function toString(value:Object,
> namespaceURIs:Array = null,
> exclude:Array = null):String
> {
> if (toStringFunction != null) {
> return toStringFunction(value, namespaceURIs, exclude);
> }
> if (exclude == null)
> {
> exclude = defaultToStringExcludes;
> }
>
> refCount = 0;
> return internalToString(value, 0, null, namespaceURIs, exclude);
> }
>
> Workaround (if any):
>
> Never set any debug level on any Logger.
--
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-26325) RemoteObject logs too eagerly all sent messages
[
https://issues.apache.org/jira/browse/FLEX-26325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649049#comment-13649049
]
Justin Mclean commented on FLEX-26325:
--
Just attach your monkey path and I'll take a look at it. The key caching
probably has the same issue as this FLEX-18697 which may speed it up if fixed.
> RemoteObject logs too eagerly all sent messages
> ---
>
> Key: FLEX-26325
> URL: https://issues.apache.org/jira/browse/FLEX-26325
> Project: Apache Flex
> Issue Type: Bug
> Components: RPC: RemoteObject
>Affects Versions: Adobe Flex SDK 4.1 (Release)
> Environment: Affected OS(s): All OS Platforms
> Language Found: English
>Reporter: Adobe JIRA
>Assignee: Adobe JIRA
> Labels: easyfix
>
> Steps to reproduce:
> 1. Set debug level on any Logger in the application (not even necessarily on
> mx.rpc.*)
> 2. Call a remote operation with a RemoteObject sending a complex object
> graph, or an object graph containing 'lazy loaded' data, e.g. with LCDS or
> GraniteDS
>
> Actual Results:
> RemoteObject computes the complete debug message in RPCObjectUtils by the
> ultra slow AS3 reflection (even when the message will never be logged at
> all), and consequently triggers all lazy initializations (for example by
> accessing all lazyCollection.length properties on all the object graph).
> See here for more details on the issue:
> http://insideria.com/2010/10/flex-rpc-and-the-broken-mxlogg.html
>
> Expected Results:
> No computation of the debug message should be done when mx.rpc is not in
> debug mode.
> At least provide one of these options :
> - Allow adding manually excluded properties in
> RPCObjectUtils.defaultToStringExcludes (make it public or add a function
> addDefaultExclude)
> - Use existing toString() methods on objects when available instead of always
> relying on AS3 reflection
> - Provide a way to completely override the default RPCObjectUtil.toString,
> i.e.
> public var toStringFunction:Function;
> public static function toString(value:Object,
> namespaceURIs:Array = null,
> exclude:Array = null):String
> {
> if (toStringFunction != null) {
> return toStringFunction(value, namespaceURIs, exclude);
> }
> if (exclude == null)
> {
> exclude = defaultToStringExcludes;
> }
>
> refCount = 0;
> return internalToString(value, 0, null, namespaceURIs, exclude);
> }
>
> Workaround (if any):
>
> Never set any debug level on any Logger.
--
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-26325) RemoteObject logs too eagerly all sent messages
[
https://issues.apache.org/jira/browse/FLEX-26325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649042#comment-13649042
]
Justin Mclean commented on FLEX-26325:
--
Can you provide monkey patch as a diff patch?
> RemoteObject logs too eagerly all sent messages
> ---
>
> Key: FLEX-26325
> URL: https://issues.apache.org/jira/browse/FLEX-26325
> Project: Apache Flex
> Issue Type: Bug
> Components: RPC: RemoteObject
>Affects Versions: Adobe Flex SDK 4.1 (Release)
> Environment: Affected OS(s): All OS Platforms
> Language Found: English
>Reporter: Adobe JIRA
>Assignee: Adobe JIRA
> Labels: easyfix
>
> Steps to reproduce:
> 1. Set debug level on any Logger in the application (not even necessarily on
> mx.rpc.*)
> 2. Call a remote operation with a RemoteObject sending a complex object
> graph, or an object graph containing 'lazy loaded' data, e.g. with LCDS or
> GraniteDS
>
> Actual Results:
> RemoteObject computes the complete debug message in RPCObjectUtils by the
> ultra slow AS3 reflection (even when the message will never be logged at
> all), and consequently triggers all lazy initializations (for example by
> accessing all lazyCollection.length properties on all the object graph).
> See here for more details on the issue:
> http://insideria.com/2010/10/flex-rpc-and-the-broken-mxlogg.html
>
> Expected Results:
> No computation of the debug message should be done when mx.rpc is not in
> debug mode.
> At least provide one of these options :
> - Allow adding manually excluded properties in
> RPCObjectUtils.defaultToStringExcludes (make it public or add a function
> addDefaultExclude)
> - Use existing toString() methods on objects when available instead of always
> relying on AS3 reflection
> - Provide a way to completely override the default RPCObjectUtil.toString,
> i.e.
> public var toStringFunction:Function;
> public static function toString(value:Object,
> namespaceURIs:Array = null,
> exclude:Array = null):String
> {
> if (toStringFunction != null) {
> return toStringFunction(value, namespaceURIs, exclude);
> }
> if (exclude == null)
> {
> exclude = defaultToStringExcludes;
> }
>
> refCount = 0;
> return internalToString(value, 0, null, namespaceURIs, exclude);
> }
>
> Workaround (if any):
>
> Never set any debug level on any Logger.
--
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-26325) RemoteObject logs too eagerly all sent messages
[
https://issues.apache.org/jira/browse/FLEX-26325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-26325:
-
Labels: easyfix (was: )
> RemoteObject logs too eagerly all sent messages
> ---
>
> Key: FLEX-26325
> URL: https://issues.apache.org/jira/browse/FLEX-26325
> Project: Apache Flex
> Issue Type: Bug
> Components: RPC: RemoteObject
>Affects Versions: Adobe Flex SDK 4.1 (Release)
> Environment: Affected OS(s): All OS Platforms
> Language Found: English
>Reporter: Adobe JIRA
>Assignee: Adobe JIRA
> Labels: easyfix
>
> Steps to reproduce:
> 1. Set debug level on any Logger in the application (not even necessarily on
> mx.rpc.*)
> 2. Call a remote operation with a RemoteObject sending a complex object
> graph, or an object graph containing 'lazy loaded' data, e.g. with LCDS or
> GraniteDS
>
> Actual Results:
> RemoteObject computes the complete debug message in RPCObjectUtils by the
> ultra slow AS3 reflection (even when the message will never be logged at
> all), and consequently triggers all lazy initializations (for example by
> accessing all lazyCollection.length properties on all the object graph).
> See here for more details on the issue:
> http://insideria.com/2010/10/flex-rpc-and-the-broken-mxlogg.html
>
> Expected Results:
> No computation of the debug message should be done when mx.rpc is not in
> debug mode.
> At least provide one of these options :
> - Allow adding manually excluded properties in
> RPCObjectUtils.defaultToStringExcludes (make it public or add a function
> addDefaultExclude)
> - Use existing toString() methods on objects when available instead of always
> relying on AS3 reflection
> - Provide a way to completely override the default RPCObjectUtil.toString,
> i.e.
> public var toStringFunction:Function;
> public static function toString(value:Object,
> namespaceURIs:Array = null,
> exclude:Array = null):String
> {
> if (toStringFunction != null) {
> return toStringFunction(value, namespaceURIs, exclude);
> }
> if (exclude == null)
> {
> exclude = defaultToStringExcludes;
> }
>
> refCount = 0;
> return internalToString(value, 0, null, namespaceURIs, exclude);
> }
>
> Workaround (if any):
>
> Never set any debug level on any Logger.
--
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-26325) RemoteObject logs too eagerly all sent messages
[
https://issues.apache.org/jira/browse/FLEX-26325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-26325:
-
Priority: Major (was: Minor)
> RemoteObject logs too eagerly all sent messages
> ---
>
> Key: FLEX-26325
> URL: https://issues.apache.org/jira/browse/FLEX-26325
> Project: Apache Flex
> Issue Type: Bug
> Components: RPC: RemoteObject
>Affects Versions: Adobe Flex SDK 4.1 (Release)
> Environment: Affected OS(s): All OS Platforms
> Language Found: English
>Reporter: Adobe JIRA
>Assignee: Adobe JIRA
>
> Steps to reproduce:
> 1. Set debug level on any Logger in the application (not even necessarily on
> mx.rpc.*)
> 2. Call a remote operation with a RemoteObject sending a complex object
> graph, or an object graph containing 'lazy loaded' data, e.g. with LCDS or
> GraniteDS
>
> Actual Results:
> RemoteObject computes the complete debug message in RPCObjectUtils by the
> ultra slow AS3 reflection (even when the message will never be logged at
> all), and consequently triggers all lazy initializations (for example by
> accessing all lazyCollection.length properties on all the object graph).
> See here for more details on the issue:
> http://insideria.com/2010/10/flex-rpc-and-the-broken-mxlogg.html
>
> Expected Results:
> No computation of the debug message should be done when mx.rpc is not in
> debug mode.
> At least provide one of these options :
> - Allow adding manually excluded properties in
> RPCObjectUtils.defaultToStringExcludes (make it public or add a function
> addDefaultExclude)
> - Use existing toString() methods on objects when available instead of always
> relying on AS3 reflection
> - Provide a way to completely override the default RPCObjectUtil.toString,
> i.e.
> public var toStringFunction:Function;
> public static function toString(value:Object,
> namespaceURIs:Array = null,
> exclude:Array = null):String
> {
> if (toStringFunction != null) {
> return toStringFunction(value, namespaceURIs, exclude);
> }
> if (exclude == null)
> {
> exclude = defaultToStringExcludes;
> }
>
> refCount = 0;
> return internalToString(value, 0, null, namespaceURIs, exclude);
> }
>
> Workaround (if any):
>
> Never set any debug level on any Logger.
--
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-26325) RemoteObject logs too eagerly all sent messages
[
https://issues.apache.org/jira/browse/FLEX-26325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean reopened FLEX-26325:
--
> RemoteObject logs too eagerly all sent messages
> ---
>
> Key: FLEX-26325
> URL: https://issues.apache.org/jira/browse/FLEX-26325
> Project: Apache Flex
> Issue Type: Bug
> Components: RPC: RemoteObject
>Affects Versions: Adobe Flex SDK 4.1 (Release)
> Environment: Affected OS(s): All OS Platforms
> Language Found: English
>Reporter: Adobe JIRA
>Assignee: Adobe JIRA
>Priority: Minor
>
> Steps to reproduce:
> 1. Set debug level on any Logger in the application (not even necessarily on
> mx.rpc.*)
> 2. Call a remote operation with a RemoteObject sending a complex object
> graph, or an object graph containing 'lazy loaded' data, e.g. with LCDS or
> GraniteDS
>
> Actual Results:
> RemoteObject computes the complete debug message in RPCObjectUtils by the
> ultra slow AS3 reflection (even when the message will never be logged at
> all), and consequently triggers all lazy initializations (for example by
> accessing all lazyCollection.length properties on all the object graph).
> See here for more details on the issue:
> http://insideria.com/2010/10/flex-rpc-and-the-broken-mxlogg.html
>
> Expected Results:
> No computation of the debug message should be done when mx.rpc is not in
> debug mode.
> At least provide one of these options :
> - Allow adding manually excluded properties in
> RPCObjectUtils.defaultToStringExcludes (make it public or add a function
> addDefaultExclude)
> - Use existing toString() methods on objects when available instead of always
> relying on AS3 reflection
> - Provide a way to completely override the default RPCObjectUtil.toString,
> i.e.
> public var toStringFunction:Function;
> public static function toString(value:Object,
> namespaceURIs:Array = null,
> exclude:Array = null):String
> {
> if (toStringFunction != null) {
> return toStringFunction(value, namespaceURIs, exclude);
> }
> if (exclude == null)
> {
> exclude = defaultToStringExcludes;
> }
>
> refCount = 0;
> return internalToString(value, 0, null, namespaceURIs, exclude);
> }
>
> Workaround (if any):
>
> Never set any debug level on any Logger.
--
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-33341) VectorCollection becomes progressively slower
[ https://issues.apache.org/jira/browse/FLEX-33341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-33341: - Labels: VectorCollection performance (was: VectorCollection) > VectorCollection becomes progressively slower > - > > Key: FLEX-33341 > URL: https://issues.apache.org/jira/browse/FLEX-33341 > Project: Apache Flex > Issue Type: Improvement > Components: Collections >Affects Versions: Apache Flex 4.9.0 > Environment: Flash Player 11.5 >Reporter: Simon Gladman > Labels: VectorCollection, performance > Fix For: Apache Flex 4.9.0 > > > If I repeatedly addItem() and removeAll() from a VectorCollection, the > removeAll() and refresh() methods become progressively slower. > An example can be found here: > http://flexmonkey.blogspot.co.uk/2013/01/apache-flex-490-vectorcollection-vs.html -- 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-27905) Adding/Removing children to same parents sometimes causes unnecessary style invalidation
[ https://issues.apache.org/jira/browse/FLEX-27905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-27905: - Labels: performance (was: ) > Adding/Removing children to same parents sometimes causes unnecessary style > invalidation > > > Key: FLEX-27905 > URL: https://issues.apache.org/jira/browse/FLEX-27905 > Project: Apache Flex > Issue Type: Bug > Components: Styles >Affects Versions: Adobe Flex SDK 4.5.1 (Release) > Environment: Affected OS(s): All OS Platforms > Language Found: English >Reporter: Adobe JIRA > Labels: performance > > Steps to reproduce: > 1. Run attached PerformanceTests3.mxml -- remove the monkey-patched version > of UIComponent > 2. Notice how slow remove and then re-adding those 200 Groups are (each > Group has 10 Button children) > > Actual Results: > Since adding/removing to the same parent (and the styles haven't changed), > styles shouldn't need to be regenerated. Unfortunately, for a typical > application, especially when using includeIn/excludeFrom with state, this can > happen a lot. On my computer, the time it takes for me is: > 430ms, 2159ms, 18ms (code, validation, render) > > Expected Results: > After a few changes (will explain in comment below), the result I was > getting on my computer was: > 88ms, 13ms, 18ms (code, validation, render) > On more complicated examples, with more children and more styles, this can > make an even bigger difference > > 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-28921) SkinnableTextBase maxChars should be bindable.
[ https://issues.apache.org/jira/browse/FLEX-28921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-28921: - Labels: easyfix (was: ) > SkinnableTextBase maxChars should be bindable. > -- > > Key: FLEX-28921 > URL: https://issues.apache.org/jira/browse/FLEX-28921 > Project: Apache Flex > Issue Type: Improvement > Components: Spark: TextArea >Affects Versions: Adobe Flex SDK Previous > Environment: Language Found: English >Reporter: Adobe JIRA > Labels: easyfix > > The property maxChars on SkinnableTextBase should be bindable. I assume that > many properties on SkinnableTextBase aren't bindable for performance reasons. > However, it seems to me that maxChars is a property that doesn't change very > often when it is used. For this reason, I don't see any implications to > making it bindable. > In fact, it would be useful. For instance, to create a counter for how many > characters are left in a TextInput or a TextArea: > > That use-case currently results in a compiler warning because maxChars isn't > bindable. -- 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-12736) ListViewCollection.sort exponentially slower than Array.sort
[ https://issues.apache.org/jira/browse/FLEX-12736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-12736: - Labels: performance (was: ) > ListViewCollection.sort exponentially slower than Array.sort > > > Key: FLEX-12736 > URL: https://issues.apache.org/jira/browse/FLEX-12736 > Project: Apache Flex > Issue Type: Bug > Components: Collections >Affects Versions: Adobe Flex SDK Previous > Environment: Affected OS(s): Windows > Affected OS(s): Windows XP > Language Found: English >Reporter: Adobe JIRA > Labels: performance > > By chance I was looking at the SDK code for ListViewCollection.sort and was > surprised at the algorithm used. Tested showed that it's exponentially > slower than Array.sort(). Granted, it only matters on collections with more > than 1,000 items which is bad in a real app anyways, but still, it's a huge > difference in large collections. > Steps to reproduce: > 1. Create a large collection as both an Array and as ArrayCollection > 2. sort the array and set the sort property of the ArrayCollection > 3. loop through each a few times > > Actual Results: > > looping through a sorted array collection is incredibly slower than sorting > an array one time, especially when you loop many times as the collection > doesn't cache a sorted index > > Expected Results: > > I figured collection would store a sorted index and there would be a nominal > difference in performance > > Workaround (if any): > > don't use ArrayCollection.sort property if you have a ridiculous number of > items (which you really shouldn't have in the first place) > Note that on several occasions I got a script error saying a script was > causing the app to run slowly when sorting a 1,000,000 item collection (yeah, > too big collection, but still, Array.sort() handles it fine). -- 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-27291) Redundant code in Scroller: orientation change handler
[ https://issues.apache.org/jira/browse/FLEX-27291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-27291: - Labels: performance (was: ) > Redundant code in Scroller: orientation change handler > -- > > Key: FLEX-27291 > URL: https://issues.apache.org/jira/browse/FLEX-27291 > 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 > Labels: performance > > Found in version: Hero i6 (prerelease) > orientationChangeHandler seems to be redundant, since the scroll positions > depends on scroller/viewport properties (height, contentHeight, etc), not > something top and global like device orientation. This brings undesirable > dependencies and affects the performance a bit (since it would make double > proccessing on orientation change and on component properties change). > Solution: remove everything regarding orientation. > If someone will point on checkScrollPosition() and how orientation change > affects stopping throwEffect and snapping — it makes more sense to > distinguish between viewport's content resize and scroller resize to achieve > that. But not the orientation. The code smells... like _global variables. -- 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-22220) BindabilityInfo and DescribeTypeCache Memoization
[ https://issues.apache.org/jira/browse/FLEX-0?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-0: - Labels: performance (was: ) > BindabilityInfo and DescribeTypeCache Memoization > - > > Key: FLEX-0 > URL: https://issues.apache.org/jira/browse/FLEX-0 > Project: Apache Flex > Issue Type: Improvement > Components: Data Binding >Affects Versions: Adobe Flex SDK 4.5 (Release) > Environment: Affected OS(s): All OS Platforms > Affected OS(s): All OS Platforms > Browser: Safari > Language Found: English >Reporter: Adobe JIRA > Labels: performance > > Steps to reproduce: > 1. Watch DescribeTypeCache rack up time in parsing xml of classes, which > don't change at runtime. > 2. > 3. > > Actual Results: > Many of the Binding-related functions involved in initialization are largely > methods that calculate values that aren't dependent on state. This means > that they can be calculated pre-compile-time, in some sort of generated > class, thereby increasing startup time performance. There is no need to > calculate these values before hand. > Specifically, in mx.binding.BindabilityInfo, when > mx.binding.PropertyWatcher-and-related call Watcher#updateParent, they > calculate the DescribeTypeCache, and the events for the class, by processing > the metadata from the class. This information does not change at runtime. > It can and should be either processed by the compiler, which could spit out a > generated class of the pre-computed values, or the properties in these > classes that are "private" and that store the values > (BindabilityInfo#typeDescription, BindabilityInfo#classChangeEvents, > BindabilityInfo#childChangeEvents, and DescribeTypeCache#typeCache) should be > made "mx_internal". This would allow us to precompute them using our own > methods if it seems too much work to solve this problem with the compiler. > There are easily 30+ classes that must go through this "DescribeType" phase > in an application, and this requires significant resources to calculate. It > should be precomputed, or the properties should be "mx_interal" so we can > figure out our own means for adding the precomputed values to the cache. > Please let me know if you could make this change immediately. It should only > take 5 minutes to make the properties mx_internal, and no harm would be done. > Thanks so much. > > Expected Results: > mx_internal properties, so we can precalculate values and add them to the > cache as a mixin. > > Workaround (if any): > There is no work around. This should be a very simple enhancement and should > be easily included in the Flex 4 release. -- 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-27712) Check for listeners before dispatching them
[ https://issues.apache.org/jira/browse/FLEX-27712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-27712: - Labels: performance (was: ) > Check for listeners before dispatching them > --- > > Key: FLEX-27712 > URL: https://issues.apache.org/jira/browse/FLEX-27712 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Framework >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: performance > > In the UIComponent class there are places where event listeners are being > created and dispatched without checking if listeners exist. This may help > performance. > // Original Code > dispatchEvent(new FlexEvent(FlexEvent.CREATION_COMPLETE)); > // possible change > if (hasEventListener(FlexEvent.CREATION_COMPLETE)) > dispatchEvent(new FlexEvent(FlexEvent.CREATION_COMPLETE)); -- 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-33282) Performance issue with multiple item renderers
[ https://issues.apache.org/jira/browse/FLEX-33282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-33282: - Labels: perfomance (was: ) > Performance issue with multiple item renderers > --- > > Key: FLEX-33282 > URL: https://issues.apache.org/jira/browse/FLEX-33282 > Project: Apache Flex > Issue Type: Bug > Components: Spark: DataGrid >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: At least on mac >Reporter: Petteri Tuovila > Labels: perfomance > > The problem is that the ItemRenderer's prepare is called for every visible > ItemRenderer when the mouse is moved over the grid and when starting and > finishing item editing. Of course that prepare function should be called when > the renderers are first brought to stage at the initialization and when you > scroll up or down outside the screen when the renderers are recycled. > We are using datasets that well fit the screen with multiple columns so this > can really make the program a little sluggish to use. When starting to edit > there's easily a second or two delay before editor appears, after the > indicator catches up with the mouse. -- 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-23466) Very Simple Proposal to Speed Up Download Times and Perceived Performance of Flex Apps
[ https://issues.apache.org/jira/browse/FLEX-23466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-23466. -- Resolution: Won't Fix Can't fix caching RSL frameworks is an Flash Player feature. Apache Flex RSLs will be cached by the normal browser caching mechanism. > Very Simple Proposal to Speed Up Download Times and Perceived Performance of > Flex Apps > -- > > Key: FLEX-23466 > URL: https://issues.apache.org/jira/browse/FLEX-23466 > Project: Apache Flex > Issue Type: New Feature > Components: .Unspecified - Framework >Affects Versions: Adobe Flex SDK Previous > Environment: Language Found: English >Reporter: Adobe JIRA > > I have been spending months trying to optimize some of our Flex apps, using > all the standards out there (RSL, Modules, externalizing assets, making code > smaller too, etc.). RSLs don't really work for most of my audience because > because many of them have older computers and it can take 10-20 seconds+ to > download. > I was thinking, with the great advancement/feature of being able to cache > Adobe frameworks into the Flash Player, how about the idea of creating a base > "wrapper" or "preloader" application that was just a > spark.components.Application, which is 300kb+, and somehow standardizing > that. > My thinking is that, if Adobe sponsors such a thing, and many people use it, > we have a much higher chance of that being cached in the browser from someone > else so we can use it. And it's small enough so the browser cache wouldn't > mind that much. > Even better, what if you could cache a swf like that in the Flash Player! > Then all of our apps would effectively start out out 40kb (a module's size?). > Loading all the RSLs can be up to 2mb! With this, it'd be a lot smaller, and > very practical. > Love to know your thoughts, > Lance -- 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-23466) Very Simple Proposal to Speed Up Download Times and Perceived Performance of Flex Apps
[ https://issues.apache.org/jira/browse/FLEX-23466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648975#comment-13648975 ] Justin Mclean commented on FLEX-23466: -- Interesting enough this was added (caching framework RSLs) and then taken away with the donation to Apache Flex. As framework RSL caching is a Flash Player feature there noting Apache Flex can do about this issue. (Sadly). > Very Simple Proposal to Speed Up Download Times and Perceived Performance of > Flex Apps > -- > > Key: FLEX-23466 > URL: https://issues.apache.org/jira/browse/FLEX-23466 > Project: Apache Flex > Issue Type: New Feature > Components: .Unspecified - Framework >Affects Versions: Adobe Flex SDK Previous > Environment: Language Found: English >Reporter: Adobe JIRA > > I have been spending months trying to optimize some of our Flex apps, using > all the standards out there (RSL, Modules, externalizing assets, making code > smaller too, etc.). RSLs don't really work for most of my audience because > because many of them have older computers and it can take 10-20 seconds+ to > download. > I was thinking, with the great advancement/feature of being able to cache > Adobe frameworks into the Flash Player, how about the idea of creating a base > "wrapper" or "preloader" application that was just a > spark.components.Application, which is 300kb+, and somehow standardizing > that. > My thinking is that, if Adobe sponsors such a thing, and many people use it, > we have a much higher chance of that being cached in the browser from someone > else so we can use it. And it's small enough so the browser cache wouldn't > mind that much. > Even better, what if you could cache a swf like that in the Flash Player! > Then all of our apps would effectively start out out 40kb (a module's size?). > Loading all the RSLs can be up to 2mb! With this, it'd be a lot smaller, and > very practical. > Love to know your thoughts, > Lance -- 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-23466) Very Simple Proposal to Speed Up Download Times and Perceived Performance of Flex Apps
[ https://issues.apache.org/jira/browse/FLEX-23466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-23466: - Description: I have been spending months trying to optimize some of our Flex apps, using all the standards out there (RSL, Modules, externalizing assets, making code smaller too, etc.). RSLs don't really work for most of my audience because because many of them have older computers and it can take 10-20 seconds+ to download. I was thinking, with the great advancement/feature of being able to cache Adobe frameworks into the Flash Player, how about the idea of creating a base "wrapper" or "preloader" application that was just a spark.components.Application, which is 300kb+, and somehow standardizing that. My thinking is that, if Adobe sponsors such a thing, and many people use it, we have a much higher chance of that being cached in the browser from someone else so we can use it. And it's small enough so the browser cache wouldn't mind that much. Even better, what if you could cache a swf like that in the Flash Player! Then all of our apps would effectively start out out 40kb (a module's size?). Loading all the RSLs can be up to 2mb! With this, it'd be a lot smaller, and very practical. Love to know your thoughts, Lance > Very Simple Proposal to Speed Up Download Times and Perceived Performance of > Flex Apps > -- > > Key: FLEX-23466 > URL: https://issues.apache.org/jira/browse/FLEX-23466 > Project: Apache Flex > Issue Type: New Feature > Components: .Unspecified - Framework >Affects Versions: Adobe Flex SDK Previous > Environment: Language Found: English >Reporter: Adobe JIRA > > I have been spending months trying to optimize some of our Flex apps, using > all the standards out there (RSL, Modules, externalizing assets, making code > smaller too, etc.). RSLs don't really work for most of my audience because > because many of them have older computers and it can take 10-20 seconds+ to > download. > I was thinking, with the great advancement/feature of being able to cache > Adobe frameworks into the Flash Player, how about the idea of creating a base > "wrapper" or "preloader" application that was just a > spark.components.Application, which is 300kb+, and somehow standardizing > that. > My thinking is that, if Adobe sponsors such a thing, and many people use it, > we have a much higher chance of that being cached in the browser from someone > else so we can use it. And it's small enough so the browser cache wouldn't > mind that much. > Even better, what if you could cache a swf like that in the Flash Player! > Then all of our apps would effectively start out out 40kb (a module's size?). > Loading all the RSLs can be up to 2mb! With this, it'd be a lot smaller, and > very practical. > Love to know your thoughts, > Lance -- 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-16964) HaloBorder performance issue
[
https://issues.apache.org/jira/browse/FLEX-16964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648972#comment-13648972
]
Justin Mclean commented on FLEX-16964:
--
Still an "issue" in Apache Flex 4.9 - should be worth looking into as potential
for performance increase.
> HaloBorder performance issue
>
>
> Key: FLEX-16964
> URL: https://issues.apache.org/jira/browse/FLEX-16964
> Project: Apache Flex
> Issue Type: Improvement
> Components: Skinning
>Affects Versions: Adobe Flex SDK 3.0 (Release)
> Environment: Language Found: English
>Reporter: Adobe JIRA
>
> Steps to reproduce:
> 1. Create a canvas and add a child.
> 2. Add logic to move or resize the child.
> 3. Run
> 4. Turn show redraw regions on.
> 5. Now move or resize the child.
>
> Actual Results:
> It redraws the complete canvas
>
> Expected Results:
> It should redraw only the changes.
>
> Workaround (if any):
> Create a new skin by inheriting it from HaloBorder, like this (see
> [adjustment]):
>
> package
> {
> import mx.skins.halo.HaloBorder;
> import mx.core.mx_internal;
> use namespace mx_internal;
> public class FixedHaloBorder extends HaloBorder
> {
> public function FixedHaloBorder()
> {
> super();
> }
> protected var prevWidth:Number;
> protected var prevHeight:Number;
> override protected function updateDisplayList(w:Number, h:Number):void
> {
> if (isNaN(w) || isNaN(h)) return;
> // Store background color in an object,
> // so that null is distinct from black.
> backgroundColor = getBackgroundColor();
> bRoundedCorners = false;
> backgroundAlphaName = "backgroundAlpha";
> backgroundHole = null;
> radius = 0;
> radiusObj = null;
> // [adjustment] We should only draw the border and background
> when the size has changed.
> if(prevWidth != w || prevHeight != h)
> {
> drawBorder(w,h);
> drawBackground(w,h);
> prevWidth = w;
> prevHeight = h;
> }
> }
>
> /**
> * @private
> * If borderStyle may have changed, clear the cached border metrics.
> */
> override public function styleChanged(styleProp:String):void
> {
> super.styleChanged(styleProp);
> // [adjustment] We have to set backgroundColor explicitly to
> workaround another bug.
> backgroundColor = getStyle("backgroundColor");
>
> // [adjustment] We should draw the border and background when a
> style has changed.
>drawBorder(width,height);
>drawBackground(width,height);
> }
> }
> }
>
--
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-28861) Migrate fix to truncateToFit to StyleableTextField
[ https://issues.apache.org/jira/browse/FLEX-28861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648967#comment-13648967 ] Justin Mclean commented on FLEX-28861: -- Fixed issue with unused splice same as other truncateToFit's > Migrate fix to truncateToFit to StyleableTextField > -- > > Key: FLEX-28861 > URL: https://issues.apache.org/jira/browse/FLEX-28861 > Project: Apache Flex > Issue Type: Bug > Components: Mobile: Text >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 > > Apply changes in revision 22797 and 22853 to StyleableTextField -- 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-28861) Migrate fix to truncateToFit to StyleableTextField
[ https://issues.apache.org/jira/browse/FLEX-28861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648962#comment-13648962 ] Justin Mclean commented on FLEX-28861: -- Anyone know what revision 22797 and 22853 were? No access to Adobe SVN. > Migrate fix to truncateToFit to StyleableTextField > -- > > Key: FLEX-28861 > URL: https://issues.apache.org/jira/browse/FLEX-28861 > Project: Apache Flex > Issue Type: Bug > Components: Mobile: Text >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 > > Apply changes in revision 22797 and 22853 to StyleableTextField -- 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-14317) mx.core.UITextField.truncateToFit() removes all text formatting if text needs to be truncated
[
https://issues.apache.org/jira/browse/FLEX-14317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-14317:
-
Labels: easytest (was: )
> mx.core.UITextField.truncateToFit() removes all text formatting if text needs
> to be truncated
> -
>
> Key: FLEX-14317
> URL: https://issues.apache.org/jira/browse/FLEX-14317
> Project: Apache Flex
> Issue Type: Bug
> Components: mx: Text
>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: easytest
>
> Steps to reproduce:
> 1. Assign bold formatting to a Label, Text, or anything using a UITextField.
> 2. Reduce the width of the component so that the text cannot be fully
> displayed
> 3. call component.truncateToFit() to truncate the obscured text and replace
> it with an ellipsis
>
> Actual Results:
>
> The text is truncated, but the formatting is changed back to the text field's
> default format. If this causes a transition from bold back to normal
> formatting, it is likely that the ellipsis replacement will be too agressive,
> since the normal text now takes up less width than the bold text.
> Further, any code calling truncateToFit() needs to reformat the resulting
> text.
>
> Expected Results:
>
> The text should retain its formatting, and just put the ellipsis where it
> needs to go.
>
> Workaround (if any):
>
> Here's my suggested code fix. It works (and least, it works for text where
> everything is the same format):
> // Need to check if we should truncate, but it
> // could be due to rounding error. Let's check that it's not.
> // Examples of rounding errors happen with "South Africa" and "Game"
> // with verdana.ttf.
> if (originalText != "" && measuredWidth > w + 0.01)
> {
> // This should get us into the ballpark.
> var s:String = super.text = originalText;
> var tf:TextFormat = textField.getTextFormat();
> while (s.length > 1 && measuredWidth > w)
> {
> s = s.slice(0, -1);
> super.text = s + truncationIndicator;
> setTextFormat( tf );
> }
>
> return true;
> }
> I tried a variant that didn't save/restore the TextFormat object, and instead
> called replaceText( s.length - 2, s.length, truncationIndicator );, but that
> seemed to cause an infinite event dispatch loop. If that infinite loop could
> be fixed, then the replaceText method would be even better, since it would
> even work for text with multiple TextRuns of different formats.
--
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-18072) Label does not show any text if truncateToFit is false
[
https://issues.apache.org/jira/browse/FLEX-18072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean resolved FLEX-18072.
--
Resolution: Not A Problem
Fix Version/s: Apache Flex 4.10.0
No longer an issue if issue exist it was in previous version of the SDK.
> Label does not show any text if truncateToFit is false
> --
>
> Key: FLEX-18072
> URL: https://issues.apache.org/jira/browse/FLEX-18072
> Project: Apache Flex
> Issue Type: Bug
> Components: mx: Label
>Affects Versions: Adobe Flex SDK 3.3 (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: easyfix, easytest
> Fix For: Apache Flex 4.10.0
>
>
> Steps to reproduce:
> 1.
> Create a label
> 2.
> set truncateToFit to false
> 3.
> see that you see no text
>
> Actual Results:
> No text is visible at all
>
> Expected Results:
> Seeing text
>
>
> Workaround (if any):
>
> If you look at updateDisplayList you'll see a branch that does
> if (truncateToFit)
> {
> ...
> }
> in there it sets the textField.text to _text;
> this does not happen at all otherwise, therefore you're sitting there with
> valid text in
> _text, but it won't show
> can derive from label and set it manually in updateDisplayList i suppose
--
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-18072) Label does not show any text if truncateToFit is false
[
https://issues.apache.org/jira/browse/FLEX-18072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648956#comment-13648956
]
Justin Mclean commented on FLEX-18072:
--
Both truncateToFit="false" and truncateToFit="true" work as expected.
> Label does not show any text if truncateToFit is false
> --
>
> Key: FLEX-18072
> URL: https://issues.apache.org/jira/browse/FLEX-18072
> Project: Apache Flex
> Issue Type: Bug
> Components: mx: Label
>Affects Versions: Adobe Flex SDK 3.3 (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: easyfix, easytest
>
> Steps to reproduce:
> 1.
> Create a label
> 2.
> set truncateToFit to false
> 3.
> see that you see no text
>
> Actual Results:
> No text is visible at all
>
> Expected Results:
> Seeing text
>
>
> Workaround (if any):
>
> If you look at updateDisplayList you'll see a branch that does
> if (truncateToFit)
> {
> ...
> }
> in there it sets the textField.text to _text;
> this does not happen at all otherwise, therefore you're sitting there with
> valid text in
> _text, but it won't show
> can derive from label and set it manually in updateDisplayList i suppose
--
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-14316) mx.core.UITextField.truncateToFit() contains dead code
[
https://issues.apache.org/jira/browse/FLEX-14316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean resolved FLEX-14316.
--
Resolution: Fixed
Fix Version/s: Apache Flex 4.10.0
Checked into develop branch
> mx.core.UITextField.truncateToFit() contains dead code
> --
>
> Key: FLEX-14316
> URL: https://issues.apache.org/jira/browse/FLEX-14316
> Project: Apache Flex
> Issue Type: Bug
> Components: mx: Label
>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: Trivial
> Labels: easyfix
> Fix For: Apache Flex 4.10.0
>
>
> The truncateToFit() method contains a line of dead code. The results of
> originalText.slice() are not assigned anywhere.
> if (originalText != "" && textWidth + TEXT_WIDTH_PADDING > w +
> 0.01)
> {
> // This should get us into the ballpark.
> var s:String = super.text = originalText;
> originalText.slice(0,
> Math.floor((w / (textWidth + TEXT_WIDTH_PADDING)) *
> originalText.length));
> while (s.length > 1 && textWidth + TEXT_WIDTH_PADDING > w)
> {
> s = s.slice(0, -1);
> super.text = s + truncationIndicator;
> }
>
> return true;
> }
> So maybe the AS3 compiler is optimizing this out, but the code should be
> removed/commented out from the SDK.
--
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-14316) mx.core.UITextField.truncateToFit() contains dead code
[
https://issues.apache.org/jira/browse/FLEX-14316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648916#comment-13648916
]
Justin Mclean commented on FLEX-14316:
--
was fixed in UITextField but not in UIFTETextField
> mx.core.UITextField.truncateToFit() contains dead code
> --
>
> Key: FLEX-14316
> URL: https://issues.apache.org/jira/browse/FLEX-14316
> Project: Apache Flex
> Issue Type: Bug
> Components: mx: Label
>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: Trivial
> Labels: easyfix
>
> The truncateToFit() method contains a line of dead code. The results of
> originalText.slice() are not assigned anywhere.
> if (originalText != "" && textWidth + TEXT_WIDTH_PADDING > w +
> 0.01)
> {
> // This should get us into the ballpark.
> var s:String = super.text = originalText;
> originalText.slice(0,
> Math.floor((w / (textWidth + TEXT_WIDTH_PADDING)) *
> originalText.length));
> while (s.length > 1 && textWidth + TEXT_WIDTH_PADDING > w)
> {
> s = s.slice(0, -1);
> super.text = s + truncationIndicator;
> }
>
> return true;
> }
> So maybe the AS3 compiler is optimizing this out, but the code should be
> removed/commented out from the SDK.
--
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-13994) ListBase throws an exception due to lack of error checking
[ https://issues.apache.org/jira/browse/FLEX-13994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648189#comment-13648189 ] Justin Mclean commented on FLEX-13994: -- Changed offscreenExtraRowsTop to offscreenExtraRowsTop > 0 and checked into develop. Stopping an RTE even if it occurred due to user error is still worth while IMO. I run into this error once or twice as well. > ListBase throws an exception due to lack of error checking > -- > > Key: FLEX-13994 > URL: https://issues.apache.org/jira/browse/FLEX-13994 > Project: Apache Flex > Issue Type: Improvement > Components: mx: List >Affects Versions: Adobe Flex SDK 3.0 (Release) > Environment: Affected OS(s): Windows > Affected OS(s): Windows XP > Browser: Internet Explorer 7.x > Language Found: English >Reporter: Adobe JIRA >Priority: Minor > Labels: easyfix > Fix For: Adobe Flex SDK 3.0 (Release) > > > Steps to reproduce: > 1. Create a ListBox object > 2. Dynamicaly load a dataProvider every so often > > Actual Results: > ListBase throws an exception every once in a while > > Expected Results: > No exception thrown > > Workaround (if any): > None > Description: > In the file ListBase.as there is a function "makeRowsAndColumnsWithExtraRows" > starting on line 1326. > line 1337 reads: > offscreenExtraRowsTop = Math.min(desiredExtraRowsTop, > verticalScrollPosition); > Every so often, and I'm not sure why, the value for verticalScrollPosition > is set to -1 and so the value for offscreenExtraRowsTop is also -1. > Line 1348 reads: > var curY:Number = offscreenExtraRowsTop ? > rowInfo[offscreenExtraRowsTop-1].y + rowHeight : 0; > and should read: > var curY:Number = (offscreenExtraRowsTop > 0) ? > rowInfo[offscreenExtraRowsTop-1].y + rowHeight : 0; > When verticalScrollPosition is set to -1 this causes the calculation > (offscreenExtraRowsTop-1) on line 1348 to come out at -2 and an exception is > thrown since -2 is not a valid entry in 'rowInfo.' > If my proposed change to line 1348 was made then the exception would not be > thrown because the calculation would not happen and the default value of 0 > would be returned. -- 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-23614) a miss on isValidIPAddress in EmailValidator
[ https://issues.apache.org/jira/browse/FLEX-23614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646068#comment-13646068 ] Justin Mclean edited comment on FLEX-23614 at 5/3/13 4:14 AM: -- Other formats that should be invalid but are not. justin@[1. .1.1] justin@[1.\t.1.1] was (Author: jmclean): Other formats that should be invalid: justin@[1. .1.1] justin@[1.\t.1.1] > a miss on isValidIPAddress in EmailValidator > > > Key: FLEX-23614 > URL: https://issues.apache.org/jira/browse/FLEX-23614 > Project: Apache Flex > Issue Type: New Feature > Components: Validators >Affects Versions: Adobe Flex SDK Previous > Environment: Language Found: English >Reporter: Adobe JIRA > Labels: easyfix > Fix For: Apache Flex 4.10.0 > > > if ip 192.168..1 then return true still > i think 192.168..1 is not legal -- 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-23614) a miss on isValidIPAddress in EmailValidator
[ https://issues.apache.org/jira/browse/FLEX-23614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645284#comment-13645284 ] Justin Mclean edited comment on FLEX-23614 at 5/3/13 4:13 AM: -- Fixed this exact issue and checked into develop branch. was (Author: jmclean): Checked into develop branch. > a miss on isValidIPAddress in EmailValidator > > > Key: FLEX-23614 > URL: https://issues.apache.org/jira/browse/FLEX-23614 > Project: Apache Flex > Issue Type: New Feature > Components: Validators >Affects Versions: Adobe Flex SDK Previous > Environment: Language Found: English >Reporter: Adobe JIRA > Labels: easyfix > Fix For: Apache Flex 4.10.0 > > > if ip 192.168..1 then return true still > i think 192.168..1 is not legal -- 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-27987) Null reference in the focusInHandler
[ https://issues.apache.org/jira/browse/FLEX-27987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-27987. -- Resolution: Cannot Reproduce Fix Version/s: Apache Flex 4.10.0 Looking at focusInHandler there are null checks, so this was probably been fixed in a previous version of the SDK. > Null reference in the focusInHandler > > > Key: FLEX-27987 > URL: https://issues.apache.org/jira/browse/FLEX-27987 > Project: Apache Flex > Issue Type: Bug > Components: Spark: Scroller >Affects Versions: Adobe Flex SDK 4.5.1 (Release) > Environment: Affected OS(s): Windows > Affected OS(s): Windows 7 > Language Found: English >Reporter: Adobe JIRA > Labels: easyfix, easytest > Fix For: Apache Flex 4.10.0 > > > You can test it in the test application I appended. > Steps to reproduce: > 1. Create a List with buttons in the ItemRenderer > 2. Dispatch an event with the click on the button > 3. In the main application listen for this event and change the state > 4. Switch to another window and back to the application > > Actual Results: > A null reference error is thrown in the focusInHandler of the Scroller class > because the focusManager is null and there is no check if it isn't null. > > Expected Results: > No error should be thrown. -- 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-16876) Unrequired cast in DataGridItemRenderer.as
[ https://issues.apache.org/jira/browse/FLEX-16876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-16876. -- Resolution: Fixed Fix Version/s: Apache Flex 4.10.0 Checked into develop branch. > Unrequired cast in DataGridItemRenderer.as > -- > > Key: FLEX-16876 > URL: https://issues.apache.org/jira/browse/FLEX-16876 > Project: Apache Flex > Issue Type: Improvement > Components: mx: DataGrid >Affects Versions: Adobe Flex SDK 3.2 (Release) > Environment: Affected OS(s): All OS Platforms > Affected OS(s): All OS Platforms > Browser: Other (specify version) > Language Found: English >Reporter: Adobe JIRA > Labels: easyfix > Fix For: Apache Flex 4.10.0 > > > Unrequired cast in DataGridItemRenderer.as > line 410 > if (DataGrid(_listData.owner).variableRowHeight) > multiline = true; > can be > if (dg.variableRowHeight) > multiline = true; -- 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-33523) MultiDPIBitmapSource is not behaving properly when fillMode = repeat
[ https://issues.apache.org/jira/browse/FLEX-33523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-33523. -- Resolution: Fixed Fix Version/s: Apache Flex 4.10.0 checked into develop branch > MultiDPIBitmapSource is not behaving properly when fillMode = repeat > > > Key: FLEX-33523 > URL: https://issues.apache.org/jira/browse/FLEX-33523 > Project: Apache Flex > Issue Type: Bug > Components: Spark: Image >Affects Versions: Apache Flex 4.9.0 > Environment: Flash builder 4.7 >Reporter: Ejaz Asghar >Priority: Critical > Labels: BitmapFillMode.REPEAT, BitmapImage, > MultiDPIBitmapSource,, easyfix > Fix For: Apache Flex 4.10.0 > > > Hi there, > I'm developing a learning mobile app for children using Apache Flex and so > far it is going great. Performance is good too. I didnt just learn a lot, but > i also discovered many problem, one of them is v important and i'd appreciate > if you guys take a look into it and fix it. > Problem is related to MultiDPIBitmapSource. It is working fine , however when > i pass MultiDPIBitmapSource to a bitmapImage/Image controls with fillMode = > repeat, it scales the image twice (instead of just replacing the image with > appropriate dpi which is a usual case) > To generate the bug, simply pass a MultiDPIBitmapSource to any image control > with fillmode = repeat, > Waiting for reply, Thanks -- 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-33505) value property of NumericStepper does not update on text input
[ https://issues.apache.org/jira/browse/FLEX-33505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-33505: - Labels: easyfix easytest (was: easytest) > value property of NumericStepper does not update on text input > -- > > Key: FLEX-33505 > URL: https://issues.apache.org/jira/browse/FLEX-33505 > Project: Apache Flex > Issue Type: Bug > Components: mx: NumericStepper, Spark: NumericStepper >Affects Versions: Adobe Flex SDK 3.6 (Release), Adobe Flex SDK 4.6 > (Release), Apache Flex 4.9.0 >Reporter: Chris Martin > Labels: easyfix, easytest > Attachments: NumericStepperTest.zip > > > If a user changes the value of a numeric stepper, they must focus on an > different UI element for the change to propogate down to the value property. > I'll attach example code that demonstrates this behavior. The application is > simple. User clicks on a button to present a popup with a numeric stepper in > it. When the popup closes the label just to the right of the button gets > updated with the NumericStepper.value property > Steps to Reproduce > 1.) Click on the button > 2.) Click into the NumericStepper and type in a new value > 3.) Close the popup > Result > The label is not updated with the appropriate value > Expected Result > The label is updated with the value that was typed into the NumericStepper > Workaround > You can get around this by detecting if the NumericStepper.textDisplay.text > does not match the NumericStepper.value, if so then assume the > textDisplay.text value is the right one and use it. This is not a good > workaround as it requires an assumption and any updates to how the text value > gets formatted into a numeric value in the component will not be carried over > in the custom work around. > To Force expected behavior you can do the following: > 1.) Click on the button > 2.) Click into the NumericStepper and type in a new value > 3.) Click into the TextInput > 4.) Close the popup > When the NumericStepper loses focus, then the appropriate update functions > are called in the component to update the value property -- 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-27543) NumericStepper should loop from max to min and min to max buy default.
[ https://issues.apache.org/jira/browse/FLEX-27543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-27543: - Labels: easytest (was: ) > NumericStepper should loop from max to min and min to max buy default. > -- > > Key: FLEX-27543 > URL: https://issues.apache.org/jira/browse/FLEX-27543 > Project: Apache Flex > Issue Type: Improvement > Components: Spark: NumericStepper >Affects Versions: Adobe Flex SDK Previous > Environment: Affected OS(s): All OS Platforms > Affected OS(s): All OS Platforms > Browser: Other (specify version) > Language Found: English >Reporter: Adobe JIRA > Labels: easytest > > When a NumericStepper has a minimum and maximum set on it it doesn't give any > feedback to the user when these values are reached if they are using the > incrment/decrement buttons or the cursor keys (if they are using the text > input and add an invalid value, the control update to a valid value and > therefore isn't unresponsive). Therefore to the user the control just becomes > unresponsive. > By default the NumericStepper should loop the values from max to min and min > to max buy default, and have a Boolean property that can be set to stop this > default behavior. This means that the control never becomes unresponsive and > the user can clearly see a max/min is reach when the value loops and make a > decision on the value they want to use (much like the steppers you see on > IPhone/IPad. > http://bugs.adobe.com/jira/browse/SDK-30477 goes some way to resolving the > unresponsive issue, but doesn't take into account if the user is using their > cursor keys, therefore looping would be the best default behavior. -- 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-28247) In a NumericStepper, when typing a value manually and tabbing out of the field, the new value is not committed.
[ https://issues.apache.org/jira/browse/FLEX-28247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-28247: - Labels: easyfix easytest (was: ) > In a NumericStepper, when typing a value manually and tabbing out of the > field, the new value is not committed. > --- > > Key: FLEX-28247 > URL: https://issues.apache.org/jira/browse/FLEX-28247 > Project: Apache Flex > Issue Type: Bug > Components: mx: NumericStepper >Affects Versions: Adobe Flex SDK Previous > 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: > 1. Download the Flex in a Week projects archive > (FiaW_Day4_ProjectArchive.zip). Sorry, I cannot locate the download link any > more. > 2. Extract and run project ex4_05_solution. You should see a list of > employees. > 3. Click on the evaluation note of Athena Parker (9) until the numeric > stepper appears. > 4. Select the value 9 in the edit field and replace it by value 55 for > example. > 5. Hit TAB to leave the field. > > Actual Results: > The value reverts to 9. > > Expected Results: > The value commits as 55. > > Workaround (if any): > Needs messing with focus events, I guess. > Note: The same steps but leaving the field with a click somewhere else or > with commits the new value as expected. -- 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-15441) setSelection doesn't set insertion point correctly on a non-focused TextInput (and probably other text components)
[ https://issues.apache.org/jira/browse/FLEX-15441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-15441: - Labels: easytest (was: ) > setSelection doesn't set insertion point correctly on a non-focused > TextInput (and probably other text components) > --- > > Key: FLEX-15441 > URL: https://issues.apache.org/jira/browse/FLEX-15441 > Project: Apache Flex > Issue Type: Bug > Components: mx: TextInput >Affects Versions: Adobe Flex SDK 3.1 (Release) > Environment: Affected OS(s): Mac > Browser: Safari > Language Found: English >Reporter: Adobe JIRA > Labels: easytest > > Steps to reproduce: > 1. Use this MXML code: > > http://www.adobe.com/2006/mxml"; layout="vertical"> > > > > tInput.setSelection(step1.value, > step2.value) > >enter="tInput.setSelection(step1.value, step2.value)"/> > > > 2. Test it out by using the steppers and either the button or the enter key > (when focused in TextInput) to invoke setSelection > 3. Note that when the two steppers have the same value, the insertion point > should be moved. It works fine when the focus > is in the TextArea and you press enter, but when you use the button (and > hence the focus is elsewhere), it sets the selection > to the entire text. > 4. Note also: I first discovered this bug with a subclassed TextInput where > I'd set alwaysShowSelection to true on the TextField; > it behaved in a *different* wrong fashion: it always moved the cursor to the > start of the text. But watching the behavior in that > case was where I became convinced that this is a focus issue. > > Actual Results: setSelection(index,index) selects the entire field when the > focus is away from the field > > Expected Results: setSelection(index,index) should work the same whether the > focus is on the field or not, and it should move the > insertion point to "index" > > Workaround (if any): none that I know of. -- 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
