[jira] [Assigned] (FLEX-34298) Installer log incorrectly says it installing FP 13 when in fact it's installing FP13 beta
[ https://issues.apache.org/jira/browse/FLEX-34298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean reassigned FLEX-34298: Assignee: Justin Mclean > Installer log incorrectly says it installing FP 13 when in fact it's > installing FP13 beta > - > > Key: FLEX-34298 > URL: https://issues.apache.org/jira/browse/FLEX-34298 > Project: Apache Flex > Issue Type: Bug > Components: InstallApacheFlex, Installer, installer.xml (SDK) >Affects Versions: Install Apache Flex 3.0, Install Apache Flex 3.1 >Reporter: Justin Mclean >Assignee: Justin Mclean >Priority: Minor > > When selecting FP 13 beta log file indicates it installer FP 13 dropping the > beta - may be important to know the distinction. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (FLEX-34298) Installer log incorrectly says it installing FP 13 when in fact it's installing FP13 beta
[ https://issues.apache.org/jira/browse/FLEX-34298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-34298. -- Resolution: Fixed Checked into develop > Installer log incorrectly says it installing FP 13 when in fact it's > installing FP13 beta > - > > Key: FLEX-34298 > URL: https://issues.apache.org/jira/browse/FLEX-34298 > Project: Apache Flex > Issue Type: Bug > Components: InstallApacheFlex, Installer, installer.xml (SDK) >Affects Versions: Install Apache Flex 3.0, Install Apache Flex 3.1 >Reporter: Justin Mclean >Priority: Minor > > When selecting FP 13 beta log file indicates it installer FP 13 dropping the > beta - may be important to know the distinction. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34298) Installer log incorrectly says it installing FP 13 when in fact it's installing FP13 beta
[ https://issues.apache.org/jira/browse/FLEX-34298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-34298: - Affects Version/s: Install Apache Flex 3.1 > Installer log incorrectly says it installing FP 13 when in fact it's > installing FP13 beta > - > > Key: FLEX-34298 > URL: https://issues.apache.org/jira/browse/FLEX-34298 > Project: Apache Flex > Issue Type: Bug > Components: InstallApacheFlex, Installer, installer.xml (SDK) >Affects Versions: Install Apache Flex 3.0, Install Apache Flex 3.1 >Reporter: Justin Mclean >Assignee: Justin Mclean >Priority: Minor > > When selecting FP 13 beta log file indicates it installer FP 13 dropping the > beta - may be important to know the distinction. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FLEX-34257) Korean characters are displayed as blank box on the TextField in Galaxy Note 3/Android 4.4
[ https://issues.apache.org/jira/browse/FLEX-34257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054501#comment-14054501 ] Justin Mclean commented on FLEX-34257: -- Looks like it's a known AIR issue: https://forums.adobe.com/thread/1201193 This may also help: http://apache-flex-users.246.n4.nabble.com/Korean-text-not-displayed-in-spark-Label-td4053.html > Korean characters are displayed as blank box on the TextField in Galaxy Note > 3/Android 4.4 > -- > > Key: FLEX-34257 > URL: https://issues.apache.org/jira/browse/FLEX-34257 > Project: Apache Flex > Issue Type: Bug > Components: Spark: CheckBox, Spark: Label, Spark: RadioButton, > Spark: TextArea, Spark: TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: apk compile : Flex4.6, AIR 3.7 SDK, Apache Flex4.9, AIR > 13.0 SDK > runtime : AIR 4.0, AIR 13.0 > os : android Kikat (4.4.2) >Reporter: dongil park > Attachments: Main.mxml, fontEmbedcss.css, screenshot-1.jpg > > > Korean characters are displayed as blank box on the TextField. > I want to see the Korean characters in the TextField. > I have tried to test. > The test results are : > *TextInput, TextArea Component, RadioButton, CheckBox Component : > Disappearing characters or displayed with blank box. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FLEX-34257) Korean characters are displayed as blank box on the TextField in Galaxy Note 3/Android 4.4
[ https://issues.apache.org/jira/browse/FLEX-34257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054499#comment-14054499 ] dongil park commented on FLEX-34257: Right. In my case, at compile time, and use of embedded fonts. Rather than applying a dynamically ... It is a temporary measure to cope. > Korean characters are displayed as blank box on the TextField in Galaxy Note > 3/Android 4.4 > -- > > Key: FLEX-34257 > URL: https://issues.apache.org/jira/browse/FLEX-34257 > Project: Apache Flex > Issue Type: Bug > Components: Spark: CheckBox, Spark: Label, Spark: RadioButton, > Spark: TextArea, Spark: TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: apk compile : Flex4.6, AIR 3.7 SDK, Apache Flex4.9, AIR > 13.0 SDK > runtime : AIR 4.0, AIR 13.0 > os : android Kikat (4.4.2) >Reporter: dongil park > Attachments: Main.mxml, fontEmbedcss.css, screenshot-1.jpg > > > Korean characters are displayed as blank box on the TextField. > I want to see the Korean characters in the TextField. > I have tried to test. > The test results are : > *TextInput, TextArea Component, RadioButton, CheckBox Component : > Disappearing characters or displayed with blank box. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FLEX-34257) Korean characters are displayed as blank box on the TextField in Galaxy Note 3/Android 4.4
[ https://issues.apache.org/jira/browse/FLEX-34257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054495#comment-14054495 ] dongil park commented on FLEX-34257: There are many fonts that support the Hangul > Korean characters are displayed as blank box on the TextField in Galaxy Note > 3/Android 4.4 > -- > > Key: FLEX-34257 > URL: https://issues.apache.org/jira/browse/FLEX-34257 > Project: Apache Flex > Issue Type: Bug > Components: Spark: CheckBox, Spark: Label, Spark: RadioButton, > Spark: TextArea, Spark: TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: apk compile : Flex4.6, AIR 3.7 SDK, Apache Flex4.9, AIR > 13.0 SDK > runtime : AIR 4.0, AIR 13.0 > os : android Kikat (4.4.2) >Reporter: dongil park > Attachments: Main.mxml, fontEmbedcss.css, screenshot-1.jpg > > > Korean characters are displayed as blank box on the TextField. > I want to see the Korean characters in the TextField. > I have tried to test. > The test results are : > *TextInput, TextArea Component, RadioButton, CheckBox Component : > Disappearing characters or displayed with blank box. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Issue Comment Deleted] (FLEX-34257) Korean characters are displayed as blank box on the TextField in Galaxy Note 3/Android 4.4
[ https://issues.apache.org/jira/browse/FLEX-34257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dongil park updated FLEX-34257: --- Comment: was deleted (was: There are many fonts that support the Hangul) > Korean characters are displayed as blank box on the TextField in Galaxy Note > 3/Android 4.4 > -- > > Key: FLEX-34257 > URL: https://issues.apache.org/jira/browse/FLEX-34257 > Project: Apache Flex > Issue Type: Bug > Components: Spark: CheckBox, Spark: Label, Spark: RadioButton, > Spark: TextArea, Spark: TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: apk compile : Flex4.6, AIR 3.7 SDK, Apache Flex4.9, AIR > 13.0 SDK > runtime : AIR 4.0, AIR 13.0 > os : android Kikat (4.4.2) >Reporter: dongil park > Attachments: Main.mxml, fontEmbedcss.css, screenshot-1.jpg > > > Korean characters are displayed as blank box on the TextField. > I want to see the Korean characters in the TextField. > I have tried to test. > The test results are : > *TextInput, TextArea Component, RadioButton, CheckBox Component : > Disappearing characters or displayed with blank box. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FLEX-34257) Korean characters are displayed as blank box on the TextField in Galaxy Note 3/Android 4.4
[ https://issues.apache.org/jira/browse/FLEX-34257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054494#comment-14054494 ] Justin Mclean commented on FLEX-34257: -- Out of interest what do you get if you call Font.enumerateFonts(true) on the device that doesn't display Korean? Does it include a Korean font in the returned list? > Korean characters are displayed as blank box on the TextField in Galaxy Note > 3/Android 4.4 > -- > > Key: FLEX-34257 > URL: https://issues.apache.org/jira/browse/FLEX-34257 > Project: Apache Flex > Issue Type: Bug > Components: Spark: CheckBox, Spark: Label, Spark: RadioButton, > Spark: TextArea, Spark: TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: apk compile : Flex4.6, AIR 3.7 SDK, Apache Flex4.9, AIR > 13.0 SDK > runtime : AIR 4.0, AIR 13.0 > os : android Kikat (4.4.2) >Reporter: dongil park > Attachments: Main.mxml, fontEmbedcss.css, screenshot-1.jpg > > > Korean characters are displayed as blank box on the TextField. > I want to see the Korean characters in the TextField. > I have tried to test. > The test results are : > *TextInput, TextArea Component, RadioButton, CheckBox Component : > Disappearing characters or displayed with blank box. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (FLEX-34257) Korean characters are displayed as blank box on the TextField in Galaxy Note 3/Android 4.4
[ https://issues.apache.org/jira/browse/FLEX-34257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054492#comment-14054492 ] Justin Mclean edited comment on FLEX-34257 at 7/8/14 3:57 AM: -- I'd be surprised if that font contains Korean glyphs as far as I know only these font support Korean: http://store1.adobe.com/cfusion/store/html/index.cfm?store=OLS-US&event=searchFonts&type=category&cat=classification&code=korean was (Author: jmclean): I'd be surprised if that font contain Korean glyphs as far as I know only these font support Korean: http://store1.adobe.com/cfusion/store/html/index.cfm?store=OLS-US&event=searchFonts&type=category&cat=classification&code=korean > Korean characters are displayed as blank box on the TextField in Galaxy Note > 3/Android 4.4 > -- > > Key: FLEX-34257 > URL: https://issues.apache.org/jira/browse/FLEX-34257 > Project: Apache Flex > Issue Type: Bug > Components: Spark: CheckBox, Spark: Label, Spark: RadioButton, > Spark: TextArea, Spark: TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: apk compile : Flex4.6, AIR 3.7 SDK, Apache Flex4.9, AIR > 13.0 SDK > runtime : AIR 4.0, AIR 13.0 > os : android Kikat (4.4.2) >Reporter: dongil park > Attachments: Main.mxml, fontEmbedcss.css, screenshot-1.jpg > > > Korean characters are displayed as blank box on the TextField. > I want to see the Korean characters in the TextField. > I have tried to test. > The test results are : > *TextInput, TextArea Component, RadioButton, CheckBox Component : > Disappearing characters or displayed with blank box. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (FLEX-34257) Korean characters are displayed as blank box on the TextField in Galaxy Note 3/Android 4.4
[ https://issues.apache.org/jira/browse/FLEX-34257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054490#comment-14054490 ] dongil park edited comment on FLEX-34257 at 7/8/14 3:53 AM: One way to solve the problem was temporary. Attach the two files. (Main.mxml, fontEmbedcss.css) When applied to the font, the characters displayed normally. However, the file size is too large problem. FontEmbedcss.css the attached file does not apply, Character still seems to be an empty box. was (Author: vulcan): One way to solve the problem was temporary. Attach the two files. (Main.mxml, fontEmbedcss.css) When applied to the font, the characters displayed normally. However, capacity is far too big a problem. FontEmbedcss.css the attached file does not apply, Character still seems to be an empty box. > Korean characters are displayed as blank box on the TextField in Galaxy Note > 3/Android 4.4 > -- > > Key: FLEX-34257 > URL: https://issues.apache.org/jira/browse/FLEX-34257 > Project: Apache Flex > Issue Type: Bug > Components: Spark: CheckBox, Spark: Label, Spark: RadioButton, > Spark: TextArea, Spark: TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: apk compile : Flex4.6, AIR 3.7 SDK, Apache Flex4.9, AIR > 13.0 SDK > runtime : AIR 4.0, AIR 13.0 > os : android Kikat (4.4.2) >Reporter: dongil park > Attachments: Main.mxml, fontEmbedcss.css, screenshot-1.jpg > > > Korean characters are displayed as blank box on the TextField. > I want to see the Korean characters in the TextField. > I have tried to test. > The test results are : > *TextInput, TextArea Component, RadioButton, CheckBox Component : > Disappearing characters or displayed with blank box. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34257) Korean characters are displayed as blank box on the TextField in Galaxy Note 3/Android 4.4
[ https://issues.apache.org/jira/browse/FLEX-34257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dongil park updated FLEX-34257: --- Attachment: fontEmbedcss.css Main.mxml One way to solve the problem was temporary. Attach the two files. (Main.mxml, fontEmbedcss.css) When applied to the font, the characters displayed normally. However, capacity is far too big a problem. FontEmbedcss.css the attached file does not apply, Character still seems to be an empty box. > Korean characters are displayed as blank box on the TextField in Galaxy Note > 3/Android 4.4 > -- > > Key: FLEX-34257 > URL: https://issues.apache.org/jira/browse/FLEX-34257 > Project: Apache Flex > Issue Type: Bug > Components: Spark: CheckBox, Spark: Label, Spark: RadioButton, > Spark: TextArea, Spark: TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: apk compile : Flex4.6, AIR 3.7 SDK, Apache Flex4.9, AIR > 13.0 SDK > runtime : AIR 4.0, AIR 13.0 > os : android Kikat (4.4.2) >Reporter: dongil park > Attachments: Main.mxml, fontEmbedcss.css, screenshot-1.jpg > > > Korean characters are displayed as blank box on the TextField. > I want to see the Korean characters in the TextField. > I have tried to test. > The test results are : > *TextInput, TextArea Component, RadioButton, CheckBox Component : > Disappearing characters or displayed with blank box. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FLEX-34257) Korean characters are displayed as blank box on the TextField in Galaxy Note 3/Android 4.4
[ https://issues.apache.org/jira/browse/FLEX-34257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054492#comment-14054492 ] Justin Mclean commented on FLEX-34257: -- I'd be surprised if that font contain Korean glyphs as far as I know only these font support Korean: http://store1.adobe.com/cfusion/store/html/index.cfm?store=OLS-US&event=searchFonts&type=category&cat=classification&code=korean > Korean characters are displayed as blank box on the TextField in Galaxy Note > 3/Android 4.4 > -- > > Key: FLEX-34257 > URL: https://issues.apache.org/jira/browse/FLEX-34257 > Project: Apache Flex > Issue Type: Bug > Components: Spark: CheckBox, Spark: Label, Spark: RadioButton, > Spark: TextArea, Spark: TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: apk compile : Flex4.6, AIR 3.7 SDK, Apache Flex4.9, AIR > 13.0 SDK > runtime : AIR 4.0, AIR 13.0 > os : android Kikat (4.4.2) >Reporter: dongil park > Attachments: Main.mxml, fontEmbedcss.css, screenshot-1.jpg > > > Korean characters are displayed as blank box on the TextField. > I want to see the Korean characters in the TextField. > I have tried to test. > The test results are : > *TextInput, TextArea Component, RadioButton, CheckBox Component : > Disappearing characters or displayed with blank box. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34257) Korean characters are displayed as blank box on the TextField in Galaxy Note 3/Android 4.4
[ https://issues.apache.org/jira/browse/FLEX-34257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dongil park updated FLEX-34257: --- Attachment: (was: 20140630_153139.png) > Korean characters are displayed as blank box on the TextField in Galaxy Note > 3/Android 4.4 > -- > > Key: FLEX-34257 > URL: https://issues.apache.org/jira/browse/FLEX-34257 > Project: Apache Flex > Issue Type: Bug > Components: Spark: CheckBox, Spark: Label, Spark: RadioButton, > Spark: TextArea, Spark: TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: apk compile : Flex4.6, AIR 3.7 SDK, Apache Flex4.9, AIR > 13.0 SDK > runtime : AIR 4.0, AIR 13.0 > os : android Kikat (4.4.2) >Reporter: dongil park > Attachments: screenshot-1.jpg > > > Korean characters are displayed as blank box on the TextField. > I want to see the Korean characters in the TextField. > I have tried to test. > The test results are : > *TextInput, TextArea Component, RadioButton, CheckBox Component : > Disappearing characters or displayed with blank box. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34257) Korean characters are displayed as blank box on the TextField in Galaxy Note 3/Android 4.4
[ https://issues.apache.org/jira/browse/FLEX-34257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dongil park updated FLEX-34257: --- Attachment: screenshot-1.jpg > Korean characters are displayed as blank box on the TextField in Galaxy Note > 3/Android 4.4 > -- > > Key: FLEX-34257 > URL: https://issues.apache.org/jira/browse/FLEX-34257 > Project: Apache Flex > Issue Type: Bug > Components: Spark: CheckBox, Spark: Label, Spark: RadioButton, > Spark: TextArea, Spark: TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: apk compile : Flex4.6, AIR 3.7 SDK, Apache Flex4.9, AIR > 13.0 SDK > runtime : AIR 4.0, AIR 13.0 > os : android Kikat (4.4.2) >Reporter: dongil park > Attachments: screenshot-1.jpg > > > Korean characters are displayed as blank box on the TextField. > I want to see the Korean characters in the TextField. > I have tried to test. > The test results are : > *TextInput, TextArea Component, RadioButton, CheckBox Component : > Disappearing characters or displayed with blank box. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FLEX-34257) Korean characters are displayed as blank box on the TextField in Galaxy Note 3/Android 4.4
[ https://issues.apache.org/jira/browse/FLEX-34257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054466#comment-14054466 ] Justin Mclean commented on FLEX-34257: -- How was the Apache SDK installed? Were the optional AdobeEmbedded Font Libraries and Utilities installed? > Korean characters are displayed as blank box on the TextField in Galaxy Note > 3/Android 4.4 > -- > > Key: FLEX-34257 > URL: https://issues.apache.org/jira/browse/FLEX-34257 > Project: Apache Flex > Issue Type: Bug > Components: Spark: CheckBox, Spark: Label, Spark: RadioButton, > Spark: TextArea, Spark: TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: apk compile : Flex4.6, AIR 3.7 SDK, Apache Flex4.9, AIR > 13.0 SDK > runtime : AIR 4.0, AIR 13.0 > os : android Kikat (4.4.2) >Reporter: dongil park > Attachments: 20140630_153139.png > > > Korean characters are displayed as blank box on the TextField. > I want to see the Korean characters in the TextField. > I have tried to test. > The test results are : > *TextInput, TextArea Component, RadioButton, CheckBox Component : > Disappearing characters or displayed with blank box. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FLEX-34257) Korean characters are displayed as blank box on the TextField in Galaxy Note 3/Android 4.4
[ https://issues.apache.org/jira/browse/FLEX-34257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054465#comment-14054465 ] Dave Glasser commented on FLEX-34257: - I just tried with Flex 4.9, AIR SDK 14.0.0.110 and the problem persists. It's happening with multiple controls, but an example is FTETextField, font is embedded Adobe Helvetica LT Std, embedAsCFF=true. It's happening on a Nexus 7 tablet running Android 4.4.4. The same app from the same apk works fine on my Asus Transformer, purchased 12/2012. (I don't have it handy now to check the OS version.) We bought the font from Adobe for the express purpose of embedding it in our Flex apps, since we rotate a lot of text. The same code works great in the Flash Player, and I'm pretty sure it works in our iPad app which is the same codebase as the Android app. So I'm sure the font has the Korean glyphs. > Korean characters are displayed as blank box on the TextField in Galaxy Note > 3/Android 4.4 > -- > > Key: FLEX-34257 > URL: https://issues.apache.org/jira/browse/FLEX-34257 > Project: Apache Flex > Issue Type: Bug > Components: Spark: CheckBox, Spark: Label, Spark: RadioButton, > Spark: TextArea, Spark: TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: apk compile : Flex4.6, AIR 3.7 SDK, Apache Flex4.9, AIR > 13.0 SDK > runtime : AIR 4.0, AIR 13.0 > os : android Kikat (4.4.2) >Reporter: dongil park > Attachments: 20140630_153139.png > > > Korean characters are displayed as blank box on the TextField. > I want to see the Korean characters in the TextField. > I have tried to test. > The test results are : > *TextInput, TextArea Component, RadioButton, CheckBox Component : > Disappearing characters or displayed with blank box. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (FLEX-34400) Missing non english locales for installer log
Justin Mclean created FLEX-34400: Summary: Missing non english locales for installer log Key: FLEX-34400 URL: https://issues.apache.org/jira/browse/FLEX-34400 Project: Apache Flex Issue Type: Bug Components: InstallApacheFlex, Installer Affects Versions: Install Apache Flex 3.1 Reporter: Justin Mclean Installer log files only contains US english. The ant for air only has en_US resources. Resources for each language the installer supports should be added. Missing languages include non US english, German, Spanish, French, Greek, Korean, Japanese, Chinese, Polish and Portuguese. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34257) Korean characters are displayed as blank box on the TextField in Galaxy Note 3/Android 4.4
[ https://issues.apache.org/jira/browse/FLEX-34257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dongil park updated FLEX-34257: --- Attachment: 20140630_153139.png error capture > Korean characters are displayed as blank box on the TextField in Galaxy Note > 3/Android 4.4 > -- > > Key: FLEX-34257 > URL: https://issues.apache.org/jira/browse/FLEX-34257 > Project: Apache Flex > Issue Type: Bug > Components: Spark: CheckBox, Spark: Label, Spark: RadioButton, > Spark: TextArea, Spark: TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: apk compile : Flex4.6, AIR 3.7 SDK, Apache Flex4.9, AIR > 13.0 SDK > runtime : AIR 4.0, AIR 13.0 > os : android Kikat (4.4.2) >Reporter: dongil park > Attachments: 20140630_153139.png > > > Korean characters are displayed as blank box on the TextField. > I want to see the Korean characters in the TextField. > I have tried to test. > The test results are : > *TextInput, TextArea Component, RadioButton, CheckBox Component : > Disappearing characters or displayed with blank box. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FLEX-34371) how TagEncoder handles duplicate define* tags
[
https://issues.apache.org/jira/browse/FLEX-34371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054445#comment-14054445
]
Justin Mclean commented on FLEX-34371:
--
Do previous version of Flex such as Adobe Flex 4.6 give the same issue? Just
want to know if it's a regression issue or not.
> how TagEncoder handles duplicate define* tags
> -
>
> Key: FLEX-34371
> URL: https://issues.apache.org/jira/browse/FLEX-34371
> Project: Apache Flex
> Issue Type: Bug
>Affects Versions: Apache Flex 4.12.0
>Reporter: Guest
> Attachments: test.swf
>
>
> Suppose there are two DefineEditText tags that are the same by .equals, and a
> TagEncoder handles them. This writes them both to the SWF, but assigns them
> the same character ID. Adobe's Flash player can load the SWF fine, but it
> causes swfdump to crash with an exception like the following:
> {code}
> Exception in thread "main" java.lang.IllegalArgumentException: symbol 154
> redefined by identical tag
> at flash.swf.Dictionary.add(Dictionary.java:142)
> at flash.swf.TagDecoder.decodeDefineEditText(TagDecoder.java:1160)
> at flash.swf.TagDecoder.decodeTag(TagDecoder.java:319)
> at flash.swf.TagDecoder.decodeTags(TagDecoder.java:194)
> at flash.swf.TagDecoder.parse(TagDecoder.java:142)
> at flash.swf.tools.SwfxPrinter.dumpSwf(SwfxPrinter.java:2318)
> at flash.swf.tools.SwfxPrinter.main(SwfxPrinter.java:2225)
> {code}
> Actual result:
> defineEditText(tag) in TagEncoder calls
> {code:java}
> int id = dict.add(tag);
> {code}
> When serializing the second DefineEditText, the Dictionary finds the first
> one and returns its ID. Then, the defineEditText(tag) method writes the
> second copy with the first one's ID.
> Expected result:
> either
> - it writes the duplicate with a new ID or
> - it does not write anything and uses the first copy's ID for references to
> the second.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (FLEX-34257) Korean characters are displayed as blank box on the TextField in Galaxy Note 3/Android 4.4
[ https://issues.apache.org/jira/browse/FLEX-34257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054440#comment-14054440 ] Justin Mclean commented on FLEX-34257: -- What version of AIR are you using? It's likely to an AIR issue IMO. One of the fixes for AIR 13 was: Enhanced Supplementary Character Support for TextField Characters from the Basic Multilingual Plane (BMP) with Unicode code points between U+1 and U+10 now work correctly in TextField controls. This change greatly enlarges the code point range we support, and now includes characters like emoticons and complex CCJK characters. (see http://helpx.adobe.com/flash-player/release-note/fp_13_air_13_release_notes.html) Can you supply a simple example that shows the issue. > Korean characters are displayed as blank box on the TextField in Galaxy Note > 3/Android 4.4 > -- > > Key: FLEX-34257 > URL: https://issues.apache.org/jira/browse/FLEX-34257 > Project: Apache Flex > Issue Type: Bug > Components: Spark: CheckBox, Spark: Label, Spark: RadioButton, > Spark: TextArea, Spark: TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: apk compile : Flex4.6, AIR 3.7 SDK, Apache Flex4.9, AIR > 13.0 SDK > runtime : AIR 4.0, AIR 13.0 > os : android Kikat (4.4.2) >Reporter: dongil park > > Korean characters are displayed as blank box on the TextField. > I want to see the Korean characters in the TextField. > I have tried to test. > The test results are : > *TextInput, TextArea Component, RadioButton, CheckBox Component : > Disappearing characters or displayed with blank box. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34371) how TagEncoder handles duplicate define* tags
[
https://issues.apache.org/jira/browse/FLEX-34371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guest updated FLEX-34371:
-
Attachment: test.swf
Here's a copy of the SWF generated by the swfutils.jar from Flex 4.12.1.
> how TagEncoder handles duplicate define* tags
> -
>
> Key: FLEX-34371
> URL: https://issues.apache.org/jira/browse/FLEX-34371
> Project: Apache Flex
> Issue Type: Bug
>Affects Versions: Apache Flex 4.12.0
>Reporter: Guest
> Attachments: test.swf
>
>
> Suppose there are two DefineEditText tags that are the same by .equals, and a
> TagEncoder handles them. This writes them both to the SWF, but assigns them
> the same character ID. Adobe's Flash player can load the SWF fine, but it
> causes swfdump to crash with an exception like the following:
> {code}
> Exception in thread "main" java.lang.IllegalArgumentException: symbol 154
> redefined by identical tag
> at flash.swf.Dictionary.add(Dictionary.java:142)
> at flash.swf.TagDecoder.decodeDefineEditText(TagDecoder.java:1160)
> at flash.swf.TagDecoder.decodeTag(TagDecoder.java:319)
> at flash.swf.TagDecoder.decodeTags(TagDecoder.java:194)
> at flash.swf.TagDecoder.parse(TagDecoder.java:142)
> at flash.swf.tools.SwfxPrinter.dumpSwf(SwfxPrinter.java:2318)
> at flash.swf.tools.SwfxPrinter.main(SwfxPrinter.java:2225)
> {code}
> Actual result:
> defineEditText(tag) in TagEncoder calls
> {code:java}
> int id = dict.add(tag);
> {code}
> When serializing the second DefineEditText, the Dictionary finds the first
> one and returns its ID. Then, the defineEditText(tag) method writes the
> second copy with the first one's ID.
> Expected result:
> either
> - it writes the duplicate with a new ID or
> - it does not write anything and uses the first copy's ID for references to
> the second.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (FLEX-34371) how TagEncoder handles duplicate define* tags
[
https://issues.apache.org/jira/browse/FLEX-34371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054401#comment-14054401
]
Guest commented on FLEX-34371:
--
Here's a sample application. It defines a method writeSprite that creates a
sprite containing a editable text field, with a given initial text, placement
depth, and vertical position. When the method is called twice with the same
initial text, as it is in the sample application, it results in a SWF that
reproduces the crash in this bug.
{code:java}
import java.io.FileOutputStream;
import java.io.IOException;
import java.io.OutputStream;
import flash.swf.Header;
import flash.swf.TagEncoder;
import flash.swf.TagHandler;
import flash.swf.TagValues;
import flash.swf.tags.DefineEditText;
import flash.swf.tags.DefineSprite;
import flash.swf.tags.PlaceObject;
import flash.swf.tags.ShowFrame;
import flash.swf.types.Matrix;
import flash.swf.types.Rect;
public class Test {
public static void writeSprite(final TagHandler handler, final String
init, final int depth, final int y) {
final DefineEditText et = new DefineEditText();
et.bounds = new Rect(4000, 1000);
et.hasText = true;
et.varName = "val";
et.initialText = init;
et.visit(handler);
final DefineSprite ds = new DefineSprite();
final PlaceObject po1 = new
PlaceObject(TagValues.stagPlaceObject);
po1.setRef(et);
po1.depth = 1;
po1.setMatrix(new Matrix(0, 0));
po1.visit(ds.tagList);
final ShowFrame sf = new ShowFrame();
sf.visit(ds.tagList);
ds.visit(handler);
final PlaceObject po2 = new
PlaceObject(TagValues.stagPlaceObject);
po2.setRef(ds);
po2.depth = depth;
po2.setMatrix(new Matrix(0, y));
po2.visit(handler);
}
public static void main(String[] args) throws IOException {
final TagEncoder e = new TagEncoder();
final Header h = new Header();
h.version = 19;
h.size = new Rect(4000, 4000);
h.rate = 60;
e.header(h);
writeSprite(e, "one", 0, 0);
writeSprite(e, "one", 1, 1000);
final ShowFrame sf = new ShowFrame();
sf.visit(e);
e.finish();
final OutputStream os = new FileOutputStream("test.swf");
e.writeTo(os);
os.close();
}
}
{code}
Running this code generates a file test.swf. Running swfdump test.swf causes
SwfxPrinter to crash.
> how TagEncoder handles duplicate define* tags
> -
>
> Key: FLEX-34371
> URL: https://issues.apache.org/jira/browse/FLEX-34371
> Project: Apache Flex
> Issue Type: Bug
>Affects Versions: Apache Flex 4.12.0
>Reporter: Guest
>
> Suppose there are two DefineEditText tags that are the same by .equals, and a
> TagEncoder handles them. This writes them both to the SWF, but assigns them
> the same character ID. Adobe's Flash player can load the SWF fine, but it
> causes swfdump to crash with an exception like the following:
> {code}
> Exception in thread "main" java.lang.IllegalArgumentException: symbol 154
> redefined by identical tag
> at flash.swf.Dictionary.add(Dictionary.java:142)
> at flash.swf.TagDecoder.decodeDefineEditText(TagDecoder.java:1160)
> at flash.swf.TagDecoder.decodeTag(TagDecoder.java:319)
> at flash.swf.TagDecoder.decodeTags(TagDecoder.java:194)
> at flash.swf.TagDecoder.parse(TagDecoder.java:142)
> at flash.swf.tools.SwfxPrinter.dumpSwf(SwfxPrinter.java:2318)
> at flash.swf.tools.SwfxPrinter.main(SwfxPrinter.java:2225)
> {code}
> Actual result:
> defineEditText(tag) in TagEncoder calls
> {code:java}
> int id = dict.add(tag);
> {code}
> When serializing the second DefineEditText, the Dictionary finds the first
> one and returns its ID. Then, the defineEditText(tag) method writes the
> second copy with the first one's ID.
> Expected result:
> either
> - it writes the duplicate with a new ID or
> - it does not write anything and uses the first copy's ID for references to
> the second.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (FLEX-34257) Korean characters are displayed as blank box on the TextField in Galaxy Note 3/Android 4.4
[ https://issues.apache.org/jira/browse/FLEX-34257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054396#comment-14054396 ] Dave Glasser commented on FLEX-34257: - I'm facing this issue also. Flex 4.9, AIR 3.9. Is there a way to vote for this bug? > Korean characters are displayed as blank box on the TextField in Galaxy Note > 3/Android 4.4 > -- > > Key: FLEX-34257 > URL: https://issues.apache.org/jira/browse/FLEX-34257 > Project: Apache Flex > Issue Type: Bug > Components: Spark: CheckBox, Spark: Label, Spark: RadioButton, > Spark: TextArea, Spark: TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: apk compile : Flex4.6, AIR 3.7 SDK, Apache Flex4.9, AIR > 13.0 SDK > runtime : AIR 4.0, AIR 13.0 > os : android Kikat (4.4.2) >Reporter: dongil park > > Korean characters are displayed as blank box on the TextField. > I want to see the Korean characters in the TextField. > I have tried to test. > The test results are : > *TextInput, TextArea Component, RadioButton, CheckBox Component : > Disappearing characters or displayed with blank box. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (FLEX-34257) Korean characters are displayed as blank box on the TextField in Galaxy Note 3/Android 4.4
[ https://issues.apache.org/jira/browse/FLEX-34257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054396#comment-14054396 ] Dave Glasser edited comment on FLEX-34257 at 7/8/14 1:34 AM: - I'm facing this issue also. Flex 4.9, AIR 3.9. was (Author: dglasser): I'm facing this issue also. Flex 4.9, AIR 3.9. Is there a way to vote for this bug? > Korean characters are displayed as blank box on the TextField in Galaxy Note > 3/Android 4.4 > -- > > Key: FLEX-34257 > URL: https://issues.apache.org/jira/browse/FLEX-34257 > Project: Apache Flex > Issue Type: Bug > Components: Spark: CheckBox, Spark: Label, Spark: RadioButton, > Spark: TextArea, Spark: TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: apk compile : Flex4.6, AIR 3.7 SDK, Apache Flex4.9, AIR > 13.0 SDK > runtime : AIR 4.0, AIR 13.0 > os : android Kikat (4.4.2) >Reporter: dongil park > > Korean characters are displayed as blank box on the TextField. > I want to see the Korean characters in the TextField. > I have tried to test. > The test results are : > *TextInput, TextArea Component, RadioButton, CheckBox Component : > Disappearing characters or displayed with blank box. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (FLEX-34399) flash.swf.types.Rect gives different hashCode for .equal() instances
Guest created FLEX-34399: Summary: flash.swf.types.Rect gives different hashCode for .equal() instances Key: FLEX-34399 URL: https://issues.apache.org/jira/browse/FLEX-34399 Project: Apache Flex Issue Type: Bug Affects Versions: Apache Flex 4.12.1 Reporter: Guest Suppose two Rect objects have all the same coordinates. Compare their hashCode and compare them with equals. Actual result: .equals() returns true .hashCode() returns different values, because it incorporates Object's hashCode https://github.com/apache/flex-sdk/blob/develop/modules/swfutils/src/java/flash/swf/types/Rect.java#L105 Expected result: .hashCode() is the same for both instances -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FLEX-30341) Custom TreeItemRenderer causes RFT automation to fail
[ https://issues.apache.org/jira/browse/FLEX-30341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053668#comment-14053668 ] Sourabh Jain commented on FLEX-30341: - I am having same issue. Can you please share the solution. > Custom TreeItemRenderer causes RFT automation to fail > - > > Key: FLEX-30341 > URL: https://issues.apache.org/jira/browse/FLEX-30341 > Project: Apache Flex > Issue Type: Bug > Components: Component Replay >Affects Versions: Adobe Flex SDK Previous > Environment: Affected OS(s): Windows > Affected OS(s): Windows XP > Language Found: English >Reporter: Adobe JIRA > > Steps to reproduce: > 1. Create a custom TreeItemRenderer with no functionality. Extend > TreeItemRenderer. > 2. Create a screen with a tree that uses the custom TreeItemRenderer. Compile > with automation framework libs. > 2. Create an RFT (or FlexMonkey) test that attempts to open the branches of > the tree and click the nodes. > > Actual Results: > RFT gives null pointer exception when the tree branch is clicked. FlexMonkey > throws an exception that the automation delegate for the TreeItem cannot be > found. > > Expected Results: > Tree branches would be operational using custom TreeItemRenderers, even > without custom delegates as there is no new behavior and the > AutomationManager should seek the superclass of the TreeItemRenderer and use > the delegate associated to that class. > > Workaround (if any): > None -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (FLEX-34285) removeItem in XMLListAdapter is calling removeItemAt as an array instead of a method
[ https://issues.apache.org/jira/browse/FLEX-34285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-34285. -- Resolution: Fixed Applied patch, XMLListCollection tests pass, checked into develop. > removeItem in XMLListAdapter is calling removeItemAt as an array instead of a > method > > > Key: FLEX-34285 > URL: https://issues.apache.org/jira/browse/FLEX-34285 > Project: Apache Flex > Issue Type: Bug > Components: Data Binding >Affects Versions: Apache Flex 4.10.0 >Reporter: Dave Keen >Priority: Minor > Labels: easyfix, easytest > Attachments: FLEX-34285.patch > > > XMLListAdapater.as contains the line: > var _item:Object = removeItemAt[getItemIndex(item)]; > when it should be: > var _item:Object = removeItemAt(getItemIndex(item)); -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (FLEX-34398) log not saved when installer close button clicked
Justin Mclean created FLEX-34398: Summary: log not saved when installer close button clicked Key: FLEX-34398 URL: https://issues.apache.org/jira/browse/FLEX-34398 Project: Apache Flex Issue Type: Bug Components: InstallApacheFlex, Installer Affects Versions: Install Apache Flex 3.1 Reporter: Justin Mclean Priority: Minor Log is not saved when installer close button is clicked on or the installer closed -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34285) removeItem in XMLListAdapter is calling removeItemAt as an array instead of a method
[ https://issues.apache.org/jira/browse/FLEX-34285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-34285: - Labels: easyfix easytest (was: easyfix) > removeItem in XMLListAdapter is calling removeItemAt as an array instead of a > method > > > Key: FLEX-34285 > URL: https://issues.apache.org/jira/browse/FLEX-34285 > Project: Apache Flex > Issue Type: Bug > Components: Data Binding >Affects Versions: Apache Flex 4.10.0 >Reporter: Dave Keen >Priority: Minor > Labels: easyfix, easytest > Attachments: FLEX-34285.patch > > > XMLListAdapater.as contains the line: > var _item:Object = removeItemAt[getItemIndex(item)]; > when it should be: > var _item:Object = removeItemAt(getItemIndex(item)); -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34298) Installer log incorrectly says it installing FP 13 when in fact it's installing FP13 beta
[ https://issues.apache.org/jira/browse/FLEX-34298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-34298: - Component/s: Installer InstallApacheFlex > Installer log incorrectly says it installing FP 13 when in fact it's > installing FP13 beta > - > > Key: FLEX-34298 > URL: https://issues.apache.org/jira/browse/FLEX-34298 > Project: Apache Flex > Issue Type: Bug > Components: InstallApacheFlex, Installer, installer.xml (SDK) >Affects Versions: Install Apache Flex 3.0 >Reporter: Justin Mclean >Priority: Minor > > When selecting FP 13 beta log file indicates it installer FP 13 dropping the > beta - may be important to know the distinction. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FLEX-34298) Installer log incorrectly says it installing FP 13 when in fact it's installing FP13 beta
[ https://issues.apache.org/jira/browse/FLEX-34298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053430#comment-14053430 ] Justin Mclean commented on FLEX-34298: -- This is still happening with FP 14 and the latest 3.1 (RC6) of the installer. > Installer log incorrectly says it installing FP 13 when in fact it's > installing FP13 beta > - > > Key: FLEX-34298 > URL: https://issues.apache.org/jira/browse/FLEX-34298 > Project: Apache Flex > Issue Type: Bug > Components: installer.xml (SDK) >Affects Versions: Install Apache Flex 3.0 >Reporter: Justin Mclean >Priority: Minor > > When selecting FP 13 beta log file indicates it installer FP 13 dropping the > beta - may be important to know the distinction. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34321) Null object reference in ScrollableStageText.endTextEdit()
[ https://issues.apache.org/jira/browse/FLEX-34321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-34321: - Labels: easyfix easytest stagetext (was: easytest stagetext) > Null object reference in ScrollableStageText.endTextEdit() > -- > > Key: FLEX-34321 > URL: https://issues.apache.org/jira/browse/FLEX-34321 > Project: Apache Flex > Issue Type: Bug > Components: Mobile: Text >Affects Versions: Apache Flex 4.12.1 > Environment: iOS >Reporter: Neil Rackett >Assignee: Maurice Amsellem > Labels: easyfix, easytest, stagetext > Fix For: Apache Flex 4.12.1 > > > Using the current release version of Apache Flex 4.12.1, you can consistently > recreate this issue and crash an iPhone or iPod touch app on iOS 6 as follows: > # Publish a Flex app to an iPhone or iPod touch > # Tap on a component, the keyboard will appear > # Tap anywhere outside of the component to remove focus and you will receive > the following error: > TypeError: Error #1009: Cannot access a property or method of a null object > reference. > at > spark.components.supportClasses::ScrollableStageText/endTextEdit()[/Users/aharui/flex-sdk-4.12.1/frameworks/projects/mobilecomponents/src/spark/components/supportClasses/ScrollableStageText.as:1958] > at Function/http://adobe.com/AS3/2006/builtin::apply() > at > mx.core::UIComponent/callLaterDispatcher2()[/Users/aharui/flex-sdk-4.12.1/frameworks/projects/framework/src/mx/core/UIComponent.as:12764] > at > mx.core::UIComponent/callLaterDispatcher()[/Users/aharui/flex-sdk-4.12.1/frameworks/projects/framework/src/mx/core/UIComponent.as:12702] > Quick fix: > # Update line 1958 of ScrollableStageText class to `if (!!proxy) > proxy.visible = true;` -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34321) Null object reference in ScrollableStageText.endTextEdit()
[ https://issues.apache.org/jira/browse/FLEX-34321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-34321: - Labels: easytest stagetext (was: stagetext) > Null object reference in ScrollableStageText.endTextEdit() > -- > > Key: FLEX-34321 > URL: https://issues.apache.org/jira/browse/FLEX-34321 > Project: Apache Flex > Issue Type: Bug > Components: Mobile: Text >Affects Versions: Apache Flex 4.12.1 > Environment: iOS >Reporter: Neil Rackett >Assignee: Maurice Amsellem > Labels: easytest, stagetext > Fix For: Apache Flex 4.12.1 > > > Using the current release version of Apache Flex 4.12.1, you can consistently > recreate this issue and crash an iPhone or iPod touch app on iOS 6 as follows: > # Publish a Flex app to an iPhone or iPod touch > # Tap on a component, the keyboard will appear > # Tap anywhere outside of the component to remove focus and you will receive > the following error: > TypeError: Error #1009: Cannot access a property or method of a null object > reference. > at > spark.components.supportClasses::ScrollableStageText/endTextEdit()[/Users/aharui/flex-sdk-4.12.1/frameworks/projects/mobilecomponents/src/spark/components/supportClasses/ScrollableStageText.as:1958] > at Function/http://adobe.com/AS3/2006/builtin::apply() > at > mx.core::UIComponent/callLaterDispatcher2()[/Users/aharui/flex-sdk-4.12.1/frameworks/projects/framework/src/mx/core/UIComponent.as:12764] > at > mx.core::UIComponent/callLaterDispatcher()[/Users/aharui/flex-sdk-4.12.1/frameworks/projects/framework/src/mx/core/UIComponent.as:12702] > Quick fix: > # Update line 1958 of ScrollableStageText class to `if (!!proxy) > proxy.visible = true;` -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34335) Drag DataGrid row with GridItemRenderer - problem
[ https://issues.apache.org/jira/browse/FLEX-34335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-34335: - Labels: datagrid drag drop easytest griditemrenderer itemrenderer (was: datagrid drag drop griditemrenderer itemrenderer) > Drag DataGrid row with GridItemRenderer - problem > - > > Key: FLEX-34335 > URL: https://issues.apache.org/jira/browse/FLEX-34335 > Project: Apache Flex > Issue Type: Bug > Components: Drag and Drop, Spark: DataGrid >Affects Versions: Apache Flex 4.12.1 >Reporter: Grzegorz Pietruszka > Labels: datagrid, drag, drop, easytest, griditemrenderer, > itemrenderer > Attachments: screenshot-1.jpg, test.mxml, test.swf > > > I found the graphical problem in spark DataGrid when starting drag row - the > transparent row under cursor (with "X" icon) is too far below cursor. When I > drag first row everything looks OK, byt when I drag 20'th row then we can see > this error. > I think that problem causes GridItemRenderer, becouse when I generate > DataGrid without renderers, error doesn't occur. > I prepare test here: http://op2.pl/dragdg/test.swf -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (FLEX-34381) Sorting behavior changed between Adobe and Apache Flex SDK (?)
[ https://issues.apache.org/jira/browse/FLEX-34381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053424#comment-14053424 ] Santanu Karar edited comment on FLEX-34381 at 7/7/14 8:11 AM: -- With the new design, there is no way to preserve previously sorting order after doing a collection.sort=null and collection.refresh() (as it was achievable with Adobe SDK after sort=null); or is there a way to preserve the order even after doing a sort=null and collection.refresh() in new updated SDK? was (Author: santanu4ver): With the new design, there is no way to preserve previously sorting order after doing a collection.sort=null and collection.refresh() (as it was achievable with Adobe SDK); or is there a way to preserve the order even after doing a sort=null and collection.refresh() in new updated SDK? > Sorting behavior changed between Adobe and Apache Flex SDK (?) > -- > > Key: FLEX-34381 > URL: https://issues.apache.org/jira/browse/FLEX-34381 > Project: Apache Flex > Issue Type: Bug >Affects Versions: Apache Flex 4.12.0 >Reporter: Santanu Karar > Attachments: SortingWithAdobeSDK.fxp, SortingWithApacheSDK.fxp > > > Hi, > I recently noticed some change in behavior between Apache and Adobe Flex SDK > (when working with our application which we shifted to Apache Flex SDK some > time back). > We have always seen that doing 'sort=null' stops any further sorting to a > collection of data (in Adobe's SDK). With Apache Flex SDK I've seen this > command makes no effect and sort mechanism is active. > To prove my query, I've attached herewith two Flex projects of one is using > Adobe Flex SDK (4.6) and Apache Flex SDK (4.11.0) the other. (I confirm this > behavior is exists in 4.12.1, too). Both are same application having a list > of unsorted data binding to a List component, and a button. When you hit the > button: > - Application sort the list > - Runs a command 'sort = null' to the collection > - Add a new entry at 0th index to the collection which starts with Z > character as initial > Results when used with Adobe Flex SDK: > - Application sort the list > - List shows data as - A, B, C, D > - null assigned to the collection.sort > - List added a new Z entry at 0th index and it shows as - Z, A, B, C, D > Results when used with Apache Flex SDK: > - Application sort the list > - List shows data as - A, B, C, D > - null assigned to the collection.sort > - List added a new Z entry at bottom and it shows as - A, B, C, D, Z > Is this something an intentional change with Apache Flex SDK or its an issue. > Please, suggest. > Thanks! -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34327) NavigatorContent CreationPolicy Issue
[ https://issues.apache.org/jira/browse/FLEX-34327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-34327: - Labels: easytest (was: ) > NavigatorContent CreationPolicy Issue > - > > Key: FLEX-34327 > URL: https://issues.apache.org/jira/browse/FLEX-34327 > Project: Apache Flex > Issue Type: Bug > Components: Spark: NavigatorContent >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.8 (parity > release), Apache Flex 4.9.0, Apache Flex 4.10.0, Apache Flex 4.11.0, Apache > Flex 4.12.0 >Reporter: Imtiaz Islam > Labels: easytest > Attachments: NavigatorContentCreationPolicyIssue.zip > > > Suppose i have a viewstack with creationpolicy = auto, which has two > children, so the first child should be created first and if only i go the > second index of viewstack, the second child will be created. But > unfortunately that is not happening with navigatorcontent. Its always > getting created. I will attach the simple test case. > Note: When i used mx canvas instead of navigatorcontent the creationpolicy is > working fine. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FLEX-34349) TextInput in scroller brings up soft keyboard too soon
[ https://issues.apache.org/jira/browse/FLEX-34349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053423#comment-14053423 ] Justin Mclean commented on FLEX-34349: -- May be related to FLEX-34388 > TextInput in scroller brings up soft keyboard too soon > -- > > Key: FLEX-34349 > URL: https://issues.apache.org/jira/browse/FLEX-34349 > Project: Apache Flex > Issue Type: Bug > Components: Spark: TextInput >Affects Versions: Apache Flex 4.12.1 > Environment: iOS and Android >Reporter: Steven > Labels: easytest > Fix For: Apache Flex 4.12.1 > > > I have some textInputs in a scroller using the default skin. When you press > the scroller to move to the desired textInput the softkeyboard appears > immediately, seems like on the mouse down. This behaviour does not appear > correct. Should the soft keyboard appear only when you have stopped scrolling > and selected a textInput? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FLEX-34381) Sorting behavior changed between Adobe and Apache Flex SDK (?)
[ https://issues.apache.org/jira/browse/FLEX-34381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053424#comment-14053424 ] Santanu Karar commented on FLEX-34381: -- With the new design, there is no way to preserve previously sorting order after doing a collection.sort=null and collection.refresh() (as it was achievable with Adobe SDK); or is there a way to preserve the order even after doing a sort=null and collection.refresh() in new updated SDK? > Sorting behavior changed between Adobe and Apache Flex SDK (?) > -- > > Key: FLEX-34381 > URL: https://issues.apache.org/jira/browse/FLEX-34381 > Project: Apache Flex > Issue Type: Bug >Affects Versions: Apache Flex 4.12.0 >Reporter: Santanu Karar > Attachments: SortingWithAdobeSDK.fxp, SortingWithApacheSDK.fxp > > > Hi, > I recently noticed some change in behavior between Apache and Adobe Flex SDK > (when working with our application which we shifted to Apache Flex SDK some > time back). > We have always seen that doing 'sort=null' stops any further sorting to a > collection of data (in Adobe's SDK). With Apache Flex SDK I've seen this > command makes no effect and sort mechanism is active. > To prove my query, I've attached herewith two Flex projects of one is using > Adobe Flex SDK (4.6) and Apache Flex SDK (4.11.0) the other. (I confirm this > behavior is exists in 4.12.1, too). Both are same application having a list > of unsorted data binding to a List component, and a button. When you hit the > button: > - Application sort the list > - Runs a command 'sort = null' to the collection > - Add a new entry at 0th index to the collection which starts with Z > character as initial > Results when used with Adobe Flex SDK: > - Application sort the list > - List shows data as - A, B, C, D > - null assigned to the collection.sort > - List added a new Z entry at 0th index and it shows as - Z, A, B, C, D > Results when used with Apache Flex SDK: > - Application sort the list > - List shows data as - A, B, C, D > - null assigned to the collection.sort > - List added a new Z entry at bottom and it shows as - A, B, C, D, Z > Is this something an intentional change with Apache Flex SDK or its an issue. > Please, suggest. > Thanks! -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34345) Spark DataGrid throws a Null Pointer Exception when data provider's item is being changed by item renderer
[
https://issues.apache.org/jira/browse/FLEX-34345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-34345:
-
Labels: datagrid easytest grid itemrenderer npe (was: datagrid grid
itemrenderer npe)
> Spark DataGrid throws a Null Pointer Exception when data provider's item is
> being changed by item renderer
> --
>
> Key: FLEX-34345
> URL: https://issues.apache.org/jira/browse/FLEX-34345
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark: DataGrid, Spark: Grid
>Affects Versions: Adobe Flex SDK 4.5.1 (Release), Apache Flex 4.11.0,
> Apache Flex 4.12.1
>Reporter: Vadim Usoltsev
>Priority: Minor
> Labels: datagrid, easytest, grid, itemrenderer, npe
>
> Exception in *GridViewLayout.as:1053* occurs when data item is being changed
> by item renderer. The code:
> {code:actionscript}
> for each (var renderer:IGridItemRenderer in visibleItemRenderers)
>
> {
> var rowIndex:int = renderer.rowIndex;
> ...
> {code}
> is not null safe, because visibleItemRenderers vector can contain null items
> under some indices, made f.e. by code in *GridViewLayout.as:1753* :
> {code:actionscript}
> const renderer:IGridItemRenderer = visibleItemRenderers[index];
> visibleItemRenderers[index] = null;
> {code}
> To reproduce this, create DataGrid with data provider, that contain items
> with Date fields, and create an ItemRenderer for that column with DateField
> component, that can change the date in source data item. Error will be
> throwed when data item's field will be changed and *PropertyChangeEvent* will
> be dispatched.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (FLEX-34349) TextInput in scroller brings up soft keyboard too soon
[ https://issues.apache.org/jira/browse/FLEX-34349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-34349: - Labels: easytest (was: ) > TextInput in scroller brings up soft keyboard too soon > -- > > Key: FLEX-34349 > URL: https://issues.apache.org/jira/browse/FLEX-34349 > Project: Apache Flex > Issue Type: Bug > Components: Spark: TextInput >Affects Versions: Apache Flex 4.12.1 > Environment: iOS and Android >Reporter: Steven > Labels: easytest > Fix For: Apache Flex 4.12.1 > > > I have some textInputs in a scroller using the default skin. When you press > the scroller to move to the desired textInput the softkeyboard appears > immediately, seems like on the mouse down. This behaviour does not appear > correct. Should the soft keyboard appear only when you have stopped scrolling > and selected a textInput? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34359) RTE when accessing gridDimensions
[ https://issues.apache.org/jira/browse/FLEX-34359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-34359: - Labels: Apache easytest (was: Apache) > RTE when accessing gridDimensions > - > > Key: FLEX-34359 > URL: https://issues.apache.org/jira/browse/FLEX-34359 > Project: Apache Flex > Issue Type: Bug > Components: Spark: DataGrid >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: Windows 7 Enterprise edition, Adobe Flash builder 4.7 > Premium >Reporter: Saju Thankathurai > Labels: Apache, easytest > > Getting a RunTime Error on accessing gridDimensions. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34361) mx.states.AddItems.addItemsToArray fails with RichText & ParagraphElement
[
https://issues.apache.org/jira/browse/FLEX-34361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-34361:
-
Labels: easytest (was: )
> mx.states.AddItems.addItemsToArray fails with RichText & ParagraphElement
> -
>
> Key: FLEX-34361
> URL: https://issues.apache.org/jira/browse/FLEX-34361
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark: RichText, States
>Affects Versions: Apache Flex 4.11.0
>Reporter: Denis Johnson
> Labels: easytest
>
> When a state is used to exclude a ParagraphElement in a RichText in mxml an
> RTE is caused when the state wants to include the ParagraphElement.
> "TypeError: Error #1034: Type Coercion failed: cannot convert
> flashx.textLayout.elements::TextFlow@dad6369 to Array"
> Error occurs in: mx.states.AddItems.addItemsToArray()
> Example bellow works when state is "stateToExclude" but fails when "normal"
> {code:xml}
> ...
>
>
>
>
> ...
>
> First paragraph.
> Second paragraph.
> Optional paragraph
>
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (FLEX-34364) FlexEvent.BUTTON_DOWN events are sometimes lost
[
https://issues.apache.org/jira/browse/FLEX-34364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-34364:
-
Labels: easytest (was: )
> FlexEvent.BUTTON_DOWN events are sometimes lost
> ---
>
> Key: FLEX-34364
> URL: https://issues.apache.org/jira/browse/FLEX-34364
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark: Button
>Affects Versions: Apache Flex 4.12.0
> Environment: Mac OS X 10.9, Apache Flex 4.12.1 + AIR 13
>Reporter: Tamás Nepusz
>Priority: Minor
> Labels: easytest
> Attachments: ButtonDownBugTest.fxp
>
>
> {{FlexEvent.BUTTON_DOWN}} events are sometimes not fired for Spark Buttons.
> More precisely, they are _usually_ not fired (in ~80% of the cases) when I
> click on the button by tapping the touchpad of my MacBook Pro _and_ the
> window that contains the button is not the first window of the application.
> The events are _always_ fired properly when I click on the button using the
> mouse or the button at the bottom of my touchpad, _or_ when the button is
> contained in the first window of the application.
> I strongly suspect that this happens because {{FlexEvent.BUTTON_DOWN}} events
> are dispatched in {{ButtonBase.commitProperties()}}, but the
> {{MouseEvent.MOUSE_DOWN}} and {{MouseEvent.MOUSE_UP}} events happen so
> quickly when I tap the touchpad that {{ButtonBase.commitProperties()}} only
> gets a chance to run when the button is already up again (although this does
> not explain why it is not a problem for the first window of the application).
> This is not a big issue on its own, but note that {{DropDownController}}
> relies on the {{BUTTON_DOWN}} event to decide when to open the dropdown in a
> {{DropDownList}}, so Spark dropdowns do not work reliably in the presence of
> this bug.
> Steps to reproduce:
> # You might have to get a Mac to reproduce this issue.
> # Open the attached project.
> # Tap on the button of the first window that opens using the touchpad. Note
> that you get both a {{BUTTON_DOWN}} event and a {{CLICK}} event, and these
> are logged properly in the list shown below the button.
> # Open a new window by clicking on the button in the lower right corner.
> # Tap on the button of the new window a few times. Note that {{CLICK}} events
> are always dispatched, but in ~80% of the cases they are not preceded by a
> {{BUTTON_DOWN}} event.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (FLEX-34362) Issues with ScrollableStageText
[ https://issues.apache.org/jira/browse/FLEX-34362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-34362: - Labels: easytest scrolling stagetext textarea (was: scrolling stagetext textarea) > Issues with ScrollableStageText > --- > > Key: FLEX-34362 > URL: https://issues.apache.org/jira/browse/FLEX-34362 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Mobile >Affects Versions: Apache Flex 4.12.1 > Environment: Mainly tested on an iPhone 4 with iOS 7.1 >Reporter: HB > Labels: easytest, scrolling, stagetext, textarea > > There are several issues when using the new ScrollableStageText class inside > a Flex component (through the new Scrolling skins): > - When focusing a TextInput (guess a TextArea as well), a > softKeyboardDeactivate event is dispatched, at least on iOS. > - enabled = false doesn't work, this is because of the keepSoftKeyboardActive > function, adding a hiddenFocusStageText.editable = _editable; line > before hiddenFocusStageText.assignFocus(); works. > - Scrolling inside a TextArea component doesn't work when editable is false. > This is a real burden in some cases... I guess it's either because of > keepSoftKeyboardActive or because of the swap between the proxy image and the > StageText instance. Any further help on this issue would be really welcome. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34370) NullPointerException in TagDecoder.decodeDefineButton
[ https://issues.apache.org/jira/browse/FLEX-34370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-34370: - Labels: easytest (was: ) > NullPointerException in TagDecoder.decodeDefineButton > - > > Key: FLEX-34370 > URL: https://issues.apache.org/jira/browse/FLEX-34370 > Project: Apache Flex > Issue Type: Bug >Reporter: Guest > Labels: easytest > > I saw this when I was browsing the source code on the github mirror. > https://github.com/apache/flex-sdk/blob/develop/modules/swfutils/src/java/flash/swf/TagDecoder.java#L2181 > If I'm not mistaken, line 2181 sets t.condActions to [null], and line 2182 > causes a null pointer exception. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34365) TextInput's displayAsPassword related errors
[
https://issues.apache.org/jira/browse/FLEX-34365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-34365:
-
Labels: displayAsPassword easytest mobileTextInput password textinput
(was: displayAsPassword mobileTextInput password textinput)
> TextInput's displayAsPassword related errors
>
>
> Key: FLEX-34365
> URL: https://issues.apache.org/jira/browse/FLEX-34365
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark: TextInput
>Affects Versions: Apache Flex 4.12.0, Apache Flex 4.12.1
> Environment: Flash Builder 4.7's simulator, Android 4.2.2 (app with
> captive runtime).
> - When testing SDK 4.12.1 used the AIR 13 SDK.
> - When testing SDK 4.12.0 used the default AIR SDK.
> - When testing SDK 4.11.1 used the AIR 3.9 SDK.
> - When testing SDK 4.6 used the default AIR SDK.
>Reporter: Sebastian Toro
> Labels: displayAsPassword, easytest, mobileTextInput, password,
> textinput
> Fix For: Adobe Flex SDK 4.6 (Release), Apache Flex 4.11.0
>
>
> Run the following code on an Android mobile project:
>
> http://ns.adobe.com/mxml/2009";
> xmlns:s="library://ns.adobe.com/flex/spark"
> title="DisplayAsPassword">
>
>
>
>
>
> restrict="-A-Za-z0-9._"
> displayAsPassword="true"
>top="20" left="20" right="20"/>
> change="togglePasswordDisplay(event)"
> top="{appPassword.y + appPassword.height + 20}"
> horizontalCenter="0"/>
>
>
> When the CheckBox's selected property changes, the TextInput's
> displayAsPassword property won't. If the CheckBox's selected property changes
> and then the TextInput is focused, then the displayAsPassword property
> changes.
> The following solves the property update problem but introduces a new one:
>
> http://ns.adobe.com/mxml/2009";
> xmlns:s="library://ns.adobe.com/flex/spark"
> title="DisplayAsPassword">
>
> restrict="-A-Za-z0-9._"
> displayAsPassword="{!showPasswordButton.selected}"
>top="20" left="0" right="0"/>
> selected="false"
> top="{appPassword.y + appPassword.height + 20}"
> horizontalCenter="0"/>
>
>
> When the displayAsPassword property is updated to false and then the
> TextInput is focused, the text blinking cursor will be positioned where the
> end of the text would be if the displayAsPassword was true.
> This problem is not present in version 4.6 and 4.11 from the SDK, so the bug
> must be introduced on 4.12.0.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (FLEX-34371) how TagEncoder handles duplicate define* tags
[
https://issues.apache.org/jira/browse/FLEX-34371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053416#comment-14053416
]
Justin Mclean commented on FLEX-34371:
--
Can you provide some code or a swf to show this issue thanks.
> how TagEncoder handles duplicate define* tags
> -
>
> Key: FLEX-34371
> URL: https://issues.apache.org/jira/browse/FLEX-34371
> Project: Apache Flex
> Issue Type: Bug
>Affects Versions: Apache Flex 4.12.0
>Reporter: Guest
>
> Suppose there are two DefineEditText tags that are the same by .equals, and a
> TagEncoder handles them. This writes them both to the SWF, but assigns them
> the same character ID. Adobe's Flash player can load the SWF fine, but it
> causes swfdump to crash with an exception like the following:
> {code}
> Exception in thread "main" java.lang.IllegalArgumentException: symbol 154
> redefined by identical tag
> at flash.swf.Dictionary.add(Dictionary.java:142)
> at flash.swf.TagDecoder.decodeDefineEditText(TagDecoder.java:1160)
> at flash.swf.TagDecoder.decodeTag(TagDecoder.java:319)
> at flash.swf.TagDecoder.decodeTags(TagDecoder.java:194)
> at flash.swf.TagDecoder.parse(TagDecoder.java:142)
> at flash.swf.tools.SwfxPrinter.dumpSwf(SwfxPrinter.java:2318)
> at flash.swf.tools.SwfxPrinter.main(SwfxPrinter.java:2225)
> {code}
> Actual result:
> defineEditText(tag) in TagEncoder calls
> {code:java}
> int id = dict.add(tag);
> {code}
> When serializing the second DefineEditText, the Dictionary finds the first
> one and returns its ID. Then, the defineEditText(tag) method writes the
> second copy with the first one's ID.
> Expected result:
> either
> - it writes the duplicate with a new ID or
> - it does not write anything and uses the first copy's ID for references to
> the second.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (FLEX-34372) Disabled form gets focus and key events
[ https://issues.apache.org/jira/browse/FLEX-34372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-34372: - Labels: easytest (was: ) > Disabled form gets focus and key events > --- > > Key: FLEX-34372 > URL: https://issues.apache.org/jira/browse/FLEX-34372 > Project: Apache Flex > Issue Type: Bug > Components: Focus Manager >Affects Versions: Apache Flex 4.11.0 > Environment: Windows 7 64bit Japanese, Adobe AIR 3.8.0.1430 >Reporter: Shigeru Nakagaki > Labels: easytest > Attachments: DisabledFocusTest_src.zip > > > A form which "enabled" is false gets focus and key events > Step 1 : build an attached source > Step 2 : input "bbb" at second s:TextInput > A pop-up opens. > Step 3 : Click the s:TextInput of Step 2 > It gets focus. > Step 4 : Press "ENTER" key > it gets key events. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34373) spark.components.Alert should set a focus to defaultButton
[
https://issues.apache.org/jira/browse/FLEX-34373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-34373:
-
Labels: easyfix easytest (was: )
> spark.components.Alert should set a focus to defaultButton
> --
>
> Key: FLEX-34373
> URL: https://issues.apache.org/jira/browse/FLEX-34373
> Project: Apache Flex
> Issue Type: Bug
>Affects Versions: Apache Flex 4.12.0
> Environment: Windows 7 64bit Japanese, Flex SDK 12.1, AIR 14
>Reporter: Shigeru Nakagaki
>Priority: Minor
> Labels: easyfix, easytest
>
> Alert.show("Goal!!!", "Information", Alert.OK, null, null, null, Alert.OK);
> Even after creation-complete of Alert, alert.defaultButton is still null.
> And we have to press TAB key to set focus the button.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (FLEX-34380) TextInput with prompt displays black prompt
[ https://issues.apache.org/jira/browse/FLEX-34380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-34380: - Labels: TextArea TextInput callout easytest prompt (was: TextArea TextInput callout prompt) > TextInput with prompt displays black prompt > --- > > Key: FLEX-34380 > URL: https://issues.apache.org/jira/browse/FLEX-34380 > Project: Apache Flex > Issue Type: Bug > Components: Spark: TextArea, Spark: TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.12.0 >Reporter: Alexander Konovalov > Labels: TextArea, TextInput, callout, easytest, prompt > > The reason of the bug is component visibility changes without data changes. > Steps to reproduce (the easiest way to reproduce, but bug persists almost > everywhere): > 1. Create AIR application (add mobilecomponents.swc). > 2. Add CalloutButton > 3. Add spark TextInput inside CalloutButton with some prompt text. > 4. Run. Click on CalloutButton -> grey prompt in TextInput. > 5. Close and open CalloutButton second time -> black color for prompt > Code: > > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FLEX-34381) Sorting behavior changed between Adobe and Apache Flex SDK (?)
[ https://issues.apache.org/jira/browse/FLEX-34381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053415#comment-14053415 ] Justin Mclean commented on FLEX-34381: -- Was an change to fix several bugs involved with sorting and filtering. After sorting is set to null, collection.refresh() should be called, just like then setting up the sort order the sort order is not actually removed until collection.refresh() is called. > Sorting behavior changed between Adobe and Apache Flex SDK (?) > -- > > Key: FLEX-34381 > URL: https://issues.apache.org/jira/browse/FLEX-34381 > Project: Apache Flex > Issue Type: Bug >Affects Versions: Apache Flex 4.12.0 >Reporter: Santanu Karar > Attachments: SortingWithAdobeSDK.fxp, SortingWithApacheSDK.fxp > > > Hi, > I recently noticed some change in behavior between Apache and Adobe Flex SDK > (when working with our application which we shifted to Apache Flex SDK some > time back). > We have always seen that doing 'sort=null' stops any further sorting to a > collection of data (in Adobe's SDK). With Apache Flex SDK I've seen this > command makes no effect and sort mechanism is active. > To prove my query, I've attached herewith two Flex projects of one is using > Adobe Flex SDK (4.6) and Apache Flex SDK (4.11.0) the other. (I confirm this > behavior is exists in 4.12.1, too). Both are same application having a list > of unsorted data binding to a List component, and a button. When you hit the > button: > - Application sort the list > - Runs a command 'sort = null' to the collection > - Add a new entry at 0th index to the collection which starts with Z > character as initial > Results when used with Adobe Flex SDK: > - Application sort the list > - List shows data as - A, B, C, D > - null assigned to the collection.sort > - List added a new Z entry at 0th index and it shows as - Z, A, B, C, D > Results when used with Apache Flex SDK: > - Application sort the list > - List shows data as - A, B, C, D > - null assigned to the collection.sort > - List added a new Z entry at bottom and it shows as - A, B, C, D, Z > Is this something an intentional change with Apache Flex SDK or its an issue. > Please, suggest. > Thanks! -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34384) Inconsistent behaviour when binding to xml data
[ https://issues.apache.org/jira/browse/FLEX-34384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-34384: - Labels: easytest (was: ) > Inconsistent behaviour when binding to xml data > --- > > Key: FLEX-34384 > URL: https://issues.apache.org/jira/browse/FLEX-34384 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Compiler, Data Binding >Affects Versions: Apache Flex 4.12.1 >Reporter: Mei Xue > Labels: easytest > Attachments: xmlBindingTestFlex3.mxml, xmlBindingTestFlex4.mxml > > > When working on upgrading our application from Flex 3.3 to Flex 4.12.1, I > noticed that in Flex 4.12.1 (4.11.0 too), binding to xml.@someattribute > works, but binding to this.xml.@someattribute doesn't. Both works in Flex 3.3. > In Flex 4.12.1, if binding to xml.@someattribute first, then binding to > this.xml.@someattribute works. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34388) ScrollableStageText opens keyboard with no focus within Scroller
[ https://issues.apache.org/jira/browse/FLEX-34388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-34388: - Labels: ScrollableStageText Scroller Softkeyboard easyfix easytest (was: ScrollableStageText Scroller Softkeyboard) > ScrollableStageText opens keyboard with no focus within Scroller > > > Key: FLEX-34388 > URL: https://issues.apache.org/jira/browse/FLEX-34388 > Project: Apache Flex > Issue Type: Bug > Components: Mobile: ScrollableStageText >Affects Versions: Apache Flex 4.12.1 >Reporter: Colin Childs >Priority: Minor > Labels: ScrollableStageText, Scroller, Softkeyboard, easyfix, > easytest > Attachments: SoftkeyboardBugTest.fxp > > > A ScrollableStageText component within a Scroller will raise the softkeyboard > as you scroll. It should only open the keyboard after a full click, not > during a scroll gesture. > To reproduce: > 1) Install the attached test project on a device. > 2) Scroll up and down the screen. Notice that as you scroll, the softkeyboard > comes up with no focused input, obscuring your view of the scroller content. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FLEX-34389) Different behaviour when binding to xmlroot.@attribute.toString().length and xmlroot.child.@attribute.toString().length
[ https://issues.apache.org/jira/browse/FLEX-34389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053411#comment-14053411 ] Justin Mclean commented on FLEX-34389: -- Is this an issue with Adobe Flex 4.6? > Different behaviour when binding to xmlroot.@attribute.toString().length and > xmlroot.child.@attribute.toString().length > --- > > Key: FLEX-34389 > URL: https://issues.apache.org/jira/browse/FLEX-34389 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Compiler, Data Binding >Affects Versions: Apache Flex 4.11.0, Apache Flex 4.12.1 >Reporter: Mei Xue > Labels: easytest > Attachments: keepFlagTestFlex3.mxml, keepFlagTestFlex4.mxml > > > In Flex 4 (4.12.1 and 4.11.0), binding to > xmlroot.child.@attribute.toString().length works if compile the application > with keep-generated-actionscript flag. Otherwise, it gives this runtime error > (_testXml is the xml data and keepFlagTest is the application): > ReferenceError: Error #1069: Property _testXml not found on keepFlagTest and > there is no default value. > at _keepFlagTestWatcherSetupUtil/setup() ... > Note that binding to xmlroot.child.@attribute.toString().length works in Flex > 3 (3.3) and binding to xmlroot.@attribute.toString().length works in both > Flex 3 (3.3) and Flex 4 (4.12.1 and 4.11.0). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34390) SkinnableTextBase bug (found in Flex 4.13.0 RC2)
[
https://issues.apache.org/jira/browse/FLEX-34390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-34390:
-
Labels: easytest (was: )
> SkinnableTextBase bug (found in Flex 4.13.0 RC2)
>
>
> Key: FLEX-34390
> URL: https://issues.apache.org/jira/browse/FLEX-34390
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark: TextArea, Spark: TextInput
>Affects Versions: Apache Flex 4.13.0
> Environment: Tested on AIR 14 Simulator for iPad/iPhone
>Reporter: DarkStone
>Priority: Minor
> Labels: easytest
> Attachments: SkinnableTextBase bug (found in Flex 4.13.0 RC2).png
>
>
> [Short story]
> There is a bug in SkinnableTextBase, inside the function body of "private
> function textDisplay_changeHandler(event:Event):void", the skin.currentState
> is null when running on mobile, I don't know how to fix it, but at least I
> know we should add a null check to the skin.currentState.
> Please see the screenshot I attached:
> https://issues.apache.org/jira/secure/attachment/12653403/SkinnableTextBase%20bug%20%28found%20in%20Flex%204.13.0%20RC2%29.png
> [Steps to reproduce the bug]
> 1. Create a subclass of SkinnableComponent, name the subclass SimpleTest.
> 2. Define a SkinPart of SimpleTest:
> [SkinPart(required="true")]
> public var queryInput:TextInput;
> 3. override partAdded function for SimpleTest:
> override protected function partAdded(partName:String, instance:Object):void
> {
> if ( instance == queryInput ) {
> queryInput.text = "Hello World";
> }
> }
> 4. Create the SimpleTestSkin.mxml for SimpleTest, use the id="queryInput"/> to bind the SkinPart, use the TextInput's default skin.
> 5. Bind the SimpleTestSkin.mxml to SimpleTest using CSS.
> s|SkinnableComponent.simpleTest
> {
> skinClass: ClassReference("skin.SimpleTestSkin");
> }
> 6. Put inside
> 7. Run the application on Web or Desktop, no problems.
> 8. Run the application on AIR Simulator for mobile or run it on real mobile
> devices, will encounter the following errors:
> TypeError: Error #1009: Cannot access a property or method of a null object
> reference.
> at
> spark.components.supportClasses::SkinnableTextBase/textDisplay_changeHandler()[/Users/aharui/release4.13.0/frameworks/projects/spark/src/spark/components/supportClasses/SkinnableTextBase.as:2703]
> at flash.events::EventDispatcher/dispatchEventFunction()
> at flash.events::EventDispatcher/dispatchEvent()
> at
> mx.core::UIComponent/dispatchEvent()[/Users/aharui/release4.13.0/frameworks/projects/framework/src/mx/core/UIComponent.as:13682]
> at spark.components.supportClasses::ScrollableStageText/set
> text()[/Users/aharui/release4.13.0/frameworks/projects/mobilecomponents/src/spark/components/supportClasses/ScrollableStageText.as:1016]
> at spark.components.supportClasses::SkinnableTextBase/set
> text()[/Users/aharui/release4.13.0/frameworks/projects/spark/src/spark/components/supportClasses/SkinnableTextBase.as:1410]
> at spark.components::TextInput/set
> text()[/Users/aharui/release4.13.0/frameworks/projects/spark/src/spark/components/TextInput.as:288]
> at
> global/SYSTEM.LIB.display.updaters::updateTextComponentByCharacterAndOS()[D:\VLP\FLEX\NewsCenterDesktop\src\SYSTEM\LIB\display\updaters\updateTextComponentByCharacterAndOS.as:41]
> at
> SYSTEM.COM.panes::FeedBasicEditorPane/partAdded()[D:\VLP\FLEX\NewsCenterDesktop\src\SYSTEM\COM\panes\FeedBasicEditorPane.as:119]
> at
> SYSTEM.COM.panes::FeedEssentialEditorPane/partAdded()[D:\VLP\FLEX\NewsCenterDesktop\src\SYSTEM\COM\panes\FeedEssentialEditorPane.as:112]
> at
> SYSTEM.COM.panes::SiteEditorPane/partAdded()[D:\VLP\FLEX\NewsCenterDesktop\src\SYSTEM\COM\panes\SiteEditorPane.as:65]
> at
> spark.components.supportClasses::SkinnableComponent/findSkinParts()[/Users/aharui/release4.13.0/frameworks/projects/spark/src/spark/components/supportClasses/SkinnableComponent.as:751]
> at
> spark.components.supportClasses::SkinnableComponent/attachSkin()[/Users/aharui/release4.13.0/frameworks/projects/spark/src/spark/components/supportClasses/SkinnableComponent.as:716]
> at
> spark.components.supportClasses::SkinnableComponent/validateSkinChange()[/Users/aharui/release4.13.0/frameworks/projects/spark/src/spark/components/supportClasses/SkinnableComponent.as:457]
> at
> spark.components.supportClasses::SkinnableComponent/createChildren()[/Users/aharui/release4.13.0/frameworks/projects/spark/src/spark/components/supportClasses/SkinnableComponent.as:416]
> at
> mx.core::UIComponent/initialize()[/Users/aharui/release4.13.0/frameworks/projects/framework/src/mx/core/UIComponent.as:7695]
> at
> mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::c
[jira] [Updated] (FLEX-34389) Different behaviour when binding to xmlroot.@attribute.toString().length and xmlroot.child.@attribute.toString().length
[ https://issues.apache.org/jira/browse/FLEX-34389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-34389: - Labels: easytest (was: ) > Different behaviour when binding to xmlroot.@attribute.toString().length and > xmlroot.child.@attribute.toString().length > --- > > Key: FLEX-34389 > URL: https://issues.apache.org/jira/browse/FLEX-34389 > Project: Apache Flex > Issue Type: Bug > Components: .Unspecified - Compiler, Data Binding >Affects Versions: Apache Flex 4.11.0, Apache Flex 4.12.1 >Reporter: Mei Xue > Labels: easytest > Attachments: keepFlagTestFlex3.mxml, keepFlagTestFlex4.mxml > > > In Flex 4 (4.12.1 and 4.11.0), binding to > xmlroot.child.@attribute.toString().length works if compile the application > with keep-generated-actionscript flag. Otherwise, it gives this runtime error > (_testXml is the xml data and keepFlagTest is the application): > ReferenceError: Error #1069: Property _testXml not found on keepFlagTest and > there is no default value. > at _keepFlagTestWatcherSetupUtil/setup() ... > Note that binding to xmlroot.child.@attribute.toString().length works in Flex > 3 (3.3) and binding to xmlroot.@attribute.toString().length works in both > Flex 3 (3.3) and Flex 4 (4.12.1 and 4.11.0). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34391) ScrollableStageText with large y value crashes app
[ https://issues.apache.org/jira/browse/FLEX-34391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-34391: - Labels: ScrollableStageText easytest (was: ScrollableStageText) > ScrollableStageText with large y value crashes app > -- > > Key: FLEX-34391 > URL: https://issues.apache.org/jira/browse/FLEX-34391 > Project: Apache Flex > Issue Type: Bug > Components: Mobile: ScrollableStageText >Affects Versions: Apache Flex 4.12.1 > Environment: All >Reporter: Colin Childs >Priority: Critical > Labels: ScrollableStageText, easytest > Attachments: ScrollableStageTextTest.fxp > > > When calculating the global viewport during the initial layout of a > ScrollableStageText component, the y value can exceed the maximum allowed y > value of StageText, causing the app to crash. The exact y value required to > crash it varies based on scale, but globally, 8192 is the breaking point. > This became an issue for me when placing user generated content with text > inputs within a scroller. > To replicate: > 1) Create a new application > 2) Place a TextInput control inside the view with a large y value (~10,000) > 3) Run the app and see it crash > I have included a sample mobile application that demonstrates this issue and > a workaround I used to fix it. As a workaround, I extend ScrollableStageText > and override getGlobalViewPort, setting the y value to the min of the > globalRect.y and stage.stageHeight, and the same for the x value as well. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FLEX-34393) installer should remember language
[ https://issues.apache.org/jira/browse/FLEX-34393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-34393: - Labels: easyfix installer (was: installer) > installer should remember language > -- > > Key: FLEX-34393 > URL: https://issues.apache.org/jira/browse/FLEX-34393 > Project: Apache Flex > Issue Type: Improvement > Components: InstallApacheFlex >Affects Versions: Install Apache Flex 3.0 >Reporter: João Fernandes >Priority: Minor > Labels: easyfix, installer > > if a user selects a different user language, that option should be remembered > and the next time the installer is opened, it should load the language > previously selected. -- This message was sent by Atlassian JIRA (v6.2#6252)
