[jira] [Created] (FLEX-33371) On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events
Erik Thomas created FLEX-33371: -- Summary: On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events Key: FLEX-33371 URL: https://issues.apache.org/jira/browse/FLEX-33371 Project: Apache Flex Issue Type: Bug Components: Mobile: MobileApplication Affects Versions: Adobe Flex SDK 4.6 (Release) Environment: Samsung Galaxy Express and Galaxy S III Android Phones, FlashBuilder 4.7 Premium on Windows 7, debugging through USB as well as deployed release builds, iPhone and iPad, but the problem doesn't exist on iOS devices, only Android Reporter: Erik Thomas Priority: Critical Fix For: Adobe Flex SDK 4.6 (Release) Orientation changes on Android devices always fire the following events in this order: ViewNavigatorEvent.VIEW_DEACTIVATE Event.DEACTIVATE StageOrientationEvent.ORIENTATION_CHANGE The first two events are a defect. They must not fire simply because the user changed the orientation of the phone. The result of this defect is that we cannot do two very important things: 1. Use view state changes to hide/show layouts, using includeIn property on containers and components. On Android, components that are not included for a given state are destroyed yet they have state we want to maintain which is why we don't change Views. 2. We cannot know when the user navigates away from our application, for example to press the Home key. We have certain cleanup we must do in our complex connected app that streams FMS data, etc., and cannot keep sockets open for hours or days. On iOS, this is not a problem. Only Android has this bug and it's blocking us from releasing our product on Android. iOS does not have this defect. -- 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-33371) On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events
[ https://issues.apache.org/jira/browse/FLEX-33371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Thomas updated FLEX-33371: --- Attachment: AndroidDeactivateOnOrientationChangeDefect.zip Unzip the attached project, start FB 4.7 and set your workspace to the directory where you put this. Open, build, debug on an Android device and watch the trace output to see that the bogus events are being fired as a result of a simple orientation change. We've tested this on two phones and with release builds as well and our app just unloads on every orientation change because we are listening for the Event.DEACTIVATE to close sockets, etc. and unload the app. > On Android, changing orientation fires Event.DEACTIVATE and > FlexEvent.VIEW_DEACTIVATE events > > > Key: FLEX-33371 > URL: https://issues.apache.org/jira/browse/FLEX-33371 > Project: Apache Flex > Issue Type: Bug > Components: Mobile: MobileApplication >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: Samsung Galaxy Express and Galaxy S III Android Phones, > FlashBuilder 4.7 Premium on Windows 7, debugging through USB as well as > deployed release builds, iPhone and iPad, but the problem doesn't exist on > iOS devices, only Android >Reporter: Erik Thomas >Priority: Critical > Fix For: Adobe Flex SDK 4.6 (Release) > > Attachments: AndroidDeactivateOnOrientationChangeDefect.zip > > > Orientation changes on Android devices always fire the following events in > this order: > ViewNavigatorEvent.VIEW_DEACTIVATE > Event.DEACTIVATE > StageOrientationEvent.ORIENTATION_CHANGE > The first two events are a defect. They must not fire simply because the user > changed the orientation of the phone. > The result of this defect is that we cannot do two very important things: > 1. Use view state changes to hide/show layouts, using includeIn property on > containers and components. On Android, components that are not included for a > given state are destroyed yet they have state we want to maintain which is > why we don't change Views. > 2. We cannot know when the user navigates away from our application, for > example to press the Home key. We have certain cleanup we must do in our > complex connected app that streams FMS data, etc., and cannot keep sockets > open for hours or days. > On iOS, this is not a problem. Only Android has this bug and it's blocking us > from releasing our product on Android. iOS does not have this defect. -- 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-33371) On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events
[ https://issues.apache.org/jira/browse/FLEX-33371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565693#comment-13565693 ] Erik Thomas commented on FLEX-33371: We've tried for the better part of a day to find a workaround, but we use orientation view states extensively and need to react to orientation changes to invalidate "includeIn" property on containers and components to adjust the layout for the appropriate orientation. On iOS, this is great. On Android, by the time our orientation change event is fired, the app has already deactivated our View and destroyed all the components. Unfortunately, we developed our app with two iOS devices but no Android devices. Instead, we tested many Android form factors using simulators. Finally started testing our v1 product on more devices and discovered this problem on devices that doesn't exist in the simulators. We also need to know when the user leaves our app so we can unload it because it's highly connected with NetStream/FMS connections, etc., and on Android, because viewDeactive destroys components that trigger Controller initialization, etc., when we lose state, we can't recreate it if the user comes back to the app in the same View they left without tearing it down and putting it all back together again. This should be an incredibly simple fix. In the native extension library for Android, when there is simply an orientation change, don't propagate DEACTIVATE and VIEW_DEACTIVATE events to the AIR client. > On Android, changing orientation fires Event.DEACTIVATE and > FlexEvent.VIEW_DEACTIVATE events > > > Key: FLEX-33371 > URL: https://issues.apache.org/jira/browse/FLEX-33371 > Project: Apache Flex > Issue Type: Bug > Components: Mobile: MobileApplication >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: Samsung Galaxy Express and Galaxy S III Android Phones, > FlashBuilder 4.7 Premium on Windows 7, debugging through USB as well as > deployed release builds, iPhone and iPad, but the problem doesn't exist on > iOS devices, only Android >Reporter: Erik Thomas >Priority: Critical > Fix For: Adobe Flex SDK 4.6 (Release) > > Attachments: AndroidDeactivateOnOrientationChangeDefect.zip > > > Orientation changes on Android devices always fire the following events in > this order: > ViewNavigatorEvent.VIEW_DEACTIVATE > Event.DEACTIVATE > StageOrientationEvent.ORIENTATION_CHANGE > The first two events are a defect. They must not fire simply because the user > changed the orientation of the phone. > The result of this defect is that we cannot do two very important things: > 1. Use view state changes to hide/show layouts, using includeIn property on > containers and components. On Android, components that are not included for a > given state are destroyed yet they have state we want to maintain which is > why we don't change Views. > 2. We cannot know when the user navigates away from our application, for > example to press the Home key. We have certain cleanup we must do in our > complex connected app that streams FMS data, etc., and cannot keep sockets > open for hours or days. > On iOS, this is not a problem. Only Android has this bug and it's blocking us > from releasing our product on Android. iOS does not have this defect. -- 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-33371) On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events
[ https://issues.apache.org/jira/browse/FLEX-33371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565697#comment-13565697 ] Erik Thomas commented on FLEX-33371: Also, listening for viewDeactivate and Deactivate events and doing an event.preventDefault is an oversimplified approach to working around this problem. The reason is the order in which these events are fired. If VIEW_DEACTIVATE is fired before ORIENTATION_CHANGE, how do you know what caused the VIEW_DEACTIVATE event to fire? If the user left the building, or simply changed orientation. These are two distinct situations that we must know about. We've tried stupid stuff like a timer that starts on VIEW_DEACTIVATE, and we stop it on ORIENTATION_CHANGE and if the timer runs to completion, then we know they didn't simply change orientation, but the timing of this approach is unreliable at best in our tests. We've found many corner case problems we have to deal with on this approach. > On Android, changing orientation fires Event.DEACTIVATE and > FlexEvent.VIEW_DEACTIVATE events > > > Key: FLEX-33371 > URL: https://issues.apache.org/jira/browse/FLEX-33371 > Project: Apache Flex > Issue Type: Bug > Components: Mobile: MobileApplication >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: Samsung Galaxy Express and Galaxy S III Android Phones, > FlashBuilder 4.7 Premium on Windows 7, debugging through USB as well as > deployed release builds, iPhone and iPad, but the problem doesn't exist on > iOS devices, only Android >Reporter: Erik Thomas >Priority: Critical > Fix For: Adobe Flex SDK 4.6 (Release) > > Attachments: AndroidDeactivateOnOrientationChangeDefect.zip > > > Orientation changes on Android devices always fire the following events in > this order: > ViewNavigatorEvent.VIEW_DEACTIVATE > Event.DEACTIVATE > StageOrientationEvent.ORIENTATION_CHANGE > The first two events are a defect. They must not fire simply because the user > changed the orientation of the phone. > The result of this defect is that we cannot do two very important things: > 1. Use view state changes to hide/show layouts, using includeIn property on > containers and components. On Android, components that are not included for a > given state are destroyed yet they have state we want to maintain which is > why we don't change Views. > 2. We cannot know when the user navigates away from our application, for > example to press the Home key. We have certain cleanup we must do in our > complex connected app that streams FMS data, etc., and cannot keep sockets > open for hours or days. > On iOS, this is not a problem. Only Android has this bug and it's blocking us > from releasing our product on Android. iOS does not have this defect. -- 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-33371) On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events
[ https://issues.apache.org/jira/browse/FLEX-33371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565735#comment-13565735 ] OmPrakash Muppirala commented on FLEX-33371: Erik, I dont have my USB cable with me, so I am not able to test your project. Have you tried listening to Event.EXITING and Event.DEACTIVATE events thrown by NativeApplication.nativeApplication to do your cleanup? That way, you can bypass the spurious viewDeactivate events by not listening to them. The docs [1] seems to suggest that this is the correct way. I apologize if this is not related to your problem. I will get a chance to look at this later tonight if you havent solved your issue by then. Thanks, Om [1] http://help.adobe.com/en_US/flex/mobileapps/WSa122979b4619725672e48c412a3e152164-8000.html > On Android, changing orientation fires Event.DEACTIVATE and > FlexEvent.VIEW_DEACTIVATE events > > > Key: FLEX-33371 > URL: https://issues.apache.org/jira/browse/FLEX-33371 > Project: Apache Flex > Issue Type: Bug > Components: Mobile: MobileApplication >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: Samsung Galaxy Express and Galaxy S III Android Phones, > FlashBuilder 4.7 Premium on Windows 7, debugging through USB as well as > deployed release builds, iPhone and iPad, but the problem doesn't exist on > iOS devices, only Android >Reporter: Erik Thomas >Priority: Critical > Fix For: Adobe Flex SDK 4.6 (Release) > > Attachments: AndroidDeactivateOnOrientationChangeDefect.zip > > > Orientation changes on Android devices always fire the following events in > this order: > ViewNavigatorEvent.VIEW_DEACTIVATE > Event.DEACTIVATE > StageOrientationEvent.ORIENTATION_CHANGE > The first two events are a defect. They must not fire simply because the user > changed the orientation of the phone. > The result of this defect is that we cannot do two very important things: > 1. Use view state changes to hide/show layouts, using includeIn property on > containers and components. On Android, components that are not included for a > given state are destroyed yet they have state we want to maintain which is > why we don't change Views. > 2. We cannot know when the user navigates away from our application, for > example to press the Home key. We have certain cleanup we must do in our > complex connected app that streams FMS data, etc., and cannot keep sockets > open for hours or days. > On iOS, this is not a problem. Only Android has this bug and it's blocking us > from releasing our product on Android. iOS does not have this defect. -- 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-33371) On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events
[ https://issues.apache.org/jira/browse/FLEX-33371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565789#comment-13565789 ] Erik Thomas commented on FLEX-33371: Hi OmPrakash: The NativeApplication DEACTIVATE event also fires on orientation change events. Event.DEACTIVATE event was fired! NativeApplication.Event.DEACTIVATE event was fired! StageOrientationEvent.ORIENTATION_CHANGE event was fired! Also, NativeApplication.EXITING never fires when the user presses the Home button or switches applications. This event seems useless and never fires for any reason. Thanks for taking a look! BTW, I plan to look into joining as a contributor after my current contract is finished, but I don't have time to do that now or I might look into this issue. Thanks! Erik Erik J. Thomas CEO | Principal Developer E. J. Thomas & Associates, LLC 266 Peakview Rd, Boulder, CO 80302 303-440-8384 (office) | 303-304-1466 (mobile) ejtho...@ejthomas.com CONFIDENTIALITY NOTICE: This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s). Any disclosure, copying, distribution, or other use of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. > On Android, changing orientation fires Event.DEACTIVATE and > FlexEvent.VIEW_DEACTIVATE events > > > Key: FLEX-33371 > URL: https://issues.apache.org/jira/browse/FLEX-33371 > Project: Apache Flex > Issue Type: Bug > Components: Mobile: MobileApplication >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: Samsung Galaxy Express and Galaxy S III Android Phones, > FlashBuilder 4.7 Premium on Windows 7, debugging through USB as well as > deployed release builds, iPhone and iPad, but the problem doesn't exist on > iOS devices, only Android >Reporter: Erik Thomas >Priority: Critical > Fix For: Adobe Flex SDK 4.6 (Release) > > Attachments: AndroidDeactivateOnOrientationChangeDefect.zip > > > Orientation changes on Android devices always fire the following events in > this order: > ViewNavigatorEvent.VIEW_DEACTIVATE > Event.DEACTIVATE > StageOrientationEvent.ORIENTATION_CHANGE > The first two events are a defect. They must not fire simply because the user > changed the orientation of the phone. > The result of this defect is that we cannot do two very important things: > 1. Use view state changes to hide/show layouts, using includeIn property on > containers and components. On Android, components that are not included for a > given state are destroyed yet they have state we want to maintain which is > why we don't change Views. > 2. We cannot know when the user navigates away from our application, for > example to press the Home key. We have certain cleanup we must do in our > complex connected app that streams FMS data, etc., and cannot keep sockets > open for hours or days. > On iOS, this is not a problem. Only Android has this bug and it's blocking us > from releasing our product on Android. iOS does not have this defect. -- 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-33371) On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events
[ https://issues.apache.org/jira/browse/FLEX-33371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565837#comment-13565837 ] OmPrakash Muppirala commented on FLEX-33371: Ah, then this seems to be an AIR runtime issue. You might want to get this on Adobe's radar. I looked at the ViewNavigatorApplication class and I dont see anything fishy going on there. I see some other folks having this and similar issues as well: http://forums.adobe.com/thread/1007852 http://forums.adobe.com/message/4281681#4281681 A very similar bug that was fixed recently in the latest AIR runtime: https://bugbase.adobe.com/index.cfm?event=bug&id=3144722 Which version of AIR are you on? > On Android, changing orientation fires Event.DEACTIVATE and > FlexEvent.VIEW_DEACTIVATE events > > > Key: FLEX-33371 > URL: https://issues.apache.org/jira/browse/FLEX-33371 > Project: Apache Flex > Issue Type: Bug > Components: Mobile: MobileApplication >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: Samsung Galaxy Express and Galaxy S III Android Phones, > FlashBuilder 4.7 Premium on Windows 7, debugging through USB as well as > deployed release builds, iPhone and iPad, but the problem doesn't exist on > iOS devices, only Android >Reporter: Erik Thomas >Priority: Critical > Fix For: Adobe Flex SDK 4.6 (Release) > > Attachments: AndroidDeactivateOnOrientationChangeDefect.zip > > > Orientation changes on Android devices always fire the following events in > this order: > ViewNavigatorEvent.VIEW_DEACTIVATE > Event.DEACTIVATE > StageOrientationEvent.ORIENTATION_CHANGE > The first two events are a defect. They must not fire simply because the user > changed the orientation of the phone. > The result of this defect is that we cannot do two very important things: > 1. Use view state changes to hide/show layouts, using includeIn property on > containers and components. On Android, components that are not included for a > given state are destroyed yet they have state we want to maintain which is > why we don't change Views. > 2. We cannot know when the user navigates away from our application, for > example to press the Home key. We have certain cleanup we must do in our > complex connected app that streams FMS data, etc., and cannot keep sockets > open for hours or days. > On iOS, this is not a problem. Only Android has this bug and it's blocking us > from releasing our product on Android. iOS does not have this defect. -- 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-33371) On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events
[ https://issues.apache.org/jira/browse/FLEX-33371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565840#comment-13565840 ] OmPrakash Muppirala commented on FLEX-33371: This particular comment on the bugbase could be a possible workaround: "For workaround this issue, you can put in inside of the app.xml to avoid invoke Event trigger by surface Change. " > On Android, changing orientation fires Event.DEACTIVATE and > FlexEvent.VIEW_DEACTIVATE events > > > Key: FLEX-33371 > URL: https://issues.apache.org/jira/browse/FLEX-33371 > Project: Apache Flex > Issue Type: Bug > Components: Mobile: MobileApplication >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: Samsung Galaxy Express and Galaxy S III Android Phones, > FlashBuilder 4.7 Premium on Windows 7, debugging through USB as well as > deployed release builds, iPhone and iPad, but the problem doesn't exist on > iOS devices, only Android >Reporter: Erik Thomas >Priority: Critical > Fix For: Adobe Flex SDK 4.6 (Release) > > Attachments: AndroidDeactivateOnOrientationChangeDefect.zip > > > Orientation changes on Android devices always fire the following events in > this order: > ViewNavigatorEvent.VIEW_DEACTIVATE > Event.DEACTIVATE > StageOrientationEvent.ORIENTATION_CHANGE > The first two events are a defect. They must not fire simply because the user > changed the orientation of the phone. > The result of this defect is that we cannot do two very important things: > 1. Use view state changes to hide/show layouts, using includeIn property on > containers and components. On Android, components that are not included for a > given state are destroyed yet they have state we want to maintain which is > why we don't change Views. > 2. We cannot know when the user navigates away from our application, for > example to press the Home key. We have certain cleanup we must do in our > complex connected app that streams FMS data, etc., and cannot keep sockets > open for hours or days. > On iOS, this is not a problem. Only Android has this bug and it's blocking us > from releasing our product on Android. iOS does not have this defect. -- 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-33371) On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events
[ https://issues.apache.org/jira/browse/FLEX-33371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565882#comment-13565882 ] Justin Mclean commented on FLEX-33371: -- It may be a native Android issue. In native apps when when you change orientation the current activity is stopped and restated. The exiting event is probably dispatched when the application native onDestory method is called this can occur sometime (or even not at all) after the user has exited the application when the OS decides it needs more memory. > On Android, changing orientation fires Event.DEACTIVATE and > FlexEvent.VIEW_DEACTIVATE events > > > Key: FLEX-33371 > URL: https://issues.apache.org/jira/browse/FLEX-33371 > Project: Apache Flex > Issue Type: Bug > Components: Mobile: MobileApplication >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: Samsung Galaxy Express and Galaxy S III Android Phones, > FlashBuilder 4.7 Premium on Windows 7, debugging through USB as well as > deployed release builds, iPhone and iPad, but the problem doesn't exist on > iOS devices, only Android >Reporter: Erik Thomas >Priority: Critical > Fix For: Adobe Flex SDK 4.6 (Release) > > Attachments: AndroidDeactivateOnOrientationChangeDefect.zip > > > Orientation changes on Android devices always fire the following events in > this order: > ViewNavigatorEvent.VIEW_DEACTIVATE > Event.DEACTIVATE > StageOrientationEvent.ORIENTATION_CHANGE > The first two events are a defect. They must not fire simply because the user > changed the orientation of the phone. > The result of this defect is that we cannot do two very important things: > 1. Use view state changes to hide/show layouts, using includeIn property on > containers and components. On Android, components that are not included for a > given state are destroyed yet they have state we want to maintain which is > why we don't change Views. > 2. We cannot know when the user navigates away from our application, for > example to press the Home key. We have certain cleanup we must do in our > complex connected app that streams FMS data, etc., and cannot keep sockets > open for hours or days. > On iOS, this is not a problem. Only Android has this bug and it's blocking us > from releasing our product on Android. iOS does not have this defect. -- 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-33371) On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events
[ https://issues.apache.org/jira/browse/FLEX-33371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565919#comment-13565919 ] Erik Thomas commented on FLEX-33371: Awesome, OmPrakash! This did the trick! I'm still getting DEACTIVATE when leaving the app as we needed, and we no longer get any of these bogus events fired for orientation changes. I searched a lot and never saw this one. Sorry to waste your time. Hope this could get fixed anyway though. Cheers, Erik Erik J. Thomas CEO | Principal Developer E. J. Thomas & Associates, LLC 266 Peakview Rd, Boulder, CO 80302 303-440-8384 (office) | 303-304-1466 (mobile) ejtho...@ejthomas.com CONFIDENTIALITY NOTICE: This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s). Any disclosure, copying, distribution, or other use of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. > On Android, changing orientation fires Event.DEACTIVATE and > FlexEvent.VIEW_DEACTIVATE events > > > Key: FLEX-33371 > URL: https://issues.apache.org/jira/browse/FLEX-33371 > Project: Apache Flex > Issue Type: Bug > Components: Mobile: MobileApplication >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: Samsung Galaxy Express and Galaxy S III Android Phones, > FlashBuilder 4.7 Premium on Windows 7, debugging through USB as well as > deployed release builds, iPhone and iPad, but the problem doesn't exist on > iOS devices, only Android >Reporter: Erik Thomas >Priority: Critical > Fix For: Adobe Flex SDK 4.6 (Release) > > Attachments: AndroidDeactivateOnOrientationChangeDefect.zip > > > Orientation changes on Android devices always fire the following events in > this order: > ViewNavigatorEvent.VIEW_DEACTIVATE > Event.DEACTIVATE > StageOrientationEvent.ORIENTATION_CHANGE > The first two events are a defect. They must not fire simply because the user > changed the orientation of the phone. > The result of this defect is that we cannot do two very important things: > 1. Use view state changes to hide/show layouts, using includeIn property on > containers and components. On Android, components that are not included for a > given state are destroyed yet they have state we want to maintain which is > why we don't change Views. > 2. We cannot know when the user navigates away from our application, for > example to press the Home key. We have certain cleanup we must do in our > complex connected app that streams FMS data, etc., and cannot keep sockets > open for hours or days. > On iOS, this is not a problem. Only Android has this bug and it's blocking us > from releasing our product on Android. iOS does not have this defect. -- 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-33371) On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events
[ https://issues.apache.org/jira/browse/FLEX-33371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565922#comment-13565922 ] Erik Thomas commented on FLEX-33371: Thanks Justin. OmPrakash found an obscure mention of using manifest element and it works perfectly. I still think this is a bug, probably in the AIR runtime, but this manifest entry solved my problems perfectly. Erik Erik J. Thomas CEO | Principal Developer E. J. Thomas & Associates, LLC 266 Peakview Rd, Boulder, CO 80302 303-440-8384 (office) | 303-304-1466 (mobile) ejtho...@ejthomas.com CONFIDENTIALITY NOTICE: This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s). Any disclosure, copying, distribution, or other use of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. > On Android, changing orientation fires Event.DEACTIVATE and > FlexEvent.VIEW_DEACTIVATE events > > > Key: FLEX-33371 > URL: https://issues.apache.org/jira/browse/FLEX-33371 > Project: Apache Flex > Issue Type: Bug > Components: Mobile: MobileApplication >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: Samsung Galaxy Express and Galaxy S III Android Phones, > FlashBuilder 4.7 Premium on Windows 7, debugging through USB as well as > deployed release builds, iPhone and iPad, but the problem doesn't exist on > iOS devices, only Android >Reporter: Erik Thomas >Priority: Critical > Fix For: Adobe Flex SDK 4.6 (Release) > > Attachments: AndroidDeactivateOnOrientationChangeDefect.zip > > > Orientation changes on Android devices always fire the following events in > this order: > ViewNavigatorEvent.VIEW_DEACTIVATE > Event.DEACTIVATE > StageOrientationEvent.ORIENTATION_CHANGE > The first two events are a defect. They must not fire simply because the user > changed the orientation of the phone. > The result of this defect is that we cannot do two very important things: > 1. Use view state changes to hide/show layouts, using includeIn property on > containers and components. On Android, components that are not included for a > given state are destroyed yet they have state we want to maintain which is > why we don't change Views. > 2. We cannot know when the user navigates away from our application, for > example to press the Home key. We have certain cleanup we must do in our > complex connected app that streams FMS data, etc., and cannot keep sockets > open for hours or days. > On iOS, this is not a problem. Only Android has this bug and it's blocking us > from releasing our product on Android. iOS does not have this defect. -- 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-33366) The candidate input method can not follow
[ https://issues.apache.org/jira/browse/FLEX-33366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565926#comment-13565926 ] Alex Harui commented on FLEX-33366: --- For me, there is no difference in IME appearance. I wish we could figure out why it is incorrect for you. Anyway, Spark needs to use a different IME logic because it is intended to support right-to-left text. I agree it isn't consistent, but it is supposed to look the same. What are you using TLF for? You can continue to use it for non-input text controls. But you may be able to swap out the controls that need the IME with the mobile.TextInputSkin as a workaround. > The candidate input method can not follow > - > > Key: FLEX-33366 > URL: https://issues.apache.org/jira/browse/FLEX-33366 > Project: Apache Flex > Issue Type: Bug > Components: Spark: TextArea, Spark: TextInput >Affects Versions: Apache Flex 4.8 (parity release) > Environment: windows,IE8 >Reporter: zy > > The spark:TextArea and TextInput Chinese candidate input method can not > follow. > But mx:TextArea and TextInput not this issue. > I guess you only test the English input method, Chinese input methods all > have this problem, it is affecting the user experience. > you can test this Chinese input method.all chinese use this. > http://dl_dir.qq.com/invc/qqpinyin/QQPinyin_Setup_1.1.1224.400.exe > I made a picture to illustrate the problem. > http://img.my.csdn.net/uploads/201301/24/1359028348_2400.jpg > If you are unclear, please let me know. I don't know english.I am very sorry. > Thank you! -- 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-33371) On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events
[ https://issues.apache.org/jira/browse/FLEX-33371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565968#comment-13565968 ] Erik Thomas commented on FLEX-33371: Hi OmPrakash: This is almost a perfect workaround. Unfortunately, listening for the NativeApplication.DEACTIVATE event to unload is not reliable. It seems to fire randomly and not related to orientation changes. I've only tried a couple times, but as I work through my app workflows, everything is working great on Android now, just like iOS, but something is triggering the DEACTIVATE event during a workflow and the app is unloading because I'm calling exit(). So I'm not out of the woods yet, but this is a huge improvement. Erik Erik J. Thomas CEO | Principal Developer E. J. Thomas & Associates, LLC 266 Peakview Rd, Boulder, CO 80302 303-440-8384 (office) | 303-304-1466 (mobile) ejtho...@ejthomas.com CONFIDENTIALITY NOTICE: This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s). Any disclosure, copying, distribution, or other use of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. > On Android, changing orientation fires Event.DEACTIVATE and > FlexEvent.VIEW_DEACTIVATE events > > > Key: FLEX-33371 > URL: https://issues.apache.org/jira/browse/FLEX-33371 > Project: Apache Flex > Issue Type: Bug > Components: Mobile: MobileApplication >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: Samsung Galaxy Express and Galaxy S III Android Phones, > FlashBuilder 4.7 Premium on Windows 7, debugging through USB as well as > deployed release builds, iPhone and iPad, but the problem doesn't exist on > iOS devices, only Android >Reporter: Erik Thomas >Priority: Critical > Fix For: Adobe Flex SDK 4.6 (Release) > > Attachments: AndroidDeactivateOnOrientationChangeDefect.zip > > > Orientation changes on Android devices always fire the following events in > this order: > ViewNavigatorEvent.VIEW_DEACTIVATE > Event.DEACTIVATE > StageOrientationEvent.ORIENTATION_CHANGE > The first two events are a defect. They must not fire simply because the user > changed the orientation of the phone. > The result of this defect is that we cannot do two very important things: > 1. Use view state changes to hide/show layouts, using includeIn property on > containers and components. On Android, components that are not included for a > given state are destroyed yet they have state we want to maintain which is > why we don't change Views. > 2. We cannot know when the user navigates away from our application, for > example to press the Home key. We have certain cleanup we must do in our > complex connected app that streams FMS data, etc., and cannot keep sockets > open for hours or days. > On iOS, this is not a problem. Only Android has this bug and it's blocking us > from releasing our product on Android. iOS does not have this defect. -- 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-33372) Windows 8 on-screen touch keyboard not displaying
Stepan Hilbert created FLEX-33372: - Summary: Windows 8 on-screen touch keyboard not displaying Key: FLEX-33372 URL: https://issues.apache.org/jira/browse/FLEX-33372 Project: Apache Flex Issue Type: Bug Components: Spark: TextArea, Spark: TextInput Affects Versions: Adobe Flex SDK 4.6 (Release) Environment: Windows 8 Metro Internet Explorer (IE) 10.0.1 Flash Player 11,3,378,5 Reporter: Stepan Hilbert On-screen touch keyboard is not being displayed for spark text input components. It should get displayed just as it gets displayed for TextField based components. Additionally, it would be desirable to control the keyboard using: - needsSoftKeyboard property - requestSoftKeyboard() function These currently have no effect. Steps to reproduce: 1. Create a Flex application that features s:TextInput and mx:TextInput 2. Open this application in the Metro Internet Explorer on a touch-enabled Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx) 3. Tap the mx:TextInput - on-screen keyboard shows 4. Tap the s:TextInput - on-screen keyboard doesn't show Note: This bug has been discussed on the web (i.e. here: http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html) but no resolution has been reached, so that is why I'm logging this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying
[ https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Hilbert updated FLEX-33372: -- Component/s: Spark: RichEditableText > Windows 8 on-screen touch keyboard not displaying > - > > Key: FLEX-33372 > URL: https://issues.apache.org/jira/browse/FLEX-33372 > Project: Apache Flex > Issue Type: Bug > Components: Spark: RichEditableText, Spark: TextArea, Spark: > TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: Windows 8 Metro > Internet Explorer (IE) 10.0.1 > Flash Player 11,3,378,5 >Reporter: Stepan Hilbert > > On-screen touch keyboard is not being displayed for spark text input > components. It should get displayed just as it gets displayed for TextField > based components. > Additionally, it would be desirable to control the keyboard using: > - needsSoftKeyboard property > - requestSoftKeyboard() function > These currently have no effect. > Steps to reproduce: > 1. Create a Flex application that features s:TextInput and mx:TextInput > 2. Open this application in the Metro Internet Explorer on a touch-enabled > Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see > http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx) > 3. Tap the mx:TextInput - on-screen keyboard shows > 4. Tap the s:TextInput - on-screen keyboard doesn't show > Note: > This bug has been discussed on the web > (i.e. here: > http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html) > but no resolution has been reached, so that is why I'm logging this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying
[ https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Hilbert updated FLEX-33372: -- Affects Version/s: Apache Flex 4.9.0 > Windows 8 on-screen touch keyboard not displaying > - > > Key: FLEX-33372 > URL: https://issues.apache.org/jira/browse/FLEX-33372 > Project: Apache Flex > Issue Type: Bug > Components: Spark: RichEditableText, Spark: TextArea, Spark: > TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: Windows 8 Metro > Internet Explorer (IE) 10.0.1 > Flash Player 11,3,378,5 >Reporter: Stepan Hilbert > > On-screen touch keyboard is not being displayed for spark text input > components. It should get displayed just as it gets displayed for TextField > based components. > Additionally, it would be desirable to control the keyboard using: > - needsSoftKeyboard property > - requestSoftKeyboard() function > These currently have no effect. > Steps to reproduce: > 1. Create a Flex application that features s:TextInput and mx:TextInput > 2. Open this application in the Metro Internet Explorer on a touch-enabled > Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see > http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx) > 3. Tap the mx:TextInput - on-screen keyboard shows > 4. Tap the s:TextInput - on-screen keyboard doesn't show > Note: > This bug has been discussed on the web > (i.e. here: > http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html) > but no resolution has been reached, so that is why I'm logging this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying
[ https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Hilbert updated FLEX-33372: -- Description: On-screen touch keyboard is not being displayed for spark RichEditableText based text input components. It does get displayed when displayAsPassword property is set to true. It does get displayed for TextField based components. Additionally, it would be desirable to control the keyboard using: - needsSoftKeyboard property - requestSoftKeyboard() function These currently have no effect. Steps to reproduce: 1. Create a Flex application that features s:TextInput, s:TextInput with displayAsPassword="true" and mx:TextInput 2. Open this application in the Metro Internet Explorer on a touch-enabled Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx) 3. Tap the mx:TextInput - on-screen keyboard shows 4. Tap the s:TextInput with displayAsPassword="true" - on-screen keyboard shows 5. Tap the s:TextInput - on-screen keyboard doesn't show Note: This bug has been discussed on the web (i.e. here: http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html) but no resolution has been reached, so that is why I'm logging this issue. was: On-screen touch keyboard is not being displayed for spark text input components. It should get displayed just as it gets displayed for TextField based components. Additionally, it would be desirable to control the keyboard using: - needsSoftKeyboard property - requestSoftKeyboard() function These currently have no effect. Steps to reproduce: 1. Create a Flex application that features s:TextInput and mx:TextInput 2. Open this application in the Metro Internet Explorer on a touch-enabled Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx) 3. Tap the mx:TextInput - on-screen keyboard shows 4. Tap the s:TextInput - on-screen keyboard doesn't show Note: This bug has been discussed on the web (i.e. here: http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html) but no resolution has been reached, so that is why I'm logging this issue. > Windows 8 on-screen touch keyboard not displaying > - > > Key: FLEX-33372 > URL: https://issues.apache.org/jira/browse/FLEX-33372 > Project: Apache Flex > Issue Type: Bug > Components: Spark: RichEditableText, Spark: TextArea, Spark: > TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: Windows 8 Metro > Internet Explorer (IE) 10.0.1 > Flash Player 11,3,378,5 >Reporter: Stepan Hilbert > > On-screen touch keyboard is not being displayed for spark RichEditableText > based text input components. It does get displayed when displayAsPassword > property is set to true. It does get displayed for TextField based components. > Additionally, it would be desirable to control the keyboard using: > - needsSoftKeyboard property > - requestSoftKeyboard() function > These currently have no effect. > Steps to reproduce: > 1. Create a Flex application that features s:TextInput, s:TextInput with > displayAsPassword="true" and mx:TextInput > > > > 2. Open this application in the Metro Internet Explorer on a touch-enabled > Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see > http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx) > 3. Tap the mx:TextInput - on-screen keyboard shows > 4. Tap the s:TextInput with displayAsPassword="true" - on-screen keyboard > shows > 5. Tap the s:TextInput - on-screen keyboard doesn't show > Note: > This bug has been discussed on the web > (i.e. here: > http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html) > but no resolution has been reached, so that is why I'm logging this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying
[ https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566143#comment-13566143 ] Alex Harui commented on FLEX-33372: --- Before I go digging, has anyone tried 11.5 or 11.6 beta? > Windows 8 on-screen touch keyboard not displaying > - > > Key: FLEX-33372 > URL: https://issues.apache.org/jira/browse/FLEX-33372 > Project: Apache Flex > Issue Type: Bug > Components: Spark: RichEditableText, Spark: TextArea, Spark: > TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: Windows 8 Metro > Internet Explorer (IE) 10.0.1 > Flash Player 11,3,378,5 >Reporter: Stepan Hilbert > > On-screen touch keyboard is not being displayed for spark RichEditableText > based text input components. It does get displayed when displayAsPassword > property is set to true. It does get displayed for TextField based components. > Additionally, it would be desirable to control the keyboard using: > - needsSoftKeyboard property > - requestSoftKeyboard() function > These currently have no effect. > Steps to reproduce: > 1. Create a Flex application that features s:TextInput, s:TextInput with > displayAsPassword="true" and mx:TextInput > > > > 2. Open this application in the Metro Internet Explorer on a touch-enabled > Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see > http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx) > 3. Tap the mx:TextInput - on-screen keyboard shows > 4. Tap the s:TextInput with displayAsPassword="true" - on-screen keyboard > shows > 5. Tap the s:TextInput - on-screen keyboard doesn't show > Note: > This bug has been discussed on the web > (i.e. here: > http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html) > but no resolution has been reached, so that is why I'm logging this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying
[ https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566166#comment-13566166 ] Stepan Hilbert commented on FLEX-33372: --- Hi Alex, Thanks for looking into this. I cannot try 11.5 or 11.6 beta as they refuse to install on Windows 8 (I think they're not compatible). I have tried 11,3,378,5 debugger - same behavior as the non-debug version. > Windows 8 on-screen touch keyboard not displaying > - > > Key: FLEX-33372 > URL: https://issues.apache.org/jira/browse/FLEX-33372 > Project: Apache Flex > Issue Type: Bug > Components: Spark: RichEditableText, Spark: TextArea, Spark: > TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: Windows 8 Metro > Internet Explorer (IE) 10.0.1 > Flash Player 11,3,378,5 >Reporter: Stepan Hilbert > > On-screen touch keyboard is not being displayed for spark RichEditableText > based text input components. It does get displayed when displayAsPassword > property is set to true. It does get displayed for TextField based components. > Additionally, it would be desirable to control the keyboard using: > - needsSoftKeyboard property > - requestSoftKeyboard() function > These currently have no effect. > Steps to reproduce: > 1. Create a Flex application that features s:TextInput, s:TextInput with > displayAsPassword="true" and mx:TextInput > > > > 2. Open this application in the Metro Internet Explorer on a touch-enabled > Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see > http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx) > 3. Tap the mx:TextInput - on-screen keyboard shows > 4. Tap the s:TextInput with displayAsPassword="true" - on-screen keyboard > shows > 5. Tap the s:TextInput - on-screen keyboard doesn't show > Note: > This bug has been discussed on the web > (i.e. here: > http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html) > but no resolution has been reached, so that is why I'm logging this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying
[ https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566945#comment-13566945 ] Alex Harui commented on FLEX-33372: --- My sources say this is a known issue all the way through 11.6. Please file a bug at bugbase.adobe.com against the Flash Player. > Windows 8 on-screen touch keyboard not displaying > - > > Key: FLEX-33372 > URL: https://issues.apache.org/jira/browse/FLEX-33372 > Project: Apache Flex > Issue Type: Bug > Components: Spark: RichEditableText, Spark: TextArea, Spark: > TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: Windows 8 Metro > Internet Explorer (IE) 10.0.1 > Flash Player 11,3,378,5 >Reporter: Stepan Hilbert > > On-screen touch keyboard is not being displayed for spark RichEditableText > based text input components. It does get displayed when displayAsPassword > property is set to true. It does get displayed for TextField based components. > Additionally, it would be desirable to control the keyboard using: > - needsSoftKeyboard property > - requestSoftKeyboard() function > These currently have no effect. > Steps to reproduce: > 1. Create a Flex application that features s:TextInput, s:TextInput with > displayAsPassword="true" and mx:TextInput > > > > 2. Open this application in the Metro Internet Explorer on a touch-enabled > Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see > http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx) > 3. Tap the mx:TextInput - on-screen keyboard shows > 4. Tap the s:TextInput with displayAsPassword="true" - on-screen keyboard > shows > 5. Tap the s:TextInput - on-screen keyboard doesn't show > Note: > This bug has been discussed on the web > (i.e. here: > http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html) > but no resolution has been reached, so that is why I'm logging this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying
[ https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567077#comment-13567077 ] Stepan Hilbert commented on FLEX-33372: --- Thanks, the bug has been re-submitted as advised: https://bugbase.adobe.com/index.cfm?event=bug&id=3493295 I'm really curious if this turns out to be a Player issue or SDK issue. Everything points to the Player but then why displayAsPassword="true" works? > Windows 8 on-screen touch keyboard not displaying > - > > Key: FLEX-33372 > URL: https://issues.apache.org/jira/browse/FLEX-33372 > Project: Apache Flex > Issue Type: Bug > Components: Spark: RichEditableText, Spark: TextArea, Spark: > TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: Windows 8 Metro > Internet Explorer (IE) 10.0.1 > Flash Player 11,3,378,5 >Reporter: Stepan Hilbert > > On-screen touch keyboard is not being displayed for spark RichEditableText > based text input components. It does get displayed when displayAsPassword > property is set to true. It does get displayed for TextField based components. > Additionally, it would be desirable to control the keyboard using: > - needsSoftKeyboard property > - requestSoftKeyboard() function > These currently have no effect. > Steps to reproduce: > 1. Create a Flex application that features s:TextInput, s:TextInput with > displayAsPassword="true" and mx:TextInput > > > > 2. Open this application in the Metro Internet Explorer on a touch-enabled > Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see > http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx) > 3. Tap the mx:TextInput - on-screen keyboard shows > 4. Tap the s:TextInput with displayAsPassword="true" - on-screen keyboard > shows > 5. Tap the s:TextInput - on-screen keyboard doesn't show > Note: > This bug has been discussed on the web > (i.e. here: > http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html) > but no resolution has been reached, so that is why I'm logging this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying
[ https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567129#comment-13567129 ] Alex Harui commented on FLEX-33372: --- My source thinks it is a player bug, otherwise they would have passed the issue on to Flex. If you have time, you can help out by creating a non-Flex version of the test case. Take a TextField and a Sprite. Try giving them focus and see if the keyboard shows up. If it works for Sprite, there might be other code you need to borrow from RichEditableText and TLF until it fails. When RET has displayAsPassword=true it looks like it causes TLF to think someone pasted in the '" which might take TLF down some code path that allows the keyboard to show up. I don't have a device to test it on so I can't help much at this time. It occurs to me that a possible workaround might be to always force that paste operation after each keystroke. > Windows 8 on-screen touch keyboard not displaying > - > > Key: FLEX-33372 > URL: https://issues.apache.org/jira/browse/FLEX-33372 > Project: Apache Flex > Issue Type: Bug > Components: Spark: RichEditableText, Spark: TextArea, Spark: > TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: Windows 8 Metro > Internet Explorer (IE) 10.0.1 > Flash Player 11,3,378,5 >Reporter: Stepan Hilbert > > On-screen touch keyboard is not being displayed for spark RichEditableText > based text input components. It does get displayed when displayAsPassword > property is set to true. It does get displayed for TextField based components. > Additionally, it would be desirable to control the keyboard using: > - needsSoftKeyboard property > - requestSoftKeyboard() function > These currently have no effect. > Steps to reproduce: > 1. Create a Flex application that features s:TextInput, s:TextInput with > displayAsPassword="true" and mx:TextInput > > > > 2. Open this application in the Metro Internet Explorer on a touch-enabled > Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see > http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx) > 3. Tap the mx:TextInput - on-screen keyboard shows > 4. Tap the s:TextInput with displayAsPassword="true" - on-screen keyboard > shows > 5. Tap the s:TextInput - on-screen keyboard doesn't show > Note: > This bug has been discussed on the web > (i.e. here: > http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html) > but no resolution has been reached, so that is why I'm logging this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying
[ https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567252#comment-13567252 ] Stepan Hilbert commented on FLEX-33372: --- I've added a Flash-only test case to the Flash Player bug. The issue can be replicated using TLFTextField - so it seems to be a Player issue. Paste won't be a workaround as there's nothing to paste (users have no keyboard to write on). Toggling displayAsPassword doesn't seem to be useful for a workaround either. > Windows 8 on-screen touch keyboard not displaying > - > > Key: FLEX-33372 > URL: https://issues.apache.org/jira/browse/FLEX-33372 > Project: Apache Flex > Issue Type: Bug > Components: Spark: RichEditableText, Spark: TextArea, Spark: > TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: Windows 8 Metro > Internet Explorer (IE) 10.0.1 > Flash Player 11,3,378,5 >Reporter: Stepan Hilbert > > On-screen touch keyboard is not being displayed for spark RichEditableText > based text input components. It does get displayed when displayAsPassword > property is set to true. It does get displayed for TextField based components. > Additionally, it would be desirable to control the keyboard using: > - needsSoftKeyboard property > - requestSoftKeyboard() function > These currently have no effect. > Steps to reproduce: > 1. Create a Flex application that features s:TextInput, s:TextInput with > displayAsPassword="true" and mx:TextInput > > > > 2. Open this application in the Metro Internet Explorer on a touch-enabled > Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see > http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx) > 3. Tap the mx:TextInput - on-screen keyboard shows > 4. Tap the s:TextInput with displayAsPassword="true" - on-screen keyboard > shows > 5. Tap the s:TextInput - on-screen keyboard doesn't show > Note: > This bug has been discussed on the web > (i.e. here: > http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html) > but no resolution has been reached, so that is why I'm logging this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (FLEX-33361) [WEBSITE] Enable link tracking analysis for flex.apache.org
[ https://issues.apache.org/jira/browse/FLEX-33361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Kwiatkowski resolved FLEX-33361. - Resolution: Implemented Added tracking code for UA-37926454-1 to website and added privacy policy to footer of each tracked page. > [WEBSITE] Enable link tracking analysis for flex.apache.org > --- > > Key: FLEX-33361 > URL: https://issues.apache.org/jira/browse/FLEX-33361 > Project: Apache Flex > Issue Type: Improvement >Reporter: OmPrakash Muppirala >Assignee: Nick Kwiatkowski > > Discussion here: http://markmail.org/message/dpmcb5hi5y7olwu2 > One of the easiest ways to enable tracking statistics on our website would be > to use Google Analytics. If the Flex PMC agrees, this would be the steps. > Things to do: > 1. Enable GA on flex.apache.org > 2. Make stats available to Flex PMC > 3. Share GA credentials to Flex PMC > 4. Add a privacy-policy page to flex.apache.org a la > http://jackrabbit.apache.org/privacy-policy.html > 5. Include a link to the opt out plug in: > https://tools.google.com/dlpage/gaoptout -- 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-33372) Windows 8 on-screen touch keyboard not displaying
[ https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567370#comment-13567370 ] Alex Harui commented on FLEX-33372: --- I'm just thinking that a workaround would consist of setting focus to a TextInput with displayAsPassword that is actually hidden behind a TextInput without displayAsPassword. If that allows the keyboard to show up, then you can reflect what is typed into the hidden TextInput into the one on top. Another experiment, if you have time to play around, is to make a copy of RichEditableText and fool around with the code paths that are affected by displayAsPassword until you find out which code path it is that allows the keyboard to come up. That might provide a clue to other workarounds. > Windows 8 on-screen touch keyboard not displaying > - > > Key: FLEX-33372 > URL: https://issues.apache.org/jira/browse/FLEX-33372 > Project: Apache Flex > Issue Type: Bug > Components: Spark: RichEditableText, Spark: TextArea, Spark: > TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: Windows 8 Metro > Internet Explorer (IE) 10.0.1 > Flash Player 11,3,378,5 >Reporter: Stepan Hilbert > > On-screen touch keyboard is not being displayed for spark RichEditableText > based text input components. It does get displayed when displayAsPassword > property is set to true. It does get displayed for TextField based components. > Additionally, it would be desirable to control the keyboard using: > - needsSoftKeyboard property > - requestSoftKeyboard() function > These currently have no effect. > Steps to reproduce: > 1. Create a Flex application that features s:TextInput, s:TextInput with > displayAsPassword="true" and mx:TextInput > > > > 2. Open this application in the Metro Internet Explorer on a touch-enabled > Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see > http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx) > 3. Tap the mx:TextInput - on-screen keyboard shows > 4. Tap the s:TextInput with displayAsPassword="true" - on-screen keyboard > shows > 5. Tap the s:TextInput - on-screen keyboard doesn't show > Note: > This bug has been discussed on the web > (i.e. here: > http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html) > but no resolution has been reached, so that is why I'm logging this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying
[ https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567383#comment-13567383 ] Stepan Hilbert commented on FLEX-33372: --- > ...setting focus to a TextInput with displayAsPassword that is actually > hidden behind... That might work, not exactly pretty though :-). But yes, either that or we might end up rebuilding what we have on top of mx:TextInput > ...make a copy of RichEditableText I tried making a copy of RichEditableText (& RichEditableTextManager). I had to do only very minor changes to make those compile- so the copied component was near identical with RichEditableText. Somehow though, even if the copied component had displayAsPassword="true" it wouldn't trigger the keyboard. > Windows 8 on-screen touch keyboard not displaying > - > > Key: FLEX-33372 > URL: https://issues.apache.org/jira/browse/FLEX-33372 > Project: Apache Flex > Issue Type: Bug > Components: Spark: RichEditableText, Spark: TextArea, Spark: > TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: Windows 8 Metro > Internet Explorer (IE) 10.0.1 > Flash Player 11,3,378,5 >Reporter: Stepan Hilbert > > On-screen touch keyboard is not being displayed for spark RichEditableText > based text input components. It does get displayed when displayAsPassword > property is set to true. It does get displayed for TextField based components. > Additionally, it would be desirable to control the keyboard using: > - needsSoftKeyboard property > - requestSoftKeyboard() function > These currently have no effect. > Steps to reproduce: > 1. Create a Flex application that features s:TextInput, s:TextInput with > displayAsPassword="true" and mx:TextInput > > > > 2. Open this application in the Metro Internet Explorer on a touch-enabled > Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see > http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx) > 3. Tap the mx:TextInput - on-screen keyboard shows > 4. Tap the s:TextInput with displayAsPassword="true" - on-screen keyboard > shows > 5. Tap the s:TextInput - on-screen keyboard doesn't show > Note: > This bug has been discussed on the web > (i.e. here: > http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html) > but no resolution has been reached, so that is why I'm logging this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying
[ https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567388#comment-13567388 ] Alex Harui commented on FLEX-33372: --- One more question: Are you creating a Flex Mobile application? Mobile apps do not use RichEditableText and use TextField like mx:TextInput. In this issue: https://issues.apache.org/jira/browse/FLEX-33366 I describe how to swap in a mobile TextInput skin for a non-mobile app and get the Spark TextInput to use TextField. Of course, you have to give up right-to-left text support if you use TextField instead of TLF. > Windows 8 on-screen touch keyboard not displaying > - > > Key: FLEX-33372 > URL: https://issues.apache.org/jira/browse/FLEX-33372 > Project: Apache Flex > Issue Type: Bug > Components: Spark: RichEditableText, Spark: TextArea, Spark: > TextInput >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: Windows 8 Metro > Internet Explorer (IE) 10.0.1 > Flash Player 11,3,378,5 >Reporter: Stepan Hilbert > > On-screen touch keyboard is not being displayed for spark RichEditableText > based text input components. It does get displayed when displayAsPassword > property is set to true. It does get displayed for TextField based components. > Additionally, it would be desirable to control the keyboard using: > - needsSoftKeyboard property > - requestSoftKeyboard() function > These currently have no effect. > Steps to reproduce: > 1. Create a Flex application that features s:TextInput, s:TextInput with > displayAsPassword="true" and mx:TextInput > > > > 2. Open this application in the Metro Internet Explorer on a touch-enabled > Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see > http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx) > 3. Tap the mx:TextInput - on-screen keyboard shows > 4. Tap the s:TextInput with displayAsPassword="true" - on-screen keyboard > shows > 5. Tap the s:TextInput - on-screen keyboard doesn't show > Note: > This bug has been discussed on the web > (i.e. here: > http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html) > but no resolution has been reached, so that is why I'm logging this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FLEX-33374) spark VideoDisplay and VideoPlayer fails to stream video on mobile devices
Erik Thomas created FLEX-33374: -- Summary: spark VideoDisplay and VideoPlayer fails to stream video on mobile devices Key: FLEX-33374 URL: https://issues.apache.org/jira/browse/FLEX-33374 Project: Apache Flex Issue Type: Bug Components: Spark: VideoPlayer Affects Versions: Adobe Flex SDK 4.6 (Release) Environment: FlashBuilder 4.7 on Windows 7, iPad 3, iPhone 4, remote FMS 4.5 server, FLV Video source in 112K bitrate. Reporter: Erik Thomas The spark VideoDisplay will not stream video from FMS 4.5, instead it appears to do progressive download instead, and it buffers the file for about one minute before it begins to play. However, the same code running in FlashPlayer on web, or in an AIR mobile simulator, the video properly streams and displays within seconds of playing. I understand VideoDisplay is not "optimized" for mobile, but that should not cause this behavior. I am in the process of debugging the spark codebase to find the root cause, but so far have been unsuccessful. So I attached a project that displays this behavior. Just unzip the file to a directory, start FB and point the workspace to the directory, open the project, build and run it first in an AIR simulator for an iOS mobile device, you'll see video instantly. Then deploy it in debug or release to an actual device. When you launch the project, you have to wait approximately a minute before the video will start playing. I'm assuming it's failing over to progressive download from streaming in some way, but I really have no idea what is causing the issue. I really don't care if the performance of the VideoDisplay isn't optimized for mobile, and a delayed start of several seconds would be fine, but one minute? If I find a root cause I will update this defect record with my findings as this is a blocker for us so that's my focus. -- 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-33374) spark VideoDisplay and VideoPlayer fails to stream video on mobile devices
[ https://issues.apache.org/jira/browse/FLEX-33374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Thomas updated FLEX-33374: --- Attachment: VideoPlayback.zip Just unzip to a new directory, start FB 4.7 and create a new workspace that points to the directory. Build and run the project in an AIR simulator first. Video streams from my FMS 4.5 server immediately. Do the test again on an actual device, either debug or release, and you will have to wait for about a minute before the video begins to play. There is no possible way that bandwidth is the issue here. I'm running the device on my same network with the same connectivity and bandwidth as my dev computer. My devices are using WiFi so there's no way cellular bandwidth is playing any role in this issue and even if bandwidth was a contributor it would only delay a start by seconds, not a minute. I'm just hopeful someone is really familiar with this functionality and will know what's wrong for an easy fix. I'm debugging into the sources now to try to find a root cause, but I'm unfamiliar with the spark internals, especially of MediaPlayer and MediaElement, etc. > spark VideoDisplay and VideoPlayer fails to stream video on mobile devices > -- > > Key: FLEX-33374 > URL: https://issues.apache.org/jira/browse/FLEX-33374 > Project: Apache Flex > Issue Type: Bug > Components: Spark: VideoPlayer >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: FlashBuilder 4.7 on Windows 7, iPad 3, iPhone 4, remote > FMS 4.5 server, FLV Video source in 112K bitrate. >Reporter: Erik Thomas > Attachments: VideoPlayback.zip > > > The spark VideoDisplay will not stream video from FMS 4.5, instead it appears > to do progressive download instead, and it buffers the file for about one > minute before it begins to play. > However, the same code running in FlashPlayer on web, or in an AIR mobile > simulator, the video properly streams and displays within seconds of playing. > I understand VideoDisplay is not "optimized" for mobile, but that should not > cause this behavior. I am in the process of debugging the spark codebase to > find the root cause, but so far have been unsuccessful. > So I attached a project that displays this behavior. Just unzip the file to a > directory, start FB and point the workspace to the directory, open the > project, build and run it first in an AIR simulator for an iOS mobile device, > you'll see video instantly. Then deploy it in debug or release to an actual > device. When you launch the project, you have to wait approximately a minute > before the video will start playing. > I'm assuming it's failing over to progressive download from streaming in some > way, but I really have no idea what is causing the issue. > I really don't care if the performance of the VideoDisplay isn't optimized > for mobile, and a delayed start of several seconds would be fine, but one > minute? > If I find a root cause I will update this defect record with my findings as > this is a blocker for us so that's my focus. -- 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-33374) spark VideoDisplay and VideoPlayer fails to stream video on mobile devices
[ https://issues.apache.org/jira/browse/FLEX-33374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Thomas updated FLEX-33374: --- Attachment: VideoDisplay.jpg This is a screen shot of an AIR simulator for the iPhone. The video streams immediately. If you run the same app on the device itself, with WiFi connectivity and high bandwidth connection, it still takes a minute before the video begins playing. > spark VideoDisplay and VideoPlayer fails to stream video on mobile devices > -- > > Key: FLEX-33374 > URL: https://issues.apache.org/jira/browse/FLEX-33374 > Project: Apache Flex > Issue Type: Bug > Components: Spark: VideoPlayer >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: FlashBuilder 4.7 on Windows 7, iPad 3, iPhone 4, remote > FMS 4.5 server, FLV Video source in 112K bitrate. >Reporter: Erik Thomas > Attachments: VideoDisplay.jpg, VideoPlayback.zip > > > The spark VideoDisplay will not stream video from FMS 4.5, instead it appears > to do progressive download instead, and it buffers the file for about one > minute before it begins to play. > However, the same code running in FlashPlayer on web, or in an AIR mobile > simulator, the video properly streams and displays within seconds of playing. > I understand VideoDisplay is not "optimized" for mobile, but that should not > cause this behavior. I am in the process of debugging the spark codebase to > find the root cause, but so far have been unsuccessful. > So I attached a project that displays this behavior. Just unzip the file to a > directory, start FB and point the workspace to the directory, open the > project, build and run it first in an AIR simulator for an iOS mobile device, > you'll see video instantly. Then deploy it in debug or release to an actual > device. When you launch the project, you have to wait approximately a minute > before the video will start playing. > I'm assuming it's failing over to progressive download from streaming in some > way, but I really have no idea what is causing the issue. > I really don't care if the performance of the VideoDisplay isn't optimized > for mobile, and a delayed start of several seconds would be fine, but one > minute? > If I find a root cause I will update this defect record with my findings as > this is a blocker for us so that's my focus. -- 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-33374) spark VideoDisplay and VideoPlayer fails to stream video on mobile devices
[ https://issues.apache.org/jira/browse/FLEX-33374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567731#comment-13567731 ] Erik Thomas commented on FLEX-33374: BTW, I thought of tryng to use StageVideo but the problem there is, we display the video in a popup container. StageVideo plays underneath the display tree and cannot be displayed within a popup Flex container. I'm also trying to workaround this with Netconnection, Netstream and Video classes instead but it would be really cool to have VideoDisplay stream on mobile. > spark VideoDisplay and VideoPlayer fails to stream video on mobile devices > -- > > Key: FLEX-33374 > URL: https://issues.apache.org/jira/browse/FLEX-33374 > Project: Apache Flex > Issue Type: Bug > Components: Spark: VideoPlayer >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: FlashBuilder 4.7 on Windows 7, iPad 3, iPhone 4, remote > FMS 4.5 server, FLV Video source in 112K bitrate. >Reporter: Erik Thomas > Attachments: VideoDisplay.jpg, VideoPlayback.zip > > > The spark VideoDisplay will not stream video from FMS 4.5, instead it appears > to do progressive download instead, and it buffers the file for about one > minute before it begins to play. > However, the same code running in FlashPlayer on web, or in an AIR mobile > simulator, the video properly streams and displays within seconds of playing. > I understand VideoDisplay is not "optimized" for mobile, but that should not > cause this behavior. I am in the process of debugging the spark codebase to > find the root cause, but so far have been unsuccessful. > So I attached a project that displays this behavior. Just unzip the file to a > directory, start FB and point the workspace to the directory, open the > project, build and run it first in an AIR simulator for an iOS mobile device, > you'll see video instantly. Then deploy it in debug or release to an actual > device. When you launch the project, you have to wait approximately a minute > before the video will start playing. > I'm assuming it's failing over to progressive download from streaming in some > way, but I really have no idea what is causing the issue. > I really don't care if the performance of the VideoDisplay isn't optimized > for mobile, and a delayed start of several seconds would be fine, but one > minute? > If I find a root cause I will update this defect record with my findings as > this is a blocker for us so that's my focus. -- 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-33374) spark VideoDisplay and VideoPlayer fails to stream video on mobile devices
[ https://issues.apache.org/jira/browse/FLEX-33374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567740#comment-13567740 ] Erik Thomas commented on FLEX-33374: And yes, I understand the spark VideoDisplay leverages OSMF, including MediaPlayer and MediaElement and the defect may belong to OSMF. I will download and debug their sources and see if I can find something. > spark VideoDisplay and VideoPlayer fails to stream video on mobile devices > -- > > Key: FLEX-33374 > URL: https://issues.apache.org/jira/browse/FLEX-33374 > Project: Apache Flex > Issue Type: Bug > Components: Spark: VideoPlayer >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: FlashBuilder 4.7 on Windows 7, iPad 3, iPhone 4, remote > FMS 4.5 server, FLV Video source in 112K bitrate. >Reporter: Erik Thomas > Attachments: VideoDisplay.jpg, VideoPlayback.zip > > > The spark VideoDisplay will not stream video from FMS 4.5, instead it appears > to do progressive download instead, and it buffers the file for about one > minute before it begins to play. > However, the same code running in FlashPlayer on web, or in an AIR mobile > simulator, the video properly streams and displays within seconds of playing. > I understand VideoDisplay is not "optimized" for mobile, but that should not > cause this behavior. I am in the process of debugging the spark codebase to > find the root cause, but so far have been unsuccessful. > So I attached a project that displays this behavior. Just unzip the file to a > directory, start FB and point the workspace to the directory, open the > project, build and run it first in an AIR simulator for an iOS mobile device, > you'll see video instantly. Then deploy it in debug or release to an actual > device. When you launch the project, you have to wait approximately a minute > before the video will start playing. > I'm assuming it's failing over to progressive download from streaming in some > way, but I really have no idea what is causing the issue. > I really don't care if the performance of the VideoDisplay isn't optimized > for mobile, and a delayed start of several seconds would be fine, but one > minute? > If I find a root cause I will update this defect record with my findings as > this is a blocker for us so that's my focus. -- 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-33375) Button clicked in a Component (Group) causes the component to stay in memory
Christian Kiefer created FLEX-33375:
---
Summary: Button clicked in a Component (Group) causes the
component to stay in memory
Key: FLEX-33375
URL: https://issues.apache.org/jira/browse/FLEX-33375
Project: Apache Flex
Issue Type: Bug
Components: Spark: Button
Environment: air 3.5 mobile
Reporter: Christian Kiefer
Priority: Critical
Code:
protected function handleLoginClicked(event:MouseEvent):void
{
dispatchEvent(new LoginEvent(LoginEvent.LOGIN, "XYZ", "123"));
}
]]>
Result:
After the login event is dispatches the view/current component (group) gets
disposed and removed...
Problem:
clicking the label and the view isn't in memory anymore.
clicking the button causes the view to stay in memory.
--
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-33375) Button clicked in a Component (Group) causes the component to stay in memory
[
https://issues.apache.org/jira/browse/FLEX-33375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Kiefer updated FLEX-33375:
Description:
Code:
protected function handleLoginClicked(event:MouseEvent):void
{
dispatchEvent(new LoginEvent(LoginEvent.LOGIN, "XYZ", "123"));
}
]]>
Result:
After the login event is dispatched the view/current component (group) gets
disposed and removed...
Problem:
clicking the label and the view isn't in memory anymore.
clicking the button causes the view to stay in memory.
was:
Code:
protected function handleLoginClicked(event:MouseEvent):void
{
dispatchEvent(new LoginEvent(LoginEvent.LOGIN, "XYZ", "123"));
}
]]>
Result:
After the login event is dispatches the view/current component (group) gets
disposed and removed...
Problem:
clicking the label and the view isn't in memory anymore.
clicking the button causes the view to stay in memory.
> Button clicked in a Component (Group) causes the component to stay in memory
>
>
> Key: FLEX-33375
> URL: https://issues.apache.org/jira/browse/FLEX-33375
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark: Button
> Environment: air 3.5 mobile
>Reporter: Christian Kiefer
>Priority: Critical
>
> Code:
> protected function handleLoginClicked(event:MouseEvent):void
> {
> dispatchEvent(new LoginEvent(LoginEvent.LOGIN, "XYZ", "123"));
> }
>
> ]]>
>
> enabled="true"
> label="test"
> height="60"
> click="handleLoginClicked(event)"/>
>
>
> Result:
> After the login event is dispatched the view/current component (group) gets
> disposed and removed...
> Problem:
> clicking the label and the view isn't in memory anymore.
> clicking the button causes the view to stay in memory.
--
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-33375) Button clicked in a Component (Group) causes the component to stay in memory
[
https://issues.apache.org/jira/browse/FLEX-33375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Harui resolved FLEX-33375.
---
Resolution: Not A Problem
We would need a complete test case to be sure, but the most likely cause based
on the snippet you included is that the button still has keyboard focus. The
FocusManager does not try to figure out where else to put focus when the
focused item is removed from the display list. It is highly recommended that
you call setFocus on some useful component for your users that may not be able
to use a mouse, and doing so should allow the view to be garbage collected.
Otherwise, please re-open with a small and complete test case.
> Button clicked in a Component (Group) causes the component to stay in memory
>
>
> Key: FLEX-33375
> URL: https://issues.apache.org/jira/browse/FLEX-33375
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark: Button
> Environment: air 3.5 mobile
>Reporter: Christian Kiefer
>Priority: Critical
>
> Code:
> protected function handleLoginClicked(event:MouseEvent):void
> {
> dispatchEvent(new LoginEvent(LoginEvent.LOGIN, "XYZ", "123"));
> }
>
> ]]>
>
> enabled="true"
> label="test"
> height="60"
> click="handleLoginClicked(event)"/>
>
>
> Result:
> After the login event is dispatched the view/current component (group) gets
> disposed and removed...
> Problem:
> clicking the label and the view isn't in memory anymore.
> clicking the button causes the view to stay in memory.
--
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-33375) Button clicked in a Component (Group) causes the component to stay in memory
[
https://issues.apache.org/jira/browse/FLEX-33375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567929#comment-13567929
]
Christian Kiefer commented on FLEX-33375:
-
That was the problem... thanks a lot for your quick reponse!!!
> Button clicked in a Component (Group) causes the component to stay in memory
>
>
> Key: FLEX-33375
> URL: https://issues.apache.org/jira/browse/FLEX-33375
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark: Button
> Environment: air 3.5 mobile
>Reporter: Christian Kiefer
>Priority: Critical
>
> Code:
> protected function handleLoginClicked(event:MouseEvent):void
> {
> dispatchEvent(new LoginEvent(LoginEvent.LOGIN, "XYZ", "123"));
> }
>
> ]]>
>
> enabled="true"
> label="test"
> height="60"
> click="handleLoginClicked(event)"/>
>
>
> Result:
> After the login event is dispatched the view/current component (group) gets
> disposed and removed...
> Problem:
> clicking the label and the view isn't in memory anymore.
> clicking the button causes the view to stay in memory.
--
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-33366) The candidate input method can not follow
[ https://issues.apache.org/jira/browse/FLEX-33366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Harui updated FLEX-33366: -- Attachment: IMETest.zip Built with Adobe Flex 4.9.0 > The candidate input method can not follow > - > > Key: FLEX-33366 > URL: https://issues.apache.org/jira/browse/FLEX-33366 > Project: Apache Flex > Issue Type: Bug > Components: Spark: TextArea, Spark: TextInput >Affects Versions: Apache Flex 4.8 (parity release) > Environment: windows,IE8 >Reporter: zy > Attachments: IMETest.zip > > > The spark:TextArea and TextInput Chinese candidate input method can not > follow. > But mx:TextArea and TextInput not this issue. > I guess you only test the English input method, Chinese input methods all > have this problem, it is affecting the user experience. > you can test this Chinese input method.all chinese use this. > http://dl_dir.qq.com/invc/qqpinyin/QQPinyin_Setup_1.1.1224.400.exe > I made a picture to illustrate the problem. > http://img.my.csdn.net/uploads/201301/24/1359028348_2400.jpg > If you are unclear, please let me know. I don't know english.I am very sorry. > Thank you! -- 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-33366) The candidate input method can not follow
[ https://issues.apache.org/jira/browse/FLEX-33366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13568152#comment-13568152 ] Alex Harui edited comment on FLEX-33366 at 1/31/13 9:52 PM: Added zip of debug version built with Adobe Flex 4.9.0 was (Author: aharui): Built with Adobe Flex 4.9.0 > The candidate input method can not follow > - > > Key: FLEX-33366 > URL: https://issues.apache.org/jira/browse/FLEX-33366 > Project: Apache Flex > Issue Type: Bug > Components: Spark: TextArea, Spark: TextInput >Affects Versions: Apache Flex 4.8 (parity release) > Environment: windows,IE8 >Reporter: zy > Attachments: IMETest.zip > > > The spark:TextArea and TextInput Chinese candidate input method can not > follow. > But mx:TextArea and TextInput not this issue. > I guess you only test the English input method, Chinese input methods all > have this problem, it is affecting the user experience. > you can test this Chinese input method.all chinese use this. > http://dl_dir.qq.com/invc/qqpinyin/QQPinyin_Setup_1.1.1224.400.exe > I made a picture to illustrate the problem. > http://img.my.csdn.net/uploads/201301/24/1359028348_2400.jpg > If you are unclear, please let me know. I don't know english.I am very sorry. > Thank you! -- 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-33366) The candidate input method can not follow
[ https://issues.apache.org/jira/browse/FLEX-33366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13568157#comment-13568157 ] Alex Harui commented on FLEX-33366: --- Hi, I posted a zip file of a debug version built on my machine. I cannot reproduce your problem. My contacts in Beijing also attempted to reproduce the problem and could not. See if you can reproduce the problem with the files in this .zip file. If you can't, please attach a zip file from your system. Also, if you want to attach the URL of any internet discussion, I can try to get my contacts in Beijing to take a look. > The candidate input method can not follow > - > > Key: FLEX-33366 > URL: https://issues.apache.org/jira/browse/FLEX-33366 > Project: Apache Flex > Issue Type: Bug > Components: Spark: TextArea, Spark: TextInput >Affects Versions: Apache Flex 4.8 (parity release) > Environment: windows,IE8 >Reporter: zy > Attachments: IMETest.zip > > > The spark:TextArea and TextInput Chinese candidate input method can not > follow. > But mx:TextArea and TextInput not this issue. > I guess you only test the English input method, Chinese input methods all > have this problem, it is affecting the user experience. > you can test this Chinese input method.all chinese use this. > http://dl_dir.qq.com/invc/qqpinyin/QQPinyin_Setup_1.1.1224.400.exe > I made a picture to illustrate the problem. > http://img.my.csdn.net/uploads/201301/24/1359028348_2400.jpg > If you are unclear, please let me know. I don't know english.I am very sorry. > Thank you! -- 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-33366) The candidate input method can not follow
[ https://issues.apache.org/jira/browse/FLEX-33366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13568492#comment-13568492 ] Alex Harui commented on FLEX-33366: --- OK, my colleagues in Beijing were able to reproduce the problem. I will try to find time to determine if there is a solution or workaround. I was using the Microsoft IME which does not have the problem. > The candidate input method can not follow > - > > Key: FLEX-33366 > URL: https://issues.apache.org/jira/browse/FLEX-33366 > Project: Apache Flex > Issue Type: Bug > Components: Spark: TextArea, Spark: TextInput >Affects Versions: Apache Flex 4.8 (parity release) > Environment: windows,IE8 >Reporter: zy > Attachments: IMETest.zip > > > The spark:TextArea and TextInput Chinese candidate input method can not > follow. > But mx:TextArea and TextInput not this issue. > I guess you only test the English input method, Chinese input methods all > have this problem, it is affecting the user experience. > you can test this Chinese input method.all chinese use this. > http://dl_dir.qq.com/invc/qqpinyin/QQPinyin_Setup_1.1.1224.400.exe > I made a picture to illustrate the problem. > http://img.my.csdn.net/uploads/201301/24/1359028348_2400.jpg > If you are unclear, please let me know. I don't know english.I am very sorry. > Thank you! -- 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-33374) spark VideoDisplay and VideoPlayer fails to stream video on mobile devices
[ https://issues.apache.org/jira/browse/FLEX-33374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Thomas updated FLEX-33374: --- Priority: Minor (was: Major) Description: The spark VideoDisplay will not stream video from FMS 4.5, instead it appears to do progressive download instead, and it buffers the file for about one minute before it begins to play. However, the same code running in FlashPlayer on web, or in an AIR mobile simulator, the video properly streams and displays within seconds of playing. I understand VideoDisplay is not "optimized" for mobile, but that should not cause this behavior. I am in the process of debugging the spark codebase to find the root cause, but so far have been unsuccessful. So I attached a project that displays this behavior. Just unzip the file to a directory, start FB and point the workspace to the directory, open the project, build and run it first in an AIR simulator for an iOS mobile device, you'll see video instantly. Then deploy it in debug or release to an actual device. When you launch the project, you have to wait approximately a minute before the video will start playing. I'm assuming it's failing over to progressive download from streaming in some way, but I really have no idea what is causing the issue. UPDATE 2/1/2013 - I've downgraded the priority on this since I wrote my own video controller and display classes that just use NetConnection, NetStream, and Video classes. I guess for mobile that's the more optimized solution anyway, as VideDisplay and VideoPlayer seem pretty heavyweight in comparison. So I'm not waiting on this fix and suggest anyone building a mobile video player should do what I did anyway. was: The spark VideoDisplay will not stream video from FMS 4.5, instead it appears to do progressive download instead, and it buffers the file for about one minute before it begins to play. However, the same code running in FlashPlayer on web, or in an AIR mobile simulator, the video properly streams and displays within seconds of playing. I understand VideoDisplay is not "optimized" for mobile, but that should not cause this behavior. I am in the process of debugging the spark codebase to find the root cause, but so far have been unsuccessful. So I attached a project that displays this behavior. Just unzip the file to a directory, start FB and point the workspace to the directory, open the project, build and run it first in an AIR simulator for an iOS mobile device, you'll see video instantly. Then deploy it in debug or release to an actual device. When you launch the project, you have to wait approximately a minute before the video will start playing. I'm assuming it's failing over to progressive download from streaming in some way, but I really have no idea what is causing the issue. I really don't care if the performance of the VideoDisplay isn't optimized for mobile, and a delayed start of several seconds would be fine, but one minute? If I find a root cause I will update this defect record with my findings as this is a blocker for us so that's my focus. > spark VideoDisplay and VideoPlayer fails to stream video on mobile devices > -- > > Key: FLEX-33374 > URL: https://issues.apache.org/jira/browse/FLEX-33374 > Project: Apache Flex > Issue Type: Bug > Components: Spark: VideoPlayer >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: FlashBuilder 4.7 on Windows 7, iPad 3, iPhone 4, remote > FMS 4.5 server, FLV Video source in 112K bitrate. >Reporter: Erik Thomas >Priority: Minor > Attachments: VideoDisplay.jpg, VideoPlayback.zip > > > The spark VideoDisplay will not stream video from FMS 4.5, instead it appears > to do progressive download instead, and it buffers the file for about one > minute before it begins to play. > However, the same code running in FlashPlayer on web, or in an AIR mobile > simulator, the video properly streams and displays within seconds of playing. > I understand VideoDisplay is not "optimized" for mobile, but that should not > cause this behavior. I am in the process of debugging the spark codebase to > find the root cause, but so far have been unsuccessful. > So I attached a project that displays this behavior. Just unzip the file to a > directory, start FB and point the workspace to the directory, open the > project, build and run it first in an AIR simulator for an iOS mobile device, > you'll see video instantly. Then deploy it in debug or release to an actual > device. When you launch the project, you have to wait app
[jira] [Updated] (FLEX-33374) spark VideoDisplay and VideoPlayer fails to stream video on mobile devices
[ https://issues.apache.org/jira/browse/FLEX-33374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Thomas updated FLEX-33374: --- Description: The spark VideoDisplay will not stream video from FMS 4.5, instead it appears to do progressive download instead, and it buffers the file for about one minute before it begins to play. However, the same code running in FlashPlayer on web, or in an AIR mobile simulator, the video properly streams and displays within seconds of playing. I understand VideoDisplay is not "optimized" for mobile, but that should not cause this behavior. I am in the process of debugging the spark codebase to find the root cause, but so far have been unsuccessful. So I attached a project that displays this behavior. Just unzip the file to a directory, start FB and point the workspace to the directory, open the project, build and run it first in an AIR simulator for an iOS mobile device, you'll see video instantly. Then deploy it in debug or release to an actual device. When you launch the project, you have to wait approximately a minute before the video will start playing. I'm assuming it's failing over to progressive download from streaming in some way, but I really have no idea what is causing the issue. UPDATE 2/1/2013 - I've downgraded the priority on this since I wrote my own video controller and display classes that just use NetConnection, NetStream, and Video classes. I guess for mobile that's the more optimized solution anyway, as VideoDisplay and VideoPlayer seem pretty heavyweight in comparison. So I'm not waiting on this fix and suggest anyone building a mobile video player should do what I did anyway. Of course we have to do our own bandwidth testing which requires a server-side asc on FMS, but that's actually working better than VideoDisplay's adaptive bitrates anyway that resize the video way too often, so it's really a win not to depend on OSMF. was: The spark VideoDisplay will not stream video from FMS 4.5, instead it appears to do progressive download instead, and it buffers the file for about one minute before it begins to play. However, the same code running in FlashPlayer on web, or in an AIR mobile simulator, the video properly streams and displays within seconds of playing. I understand VideoDisplay is not "optimized" for mobile, but that should not cause this behavior. I am in the process of debugging the spark codebase to find the root cause, but so far have been unsuccessful. So I attached a project that displays this behavior. Just unzip the file to a directory, start FB and point the workspace to the directory, open the project, build and run it first in an AIR simulator for an iOS mobile device, you'll see video instantly. Then deploy it in debug or release to an actual device. When you launch the project, you have to wait approximately a minute before the video will start playing. I'm assuming it's failing over to progressive download from streaming in some way, but I really have no idea what is causing the issue. UPDATE 2/1/2013 - I've downgraded the priority on this since I wrote my own video controller and display classes that just use NetConnection, NetStream, and Video classes. I guess for mobile that's the more optimized solution anyway, as VideDisplay and VideoPlayer seem pretty heavyweight in comparison. So I'm not waiting on this fix and suggest anyone building a mobile video player should do what I did anyway. > spark VideoDisplay and VideoPlayer fails to stream video on mobile devices > ------ > > Key: FLEX-33374 > URL: https://issues.apache.org/jira/browse/FLEX-33374 > Project: Apache Flex > Issue Type: Bug > Components: Spark: VideoPlayer >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: FlashBuilder 4.7 on Windows 7, iPad 3, iPhone 4, remote > FMS 4.5 server, FLV Video source in 112K bitrate. >Reporter: Erik Thomas >Priority: Minor > Attachments: VideoDisplay.jpg, VideoPlayback.zip > > > The spark VideoDisplay will not stream video from FMS 4.5, instead it appears > to do progressive download instead, and it buffers the file for about one > minute before it begins to play. > However, the same code running in FlashPlayer on web, or in an AIR mobile > simulator, the video properly streams and displays within seconds of playing. > I understand VideoDisplay is not "optimized" for mobile, but that should not > cause this behavior. I am in the process of debugging the spark codebase to > find the root cause, but so far have been unsuccessful. > So I attached a
[jira] [Comment Edited] (FLEX-33374) spark VideoDisplay and VideoPlayer fails to stream video on mobile devices
[ https://issues.apache.org/jira/browse/FLEX-33374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567717#comment-13567717 ] Erik Thomas edited comment on FLEX-33374 at 2/1/13 3:02 PM: Just unzip to a new directory, start FB 4.7 and create a new workspace that points to the directory. Build and run the project in an AIR simulator first. Video streams from my FMS 4.5 server immediately. Do the test again on an actual device, either debug or release, and you will have to wait for about a minute before the video begins to play. The issue is not bandwidth. I'm running the device on my same network with the same connectivity and bandwidth as my dev computer over WiFi. was (Author: ejtho...@ejthomas.com): Just unzip to a new directory, start FB 4.7 and create a new workspace that points to the directory. Build and run the project in an AIR simulator first. Video streams from my FMS 4.5 server immediately. Do the test again on an actual device, either debug or release, and you will have to wait for about a minute before the video begins to play. There is no possible way that bandwidth is the issue here. I'm running the device on my same network with the same connectivity and bandwidth as my dev computer. My devices are using WiFi so there's no way cellular bandwidth is playing any role in this issue and even if bandwidth was a contributor it would only delay a start by seconds, not a minute. I'm just hopeful someone is really familiar with this functionality and will know what's wrong for an easy fix. I'm debugging into the sources now to try to find a root cause, but I'm unfamiliar with the spark internals, especially of MediaPlayer and MediaElement, etc. > spark VideoDisplay and VideoPlayer fails to stream video on mobile devices > -- > > Key: FLEX-33374 > URL: https://issues.apache.org/jira/browse/FLEX-33374 > Project: Apache Flex > Issue Type: Bug > Components: Spark: VideoPlayer >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: FlashBuilder 4.7 on Windows 7, iPad 3, iPhone 4, remote > FMS 4.5 server, FLV Video source in 112K bitrate. >Reporter: Erik Thomas >Priority: Minor > Attachments: VideoDisplay.jpg, VideoPlayback.zip > > > The spark VideoDisplay will not stream video from FMS 4.5, instead it appears > to do progressive download instead, and it buffers the file for about one > minute before it begins to play. > However, the same code running in FlashPlayer on web, or in an AIR mobile > simulator, the video properly streams and displays within seconds of playing. > I understand VideoDisplay is not "optimized" for mobile, but that should not > cause this behavior. I am in the process of debugging the spark codebase to > find the root cause, but so far have been unsuccessful. > So I attached a project that displays this behavior. Just unzip the file to a > directory, start FB and point the workspace to the directory, open the > project, build and run it first in an AIR simulator for an iOS mobile device, > you'll see video instantly. Then deploy it in debug or release to an actual > device. When you launch the project, you have to wait approximately a minute > before the video will start playing. > I'm assuming it's failing over to progressive download from streaming in some > way, but I really have no idea what is causing the issue. > UPDATE 2/1/2013 - I've downgraded the priority on this since I wrote my own > video controller and display classes that just use NetConnection, NetStream, > and Video classes. I guess for mobile that's the more optimized solution > anyway, as VideoDisplay and VideoPlayer seem pretty heavyweight in > comparison. So I'm not waiting on this fix and suggest anyone building a > mobile video player should do what I did anyway. Of course we have to do our > own bandwidth testing which requires a server-side asc on FMS, but that's > actually working better than VideoDisplay's adaptive bitrates anyway that > resize the video way too often, so it's really a win not to depend on OSMF. -- 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] [Issue Comment Deleted] (FLEX-33374) spark VideoDisplay and VideoPlayer fails to stream video on mobile devices
[ https://issues.apache.org/jira/browse/FLEX-33374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Thomas updated FLEX-33374: --- Comment: was deleted (was: And yes, I understand the spark VideoDisplay leverages OSMF, including MediaPlayer and MediaElement and the defect may belong to OSMF. I will download and debug their sources and see if I can find something. ) > spark VideoDisplay and VideoPlayer fails to stream video on mobile devices > -- > > Key: FLEX-33374 > URL: https://issues.apache.org/jira/browse/FLEX-33374 > Project: Apache Flex > Issue Type: Bug > Components: Spark: VideoPlayer >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: FlashBuilder 4.7 on Windows 7, iPad 3, iPhone 4, remote > FMS 4.5 server, FLV Video source in 112K bitrate. >Reporter: Erik Thomas >Priority: Minor > Attachments: VideoDisplay.jpg, VideoPlayback.zip > > > The spark VideoDisplay will not stream video from FMS 4.5, instead it appears > to do progressive download instead, and it buffers the file for about one > minute before it begins to play. > However, the same code running in FlashPlayer on web, or in an AIR mobile > simulator, the video properly streams and displays within seconds of playing. > I understand VideoDisplay is not "optimized" for mobile, but that should not > cause this behavior. I am in the process of debugging the spark codebase to > find the root cause, but so far have been unsuccessful. > So I attached a project that displays this behavior. Just unzip the file to a > directory, start FB and point the workspace to the directory, open the > project, build and run it first in an AIR simulator for an iOS mobile device, > you'll see video instantly. Then deploy it in debug or release to an actual > device. When you launch the project, you have to wait approximately a minute > before the video will start playing. > I'm assuming it's failing over to progressive download from streaming in some > way, but I really have no idea what is causing the issue. > UPDATE 2/1/2013 - I've downgraded the priority on this since I wrote my own > video controller and display classes that just use NetConnection, NetStream, > and Video classes. I guess for mobile that's the more optimized solution > anyway, as VideoDisplay and VideoPlayer seem pretty heavyweight in > comparison. So I'm not waiting on this fix and suggest anyone building a > mobile video player should do what I did anyway. Of course we have to do our > own bandwidth testing which requires a server-side asc on FMS, but that's > actually working better than VideoDisplay's adaptive bitrates anyway that > resize the video way too often, so it's really a win not to depend on OSMF. -- 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] [Issue Comment Deleted] (FLEX-33374) spark VideoDisplay and VideoPlayer fails to stream video on mobile devices
[ https://issues.apache.org/jira/browse/FLEX-33374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Thomas updated FLEX-33374: --- Comment: was deleted (was: This is a screen shot of an AIR simulator for the iPhone. The video streams immediately. If you run the same app on the device itself, with WiFi connectivity and high bandwidth connection, it still takes a minute before the video begins playing.) > spark VideoDisplay and VideoPlayer fails to stream video on mobile devices > -- > > Key: FLEX-33374 > URL: https://issues.apache.org/jira/browse/FLEX-33374 > Project: Apache Flex > Issue Type: Bug > Components: Spark: VideoPlayer >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: FlashBuilder 4.7 on Windows 7, iPad 3, iPhone 4, remote > FMS 4.5 server, FLV Video source in 112K bitrate. >Reporter: Erik Thomas >Priority: Minor > Attachments: VideoDisplay.jpg, VideoPlayback.zip > > > The spark VideoDisplay will not stream video from FMS 4.5, instead it appears > to do progressive download instead, and it buffers the file for about one > minute before it begins to play. > However, the same code running in FlashPlayer on web, or in an AIR mobile > simulator, the video properly streams and displays within seconds of playing. > I understand VideoDisplay is not "optimized" for mobile, but that should not > cause this behavior. I am in the process of debugging the spark codebase to > find the root cause, but so far have been unsuccessful. > So I attached a project that displays this behavior. Just unzip the file to a > directory, start FB and point the workspace to the directory, open the > project, build and run it first in an AIR simulator for an iOS mobile device, > you'll see video instantly. Then deploy it in debug or release to an actual > device. When you launch the project, you have to wait approximately a minute > before the video will start playing. > I'm assuming it's failing over to progressive download from streaming in some > way, but I really have no idea what is causing the issue. > UPDATE 2/1/2013 - I've downgraded the priority on this since I wrote my own > video controller and display classes that just use NetConnection, NetStream, > and Video classes. I guess for mobile that's the more optimized solution > anyway, as VideoDisplay and VideoPlayer seem pretty heavyweight in > comparison. So I'm not waiting on this fix and suggest anyone building a > mobile video player should do what I did anyway. Of course we have to do our > own bandwidth testing which requires a server-side asc on FMS, but that's > actually working better than VideoDisplay's adaptive bitrates anyway that > resize the video way too often, so it's really a win not to depend on OSMF. -- 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] [Issue Comment Deleted] (FLEX-33374) spark VideoDisplay and VideoPlayer fails to stream video on mobile devices
[ https://issues.apache.org/jira/browse/FLEX-33374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Thomas updated FLEX-33374: --- Comment: was deleted (was: BTW, I thought of tryng to use StageVideo but the problem there is, we display the video in a popup container. StageVideo plays underneath the display tree and cannot be displayed within a popup Flex container. I'm also trying to workaround this with Netconnection, Netstream and Video classes instead but it would be really cool to have VideoDisplay stream on mobile.) > spark VideoDisplay and VideoPlayer fails to stream video on mobile devices > -- > > Key: FLEX-33374 > URL: https://issues.apache.org/jira/browse/FLEX-33374 > Project: Apache Flex > Issue Type: Bug > Components: Spark: VideoPlayer >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: FlashBuilder 4.7 on Windows 7, iPad 3, iPhone 4, remote > FMS 4.5 server, FLV Video source in 112K bitrate. >Reporter: Erik Thomas >Priority: Minor > Attachments: VideoDisplay.jpg, VideoPlayback.zip > > > The spark VideoDisplay will not stream video from FMS 4.5, instead it appears > to do progressive download instead, and it buffers the file for about one > minute before it begins to play. > However, the same code running in FlashPlayer on web, or in an AIR mobile > simulator, the video properly streams and displays within seconds of playing. > I understand VideoDisplay is not "optimized" for mobile, but that should not > cause this behavior. I am in the process of debugging the spark codebase to > find the root cause, but so far have been unsuccessful. > So I attached a project that displays this behavior. Just unzip the file to a > directory, start FB and point the workspace to the directory, open the > project, build and run it first in an AIR simulator for an iOS mobile device, > you'll see video instantly. Then deploy it in debug or release to an actual > device. When you launch the project, you have to wait approximately a minute > before the video will start playing. > I'm assuming it's failing over to progressive download from streaming in some > way, but I really have no idea what is causing the issue. > UPDATE 2/1/2013 - I've downgraded the priority on this since I wrote my own > video controller and display classes that just use NetConnection, NetStream, > and Video classes. I guess for mobile that's the more optimized solution > anyway, as VideoDisplay and VideoPlayer seem pretty heavyweight in > comparison. So I'm not waiting on this fix and suggest anyone building a > mobile video player should do what I did anyway. Of course we have to do our > own bandwidth testing which requires a server-side asc on FMS, but that's > actually working better than VideoDisplay's adaptive bitrates anyway that > resize the video way too often, so it's really a win not to depend on OSMF. -- 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-33374) spark VideoDisplay and VideoPlayer fails to stream video on mobile devices
[ https://issues.apache.org/jira/browse/FLEX-33374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Thomas updated FLEX-33374: --- Description: The spark VideoDisplay on Mobile devices delays streaming video from FMS 4.5 for about a minute before it begins playing. I've attached a project that displays this behavior. Run it in AIR on your desktop or in a simulator, then run it on a device that's using WiFi with the same bandwidth as your computer to see the difference. This is probably a problem in OSMF but I'm posting it here for visibility to the problem. UPDATE 2/1/2013 - I wrote my own video controller and display classes that just use NetConnection, NetStream, and Video classes. This is a more optimized solution for mobile anyway, to not use heavyweight OSMF classes underneath the spark VideoPlayer and VideoDisplay classes. So I'm not waiting on this fix and suggest anyone building a mobile video player should do what I did anyway. Of course we have to do our own bandwidth testing which requires a server-side asc on FMS, but that's actually working better than VideoDisplay's adaptive bitrates anyway that resize the video way too often. was: The spark VideoDisplay will not stream video from FMS 4.5, instead it appears to do progressive download instead, and it buffers the file for about one minute before it begins to play. However, the same code running in FlashPlayer on web, or in an AIR mobile simulator, the video properly streams and displays within seconds of playing. I understand VideoDisplay is not "optimized" for mobile, but that should not cause this behavior. I am in the process of debugging the spark codebase to find the root cause, but so far have been unsuccessful. So I attached a project that displays this behavior. Just unzip the file to a directory, start FB and point the workspace to the directory, open the project, build and run it first in an AIR simulator for an iOS mobile device, you'll see video instantly. Then deploy it in debug or release to an actual device. When you launch the project, you have to wait approximately a minute before the video will start playing. I'm assuming it's failing over to progressive download from streaming in some way, but I really have no idea what is causing the issue. UPDATE 2/1/2013 - I've downgraded the priority on this since I wrote my own video controller and display classes that just use NetConnection, NetStream, and Video classes. I guess for mobile that's the more optimized solution anyway, as VideoDisplay and VideoPlayer seem pretty heavyweight in comparison. So I'm not waiting on this fix and suggest anyone building a mobile video player should do what I did anyway. Of course we have to do our own bandwidth testing which requires a server-side asc on FMS, but that's actually working better than VideoDisplay's adaptive bitrates anyway that resize the video way too often, so it's really a win not to depend on OSMF. > spark VideoDisplay and VideoPlayer fails to stream video on mobile devices > -- > > Key: FLEX-33374 > URL: https://issues.apache.org/jira/browse/FLEX-33374 > Project: Apache Flex > Issue Type: Bug > Components: Spark: VideoPlayer >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: FlashBuilder 4.7 on Windows 7, iPad 3, iPhone 4, remote > FMS 4.5 server, FLV Video source in 112K bitrate. >Reporter: Erik Thomas >Priority: Minor > Attachments: VideoDisplay.jpg, VideoPlayback.zip > > > The spark VideoDisplay on Mobile devices delays streaming video from FMS 4.5 > for about a minute before it begins playing. > I've attached a project that displays this behavior. Run it in AIR on your > desktop or in a simulator, then run it on a device that's using WiFi with the > same bandwidth as your computer to see the difference. > This is probably a problem in OSMF but I'm posting it here for visibility to > the problem. > UPDATE 2/1/2013 - I wrote my own video controller and display classes that > just use NetConnection, NetStream, and Video classes. This is a more > optimized solution for mobile anyway, to not use heavyweight OSMF classes > underneath the spark VideoPlayer and VideoDisplay classes. So I'm not waiting > on this fix and suggest anyone building a mobile video player should do what > I did anyway. Of course we have to do our own bandwidth testing which > requires a server-side asc on FMS, but that's actually working better than > VideoDisplay's adaptive bitrates anyway that resize the video way too often. -- 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-33374) spark VideoDisplay and VideoPlayer fails to stream video on mobile devices
[ https://issues.apache.org/jira/browse/FLEX-33374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Thomas updated FLEX-33374: --- Description: The spark VideoDisplay on Mobile devices delays streaming video from FMS 4.5 for about a minute before it begins playing. I've attached a project that displays this behavior. Run it in AIR on your desktop or in a simulator, then run it on a device that's using WiFi with the same bandwidth as your computer to see the difference. This is probably a problem in OSMF but I'm posting it here for visibility to the problem. UPDATE 2/1/2013 - I wrote my own video controller and display classes that just use NetConnection, NetStream, and Video classes. This is a more optimized solution for mobile anyway, to not use heavyweight OSMF classes underneath the spark VideoPlayer and VideoDisplay classes. So I'm not waiting on this fix and suggest anyone building a mobile video player should do what I did anyway. Of course we have to do our own bandwidth testing which requires a server-side asc on FMS, but that's actually working better than VideoDisplay's adaptive bitrates anyway that resize the video way too often. And I'll still have to add some reconnect logic in case the stream is interrupted. was: The spark VideoDisplay on Mobile devices delays streaming video from FMS 4.5 for about a minute before it begins playing. I've attached a project that displays this behavior. Run it in AIR on your desktop or in a simulator, then run it on a device that's using WiFi with the same bandwidth as your computer to see the difference. This is probably a problem in OSMF but I'm posting it here for visibility to the problem. UPDATE 2/1/2013 - I wrote my own video controller and display classes that just use NetConnection, NetStream, and Video classes. This is a more optimized solution for mobile anyway, to not use heavyweight OSMF classes underneath the spark VideoPlayer and VideoDisplay classes. So I'm not waiting on this fix and suggest anyone building a mobile video player should do what I did anyway. Of course we have to do our own bandwidth testing which requires a server-side asc on FMS, but that's actually working better than VideoDisplay's adaptive bitrates anyway that resize the video way too often. > spark VideoDisplay and VideoPlayer fails to stream video on mobile devices > -- > > Key: FLEX-33374 > URL: https://issues.apache.org/jira/browse/FLEX-33374 > Project: Apache Flex > Issue Type: Bug > Components: Spark: VideoPlayer >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: FlashBuilder 4.7 on Windows 7, iPad 3, iPhone 4, remote > FMS 4.5 server, FLV Video source in 112K bitrate. >Reporter: Erik Thomas >Priority: Minor > Attachments: VideoDisplay.jpg, VideoPlayback.zip > > > The spark VideoDisplay on Mobile devices delays streaming video from FMS 4.5 > for about a minute before it begins playing. > I've attached a project that displays this behavior. Run it in AIR on your > desktop or in a simulator, then run it on a device that's using WiFi with the > same bandwidth as your computer to see the difference. > This is probably a problem in OSMF but I'm posting it here for visibility to > the problem. > UPDATE 2/1/2013 - I wrote my own video controller and display classes that > just use NetConnection, NetStream, and Video classes. This is a more > optimized solution for mobile anyway, to not use heavyweight OSMF classes > underneath the spark VideoPlayer and VideoDisplay classes. So I'm not waiting > on this fix and suggest anyone building a mobile video player should do what > I did anyway. Of course we have to do our own bandwidth testing which > requires a server-side asc on FMS, but that's actually working better than > VideoDisplay's adaptive bitrates anyway that resize the video way too often. > And I'll still have to add some reconnect logic in case the stream is > interrupted. -- 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-33378) Add totalItems to s:ItemRenderer
JC Franco created FLEX-33378: Summary: Add totalItems to s:ItemRenderer Key: FLEX-33378 URL: https://issues.apache.org/jira/browse/FLEX-33378 Project: Apache Flex Issue Type: Improvement Components: Spark Components Affects Versions: Apache Flex 4.9.0 Reporter: JC Franco Add totalItems property to help determine the renderer's index relative to other items. A use case for this is changing the renderer's state based on its position. -- 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-33366) The candidate input method can not follow
[ https://issues.apache.org/jira/browse/FLEX-33366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Harui resolved FLEX-33366. --- Resolution: Invalid A simple ActionScript project without Flex also has the problem, so this is an issue with the Flash Player, not Flex. Please file a bug against the Flash Player at bugbase.adobe.com. I will see if I can create a simple workaround. > The candidate input method can not follow > - > > Key: FLEX-33366 > URL: https://issues.apache.org/jira/browse/FLEX-33366 > Project: Apache Flex > Issue Type: Bug > Components: Spark: TextArea, Spark: TextInput >Affects Versions: Apache Flex 4.8 (parity release) > Environment: windows,IE8 >Reporter: zy > Attachments: IMETest.zip > > > The spark:TextArea and TextInput Chinese candidate input method can not > follow. > But mx:TextArea and TextInput not this issue. > I guess you only test the English input method, Chinese input methods all > have this problem, it is affecting the user experience. > you can test this Chinese input method.all chinese use this. > http://dl_dir.qq.com/invc/qqpinyin/QQPinyin_Setup_1.1.1224.400.exe > I made a picture to illustrate the problem. > http://img.my.csdn.net/uploads/201301/24/1359028348_2400.jpg > If you are unclear, please let me know. I don't know english.I am very sorry. > Thank you! -- 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-33380) Get Internal build error on new Mobile Air App Project
Giles Roadnight created FLEX-33380: -- Summary: Get Internal build error on new Mobile Air App Project Key: FLEX-33380 URL: https://issues.apache.org/jira/browse/FLEX-33380 Project: Apache Flex Issue Type: Bug Components: Compiler API Affects Versions: Apache Flex 4.9.0 Environment: Flash Builder 4.6 on Windows 7 64 bit Reporter: Giles Roadnight When I create a new Flex Mobile project in Flash builder with all default options selected I get an internal build error. When I look at the logs I get: Uncaught exception in compiler java.lang.IllegalArgumentException: Comparison method violates its general contract! at java.util.TimSort.mergeHi(Unknown Source) at java.util.TimSort.mergeAt(Unknown Source) at java.util.TimSort.mergeCollapse(Unknown Source) at java.util.TimSort.sort(Unknown Source) at java.util.TimSort.sort(Unknown Source) at java.util.Arrays.sort(Unknown Source) at flex2.compiler.swc.SwcGroup.updateMaps(SwcGroup.java:281) at flex2.compiler.swc.SwcGroup.(SwcGroup.java:82) at flex2.compiler.swc.SwcCache.getSwcGroup(SwcCache.java:137) at flex2.compiler.CompilerSwcContext.load(CompilerSwcContext.java:145) at flex2.tools.oem.Application.recompile(Application.java:1170) at flex2.tools.oem.Application.compile(Application.java:894) at flex2.tools.flexbuilder.BuilderApplication.compile(BuilderApplication.java:367) at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder$MyBuilder.mybuild(ASApplicationBuilder.java:319) at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.build(ASApplicationBuilder.java:129) at com.adobe.flexbuilder.multisdk.compiler.internal.ASBuilder.build(ASBuilder.java:198) at com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.build(ASItemBuilder.java:70) at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.buildItem(FlexProjectBuilder.java:607) at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.build(FlexProjectBuilder.java:382) at com.adobe.flexbuilder.project.compiler.internal.FlexIncrementalBuilder.build(FlexIncrementalBuilder.java:187) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:629) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:172) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:203) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:220) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:362) at org.eclipse.core.internal.resources.Project$1.run(Project.java:545) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:524) at org.eclipse.core.internal.resources.Project.build(Project.java:115) at org.eclipse.ui.actions.BuildAction.invokeOperation(BuildAction.java:222) at org.eclipse.ui.actions.WorkspaceAction.execute(WorkspaceAction.java:162) at org.eclipse.ui.actions.WorkspaceAction$2.runInWorkspace(WorkspaceAction.java:483) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) eclipse.buildId=M20100909-0800 java.version=1.7.0_05 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB Command-line arguments: -os win32 -ws win32 -arch x86 This is a continuation of log file C:\Users\Giles Roadnight\workspace\.metadata\.bak_1.log Created Time: 2013-02-03 11:11:13.045 -- 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-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:comment-tabpanel&focusedCommentId=13569760#comment-13569760 ] Andy Hawksworth commented on FLEX-27543: Wrapping behaviour already exists on Spark NumbericStepper component though this is disabled by default, see the allowValueWrap property. > 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 > > 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] [Resolved] (FLEX-33311) Nullpointer in ConstraintLayout when executing Transition on content
[
https://issues.apache.org/jira/browse/FLEX-33311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxime Cowez resolved FLEX-33311.
-
Resolution: Fixed
Fix Version/s: Apache Flex 4.9.0
Though no-one was assigned to this particular bug, apparently it has somehow
been fixed in 4.9
I have no idea what the possibly related issue(s) might be.
(I can still reproduce it in 4.8, so this is not due to "external" conditions
of my test application or anything.)
> Nullpointer in ConstraintLayout when executing Transition on content
>
>
> Key: FLEX-33311
> URL: https://issues.apache.org/jira/browse/FLEX-33311
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark: Layout, Transitions
>Affects Versions: Apache Flex 4.8 (parity release)
>Reporter: Maxime Cowez
>Priority: Trivial
> Fix For: Apache Flex 4.9.0
>
> Attachments: SpecifiableListWrapper.as,
> SpecifiableListWrapperHorizontalSkin.mxml
>
>
> In some very specific cases `ConstraintLayout` will throw a nullpointer error
> when a component inside it is playing a transition. I tried a few things and
> found out that:
> - `parseConstraints()` creates a new `rowBaselines` Vector (or empties it if
> it exists)
> - some other process calls `clearConstraintCache()` in the middle of the
> execution of `parseConstraints()`, setting `rowBaselines` back to `null`
> - `parseConstraints()` calls `parseElementConstraints()` which tries to
> access elements in `rowBaselines` and throws a nullpointer error
> I know very little about how Effects and Transitions work, so the "some other
> process" part is a bit of a mistery to me.
> Here is some code to reproduce the error consistently. My apologies for the
> complexity, but I couldn't get a simpler example to trigger the error.
>
>
>
>
>
>
>
>
>
>
> height="100%"/>
>
>
>
> bottom="row1:10">
> skinClass="SpecifiableListWrapperHorizontalSkin">
>
>
>
> bottom="row1:10" baseline="row1:0"/>
>
> As you may notice, the constraint columns and rows are a copy of those used
> in FormItemSkin. I left only the content columns necessary to trigger the
> error (yup, remove the `helpContentGroup` and the error's gone).
> SpecifiableListWrapper is a custom component which I will attach, along with
> the specific skin that has the Transition that triggers the error.
> Workaround: subclass ConstraintLayout (or FormItemLayout), override
> `measure()`, put a try/cacth block around it and use this custom layout.
> public class FormItemLayout extends spark.layouts.FormItemLayout {
> override public function measure():void {
> try {
> super.measure();
> }
> catch (e:Error) { }
> }
> }
> Not exactly pretty but it works without apparent side effects.
> Quick fix (but probably not the ideal solution): just test whether
> `rowBaselines` exists before trying to access it >
> if (rowBaselines && rowBaselines[bIndex][1]) ...
> instead of
> if (rowBaselines[bIndex][1]) ...
--
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-33381) Setting s:ComboBox#typicalItem produces unnecessarily long width
JC Franco created FLEX-33381: Summary: Setting s:ComboBox#typicalItem produces unnecessarily long width Key: FLEX-33381 URL: https://issues.apache.org/jira/browse/FLEX-33381 Project: Apache Flex Issue Type: Bug Components: Spark: ComboBox Affects Versions: Apache Flex 4.9.0 Reporter: JC Franco Setting s:ComboBox#typicalItem produces unnecessarily long width. By contrast, s:DropDownList behaves as expected when setting its typicalItem property. Sample application: http://ns.adobe.com/mxml/2009"; xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/mx" minHeight="600" minWidth="955"> Avenir Next Condensed Demi Bold Italic Avenir Next Condensed Demi Bold Italic Avenir Next Condensed Demi Bold Italic -- 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-33382) Run Time Error 1009 in mx:Combobox in destoryDropdown
Justin Mclean created FLEX-33382: Summary: Run Time Error 1009 in mx:Combobox in destoryDropdown Key: FLEX-33382 URL: https://issues.apache.org/jira/browse/FLEX-33382 Project: Apache Flex Issue Type: Bug Components: mx: ComboBox Affects Versions: Adobe Flex SDK 4.6 (Release) Reporter: Justin Mclean Assignee: Justin Mclean Priority: Minor Run Time Error 1009 in destroyDropdown(), occurs infrequently and not easy to reproduce. Sample stack trace (from 11.5 release player). TypeError: Error #1009 at mx.controls::ComboBox/destroyDropdown() at mx.controls::ComboBox/removedFromStageHandler() at mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::$removeChild() at mx.core::UIComponent/removeChild() at mx.core::UIComponent/addChild() at mx.controls::AdvancedDataGrid/addRendererToContentArea() at mx.controls::AdvancedDataGrid/createHeaderItems() at mx.controls::AdvancedDataGrid/createHeaders() at mx.controls.advancedDataGridClasses::AdvancedDataGridBase/makeRowsAndColumns() at mx.controls::AdvancedDataGridBaseEx/makeRowsAndColumns() at mx.controls::AdvancedDataGrid/makeRowsAndColumns() at mx.controls.listClasses::AdvancedListBase/makeRowsAndColumnsWithExtraRows() at mx.controls.listClasses::AdvancedListBase/updateDisplayList() at mx.controls::AdvancedDataGridBaseEx/updateDisplayList() at mx.controls::AdvancedDataGrid/updateDisplayList() at mx.controls.listClasses::AdvancedListBase/validateDisplayList() at mx.managers::LayoutManager/validateDisplayList() at mx.managers::LayoutManager/doPhasedInstantiation() at mx.managers::LayoutManager/validateNow() at mx.controls::ComboBox/displayDropdown() at mx.controls::ComboBox/downArrowButton_buttonDownHandler() at flash.events::EventDispatcher/dispatchEvent() at mx.core::UIComponent/dispatchEvent() at mx.controls::Button/http://www.adobe.com/2006/flex/mx/internal::buttonPressed() at mx.controls::Button/mouseDownHandler() at flash.events::EventDispatcher/dispatchEvent() at mx.core::UIComponent/dispatchEvent() at mx.managers::SystemManager/mouseEventHandler() -- 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-33382) Run Time Error 1009 in mx:Combobox in destoryDropdown
[ https://issues.apache.org/jira/browse/FLEX-33382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-33382. -- Resolution: Fixed Fix Version/s: Apache Flex 4.10.0 Check if tween is null before called method. SVN revision check in 142453. > Run Time Error 1009 in mx:Combobox in destoryDropdown > - > > Key: FLEX-33382 > URL: https://issues.apache.org/jira/browse/FLEX-33382 > Project: Apache Flex > Issue Type: Bug > Components: mx: ComboBox >Affects Versions: Adobe Flex SDK 4.6 (Release) >Reporter: Justin Mclean >Assignee: Justin Mclean >Priority: Minor > Fix For: Apache Flex 4.10.0 > > > Run Time Error 1009 in destroyDropdown(), occurs infrequently and not easy to > reproduce. > Sample stack trace (from 11.5 release player). > TypeError: Error #1009 > at mx.controls::ComboBox/destroyDropdown() > at mx.controls::ComboBox/removedFromStageHandler() > at > mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::$removeChild() > at mx.core::UIComponent/removeChild() > at mx.core::UIComponent/addChild() > at mx.controls::AdvancedDataGrid/addRendererToContentArea() > at mx.controls::AdvancedDataGrid/createHeaderItems() > at mx.controls::AdvancedDataGrid/createHeaders() > at > mx.controls.advancedDataGridClasses::AdvancedDataGridBase/makeRowsAndColumns() > at mx.controls::AdvancedDataGridBaseEx/makeRowsAndColumns() > at mx.controls::AdvancedDataGrid/makeRowsAndColumns() > at > mx.controls.listClasses::AdvancedListBase/makeRowsAndColumnsWithExtraRows() > at mx.controls.listClasses::AdvancedListBase/updateDisplayList() > at mx.controls::AdvancedDataGridBaseEx/updateDisplayList() > at mx.controls::AdvancedDataGrid/updateDisplayList() > at mx.controls.listClasses::AdvancedListBase/validateDisplayList() > at mx.managers::LayoutManager/validateDisplayList() > at mx.managers::LayoutManager/doPhasedInstantiation() > at mx.managers::LayoutManager/validateNow() > at mx.controls::ComboBox/displayDropdown() > at mx.controls::ComboBox/downArrowButton_buttonDownHandler() > at flash.events::EventDispatcher/dispatchEvent() > at mx.core::UIComponent/dispatchEvent() > at > mx.controls::Button/http://www.adobe.com/2006/flex/mx/internal::buttonPressed() > at mx.controls::Button/mouseDownHandler() > at flash.events::EventDispatcher/dispatchEvent() > at mx.core::UIComponent/dispatchEvent() > at mx.managers::SystemManager/mouseEventHandler() -- 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-33273) CSSCondition.matchesStyleClient() is slow and creates excessive garbage
[
https://issues.apache.org/jira/browse/FLEX-33273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570902#comment-13570902
]
RJ Camarillo commented on FLEX-33273:
-
I don't see the changes for this in the trunk. Was it reverted?
> CSSCondition.matchesStyleClient() is slow and creates excessive garbage
> ---
>
> Key: FLEX-33273
> URL: https://issues.apache.org/jira/browse/FLEX-33273
> Project: Apache Flex
> Issue Type: Improvement
> Components: Styles
>Affects Versions: Adobe Flex SDK 4.1 (Release), Adobe Flex SDK 4.5
> (Release), Adobe Flex SDK 4.5.1 (Release), Adobe Flex SDK 4.6 (Release)
>Reporter: Maurice Nicholson
>Assignee: Frédéric THOMAS
> Labels: patch, performance
> Attachments: FLEX-33273.patch, PerformanceTest.zip
>
>
> CSSCondition.matchesStyleClient() is called *very* frequently during layout
> of components in many different scenarios.
> I've done a lot of profiling of Flex apps and it comes up again and again.
> The current implementation is slow and creates unnecessary garbage (which
> slows down the runtime further, since it needs to collect the garbage instead
> of doing more useful things).
> Here is the current implementation:
> {code}
> public function matchesStyleClient(object:IAdvancedStyleClient):Boolean
> {
> var match:Boolean = false;
> if (kind == CSSConditionKind.CLASS)
> {
> if (object.styleName != null && object.styleName is String)
> {
> // Look for a match in a potential list of styleNames
> var styleNames:Array = object.styleName.split(/\s+/);
> for (var i:uint = 0; i < styleNames.length; i++)
> {
> if (styleNames[i] == value)
> {
> match = true;
> break;
> }
> }
> }
> }
> else if (kind == CSSConditionKind.ID)
> {
> if (object.id == value)
> match = true;
> }
> else if (kind == CSSConditionKind.PSEUDO)
> {
> if (object.matchesCSSState(value))
> match = true;
> }
> return match;
> }
> {code}
> Here is what I suggest instead:
> {code}
> public function matchesStyleClient(object:IAdvancedStyleClient):Boolean
> {
> var match:Boolean = false;
> if (kind == CSSConditionKind.CLASS)
> {
> const styleName:String = object.styleName as String;
> if (styleName)
> {
> // Look for a match in a potential list of styleNames
> FIND:
> {
> var index:int = styleName.indexOf(value);
> if (index == -1)
> {
> break FIND;
> }
> if (index != 0 && styleName.charAt(index - 1) != ' ')
> {
> break FIND;
> }
> const next:int = index + value.length;
> if (next != styleName.length && styleName.charAt(next) !=
> ' ')
> {
> break FIND;
> }
> match = true;
> }
> }
> }
> else if (kind == CSSConditionKind.ID)
> {
> if (object.id == value)
> match = true;
> }
> else if (kind == CSSConditionKind.PSEUDO)
> {
> if (object.matchesCSSState(value))
> match = true;
> }
> return match;
> }
> {code}
> There are obviously more concise ways to express this code, but the above
> seems to match the current style more or less.
> Here is the output from a benchmark I created using Grant Skinner's
> PerformanceTest v2 Beta, comparing the current version and the suggested
> version:
> {noformat}
> Comparing speed of matching a string in space delimited string. 100 loops.
> Test Old ms New
> ms Speedup Old mem New mem Change
> matchesStyleClient(styleName: "foo", value: "foo")1006.00
> 181.00 -82
[jira] [Commented] (FLEX-33273) CSSCondition.matchesStyleClient() is slow and creates excessive garbage
[
https://issues.apache.org/jira/browse/FLEX-33273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570921#comment-13570921
]
Justin Mclean commented on FLEX-33273:
--
Changes are made in the develop branch not trunk. It will show up in trunk only
after a release is made.
You can see the change here.
http://svn.apache.org/viewvc/incubator/flex/sdk/branches/develop/frameworks/projects/framework/src/mx/styles/CSSCondition.as?view=log&pathrev=1420855
> CSSCondition.matchesStyleClient() is slow and creates excessive garbage
> ---
>
> Key: FLEX-33273
> URL: https://issues.apache.org/jira/browse/FLEX-33273
> Project: Apache Flex
> Issue Type: Improvement
> Components: Styles
>Affects Versions: Adobe Flex SDK 4.1 (Release), Adobe Flex SDK 4.5
> (Release), Adobe Flex SDK 4.5.1 (Release), Adobe Flex SDK 4.6 (Release)
>Reporter: Maurice Nicholson
>Assignee: Frédéric THOMAS
> Labels: patch, performance
> Attachments: FLEX-33273.patch, PerformanceTest.zip
>
>
> CSSCondition.matchesStyleClient() is called *very* frequently during layout
> of components in many different scenarios.
> I've done a lot of profiling of Flex apps and it comes up again and again.
> The current implementation is slow and creates unnecessary garbage (which
> slows down the runtime further, since it needs to collect the garbage instead
> of doing more useful things).
> Here is the current implementation:
> {code}
> public function matchesStyleClient(object:IAdvancedStyleClient):Boolean
> {
> var match:Boolean = false;
> if (kind == CSSConditionKind.CLASS)
> {
> if (object.styleName != null && object.styleName is String)
> {
> // Look for a match in a potential list of styleNames
> var styleNames:Array = object.styleName.split(/\s+/);
> for (var i:uint = 0; i < styleNames.length; i++)
> {
> if (styleNames[i] == value)
> {
> match = true;
> break;
> }
> }
> }
> }
> else if (kind == CSSConditionKind.ID)
> {
> if (object.id == value)
> match = true;
> }
> else if (kind == CSSConditionKind.PSEUDO)
> {
> if (object.matchesCSSState(value))
> match = true;
> }
> return match;
> }
> {code}
> Here is what I suggest instead:
> {code}
> public function matchesStyleClient(object:IAdvancedStyleClient):Boolean
> {
> var match:Boolean = false;
> if (kind == CSSConditionKind.CLASS)
> {
> const styleName:String = object.styleName as String;
> if (styleName)
> {
> // Look for a match in a potential list of styleNames
> FIND:
> {
> var index:int = styleName.indexOf(value);
> if (index == -1)
> {
> break FIND;
> }
> if (index != 0 && styleName.charAt(index - 1) != ' ')
> {
> break FIND;
> }
> const next:int = index + value.length;
> if (next != styleName.length && styleName.charAt(next) !=
> ' ')
> {
> break FIND;
> }
> match = true;
> }
> }
> }
> else if (kind == CSSConditionKind.ID)
> {
> if (object.id == value)
> match = true;
> }
> else if (kind == CSSConditionKind.PSEUDO)
> {
> if (object.matchesCSSState(value))
> match = true;
> }
> return match;
> }
> {code}
> There are obviously more concise ways to express this code, but the above
> seems to match the current style more or less.
> Here is the output from a benchmark I created using Grant Skinner's
> PerformanceTest v2 Beta, comparing the current version and the suggested
> version:
> {noformat}
> Comparing speed of matching a string in space delimited string. 100 loops.
> Test
[jira] [Commented] (FLEX-33273) CSSCondition.matchesStyleClient() is slow and creates excessive garbage
[
https://issues.apache.org/jira/browse/FLEX-33273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570926#comment-13570926
]
RJ Camarillo commented on FLEX-33273:
-
Aha! Thanks Justin!
> CSSCondition.matchesStyleClient() is slow and creates excessive garbage
> ---
>
> Key: FLEX-33273
> URL: https://issues.apache.org/jira/browse/FLEX-33273
> Project: Apache Flex
> Issue Type: Improvement
> Components: Styles
>Affects Versions: Adobe Flex SDK 4.1 (Release), Adobe Flex SDK 4.5
> (Release), Adobe Flex SDK 4.5.1 (Release), Adobe Flex SDK 4.6 (Release)
>Reporter: Maurice Nicholson
>Assignee: Frédéric THOMAS
> Labels: patch, performance
> Attachments: FLEX-33273.patch, PerformanceTest.zip
>
>
> CSSCondition.matchesStyleClient() is called *very* frequently during layout
> of components in many different scenarios.
> I've done a lot of profiling of Flex apps and it comes up again and again.
> The current implementation is slow and creates unnecessary garbage (which
> slows down the runtime further, since it needs to collect the garbage instead
> of doing more useful things).
> Here is the current implementation:
> {code}
> public function matchesStyleClient(object:IAdvancedStyleClient):Boolean
> {
> var match:Boolean = false;
> if (kind == CSSConditionKind.CLASS)
> {
> if (object.styleName != null && object.styleName is String)
> {
> // Look for a match in a potential list of styleNames
> var styleNames:Array = object.styleName.split(/\s+/);
> for (var i:uint = 0; i < styleNames.length; i++)
> {
> if (styleNames[i] == value)
> {
> match = true;
> break;
> }
> }
> }
> }
> else if (kind == CSSConditionKind.ID)
> {
> if (object.id == value)
> match = true;
> }
> else if (kind == CSSConditionKind.PSEUDO)
> {
> if (object.matchesCSSState(value))
> match = true;
> }
> return match;
> }
> {code}
> Here is what I suggest instead:
> {code}
> public function matchesStyleClient(object:IAdvancedStyleClient):Boolean
> {
> var match:Boolean = false;
> if (kind == CSSConditionKind.CLASS)
> {
> const styleName:String = object.styleName as String;
> if (styleName)
> {
> // Look for a match in a potential list of styleNames
> FIND:
> {
> var index:int = styleName.indexOf(value);
> if (index == -1)
> {
> break FIND;
> }
> if (index != 0 && styleName.charAt(index - 1) != ' ')
> {
> break FIND;
> }
> const next:int = index + value.length;
> if (next != styleName.length && styleName.charAt(next) !=
> ' ')
> {
> break FIND;
> }
> match = true;
> }
> }
> }
> else if (kind == CSSConditionKind.ID)
> {
> if (object.id == value)
> match = true;
> }
> else if (kind == CSSConditionKind.PSEUDO)
> {
> if (object.matchesCSSState(value))
> match = true;
> }
> return match;
> }
> {code}
> There are obviously more concise ways to express this code, but the above
> seems to match the current style more or less.
> Here is the output from a benchmark I created using Grant Skinner's
> PerformanceTest v2 Beta, comparing the current version and the suggested
> version:
> {noformat}
> Comparing speed of matching a string in space delimited string. 100 loops.
> Test Old ms New
> ms Speedup Old mem New mem Change
> matchesStyleClient(styleName: "foo", value: "foo")1006.00
> 181.00 -82.0 123.00 0.00 -100.0
> matchesStyleCli
[jira] [Comment Edited] (FLEX-33273) CSSCondition.matchesStyleClient() is slow and creates excessive garbage
[
https://issues.apache.org/jira/browse/FLEX-33273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570926#comment-13570926
]
RJ Camarillo edited comment on FLEX-33273 at 2/5/13 4:10 AM:
-
Aha! Thanks Justin!
If you guys are interested, we also implemented our own changes to the
mx.style.* classes to improve performance in Flex 4.6. I'm currently
integrating this change to what we have and see how it goes. Anyhow, the
primarily idea is to inline function calls (not my original idea). We are aware
that this approach is anti-OO but in terms of performance, it does the job.
was (Author: rj.camarillo):
Aha! Thanks Justin!
> CSSCondition.matchesStyleClient() is slow and creates excessive garbage
> ---
>
> Key: FLEX-33273
> URL: https://issues.apache.org/jira/browse/FLEX-33273
> Project: Apache Flex
> Issue Type: Improvement
> Components: Styles
>Affects Versions: Adobe Flex SDK 4.1 (Release), Adobe Flex SDK 4.5
> (Release), Adobe Flex SDK 4.5.1 (Release), Adobe Flex SDK 4.6 (Release)
>Reporter: Maurice Nicholson
>Assignee: Frédéric THOMAS
> Labels: patch, performance
> Attachments: FLEX-33273.patch, PerformanceTest.zip
>
>
> CSSCondition.matchesStyleClient() is called *very* frequently during layout
> of components in many different scenarios.
> I've done a lot of profiling of Flex apps and it comes up again and again.
> The current implementation is slow and creates unnecessary garbage (which
> slows down the runtime further, since it needs to collect the garbage instead
> of doing more useful things).
> Here is the current implementation:
> {code}
> public function matchesStyleClient(object:IAdvancedStyleClient):Boolean
> {
> var match:Boolean = false;
> if (kind == CSSConditionKind.CLASS)
> {
> if (object.styleName != null && object.styleName is String)
> {
> // Look for a match in a potential list of styleNames
> var styleNames:Array = object.styleName.split(/\s+/);
> for (var i:uint = 0; i < styleNames.length; i++)
> {
> if (styleNames[i] == value)
> {
> match = true;
> break;
> }
> }
> }
> }
> else if (kind == CSSConditionKind.ID)
> {
> if (object.id == value)
> match = true;
> }
> else if (kind == CSSConditionKind.PSEUDO)
> {
> if (object.matchesCSSState(value))
> match = true;
> }
> return match;
> }
> {code}
> Here is what I suggest instead:
> {code}
> public function matchesStyleClient(object:IAdvancedStyleClient):Boolean
> {
> var match:Boolean = false;
> if (kind == CSSConditionKind.CLASS)
> {
> const styleName:String = object.styleName as String;
> if (styleName)
> {
> // Look for a match in a potential list of styleNames
> FIND:
> {
> var index:int = styleName.indexOf(value);
> if (index == -1)
> {
> break FIND;
> }
> if (index != 0 && styleName.charAt(index - 1) != ' ')
> {
> break FIND;
> }
> const next:int = index + value.length;
> if (next != styleName.length && styleName.charAt(next) !=
> ' ')
> {
> break FIND;
> }
> match = true;
> }
> }
> }
> else if (kind == CSSConditionKind.ID)
> {
> if (object.id == value)
> match = true;
> }
> else if (kind == CSSConditionKind.PSEUDO)
> {
> if (object.matchesCSSState(value))
> match = true;
> }
> return match;
> }
> {code}
> There are obviously more concise ways to express this code, but the above
> seems to match the current style more or less.
> Here is the output from a benchmark I created
[jira] [Updated] (FLEX-33366) The candidate input method can not follow
[ https://issues.apache.org/jira/browse/FLEX-33366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Harui updated FLEX-33366: -- Attachment: QQTextInputSkin.mxml QQTextAreaSkin.mxml QQSparkTextInput.as QQSparkTextArea.as IMETest.mxml Attempt at a workaround. it isn't perfect but might serve as a starting point for a better solution. IMETest is an example of how to set up the components and the skinclass. You should be able to also use CSS instead of assigning a skinclass to each instance. QQSparkTextArea and QQSparkTextInput must use QQTextAreaSkin and QQTextInputSkin. The custom skins have an extra TextField that is hidden behind the RichEditableText. When focus is assigned to the component, the TextField momentarily gets focus. The IME won't follow the cursor exactly, but hopefully it will be acceptable. QQTextAreaSkin is more complicated because the TextField needs to move vertically otherwise it will obscure the text being input. It attempts to watch the position of the blinking cursor and move the TextField under it. It may not work for complex selection and other scenarios. I think that's the best I can do for now. Hope it helps. > The candidate input method can not follow > - > > Key: FLEX-33366 > URL: https://issues.apache.org/jira/browse/FLEX-33366 > Project: Apache Flex > Issue Type: Bug > Components: Spark: TextArea, Spark: TextInput >Affects Versions: Apache Flex 4.8 (parity release) > Environment: windows,IE8 >Reporter: zy > Attachments: IMETest.mxml, IMETest.zip, QQSparkTextArea.as, > QQSparkTextInput.as, QQTextAreaSkin.mxml, QQTextInputSkin.mxml > > > The spark:TextArea and TextInput Chinese candidate input method can not > follow. > But mx:TextArea and TextInput not this issue. > I guess you only test the English input method, Chinese input methods all > have this problem, it is affecting the user experience. > you can test this Chinese input method.all chinese use this. > http://dl_dir.qq.com/invc/qqpinyin/QQPinyin_Setup_1.1.1224.400.exe > I made a picture to illustrate the problem. > http://img.my.csdn.net/uploads/201301/24/1359028348_2400.jpg > If you are unclear, please let me know. I don't know english.I am very sorry. > Thank you! -- 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-33273) CSSCondition.matchesStyleClient() is slow and creates excessive garbage
[
https://issues.apache.org/jira/browse/FLEX-33273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
RJ Camarillo updated FLEX-33273:
Attachment: mx.styles - inlined.zip
> CSSCondition.matchesStyleClient() is slow and creates excessive garbage
> ---
>
> Key: FLEX-33273
> URL: https://issues.apache.org/jira/browse/FLEX-33273
> Project: Apache Flex
> Issue Type: Improvement
> Components: Styles
>Affects Versions: Adobe Flex SDK 4.1 (Release), Adobe Flex SDK 4.5
> (Release), Adobe Flex SDK 4.5.1 (Release), Adobe Flex SDK 4.6 (Release)
>Reporter: Maurice Nicholson
>Assignee: Frédéric THOMAS
> Labels: patch, performance
> Attachments: FLEX-33273.patch, mx.styles - inlined.zip,
> PerformanceTest.zip
>
>
> CSSCondition.matchesStyleClient() is called *very* frequently during layout
> of components in many different scenarios.
> I've done a lot of profiling of Flex apps and it comes up again and again.
> The current implementation is slow and creates unnecessary garbage (which
> slows down the runtime further, since it needs to collect the garbage instead
> of doing more useful things).
> Here is the current implementation:
> {code}
> public function matchesStyleClient(object:IAdvancedStyleClient):Boolean
> {
> var match:Boolean = false;
> if (kind == CSSConditionKind.CLASS)
> {
> if (object.styleName != null && object.styleName is String)
> {
> // Look for a match in a potential list of styleNames
> var styleNames:Array = object.styleName.split(/\s+/);
> for (var i:uint = 0; i < styleNames.length; i++)
> {
> if (styleNames[i] == value)
> {
> match = true;
> break;
> }
> }
> }
> }
> else if (kind == CSSConditionKind.ID)
> {
> if (object.id == value)
> match = true;
> }
> else if (kind == CSSConditionKind.PSEUDO)
> {
> if (object.matchesCSSState(value))
> match = true;
> }
> return match;
> }
> {code}
> Here is what I suggest instead:
> {code}
> public function matchesStyleClient(object:IAdvancedStyleClient):Boolean
> {
> var match:Boolean = false;
> if (kind == CSSConditionKind.CLASS)
> {
> const styleName:String = object.styleName as String;
> if (styleName)
> {
> // Look for a match in a potential list of styleNames
> FIND:
> {
> var index:int = styleName.indexOf(value);
> if (index == -1)
> {
> break FIND;
> }
> if (index != 0 && styleName.charAt(index - 1) != ' ')
> {
> break FIND;
> }
> const next:int = index + value.length;
> if (next != styleName.length && styleName.charAt(next) !=
> ' ')
> {
> break FIND;
> }
> match = true;
> }
> }
> }
> else if (kind == CSSConditionKind.ID)
> {
> if (object.id == value)
> match = true;
> }
> else if (kind == CSSConditionKind.PSEUDO)
> {
> if (object.matchesCSSState(value))
> match = true;
> }
> return match;
> }
> {code}
> There are obviously more concise ways to express this code, but the above
> seems to match the current style more or less.
> Here is the output from a benchmark I created using Grant Skinner's
> PerformanceTest v2 Beta, comparing the current version and the suggested
> version:
> {noformat}
> Comparing speed of matching a string in space delimited string. 100 loops.
> Test Old ms New
> ms Speedup Old mem New mem Change
> matchesStyleClient(styleName: "foo", value: "foo")1006.00
> 181.00 -82.0 123.00 0.00 -100.0
> matchesStyleClient(styleName: "foo ba
[jira] [Commented] (FLEX-33382) Run Time Error 1009 in mx:Combobox in destoryDropdown
[ https://issues.apache.org/jira/browse/FLEX-33382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571227#comment-13571227 ] Vineet Bhatia commented on FLEX-33382: -- SVN revision should be 1442453 - http://svn.apache.org/viewvc/flex/sdk/branches/develop/frameworks/projects/mx/src/mx/controls/ComboBox.as?revision=1442453&view=co&pathrev=1442453 > Run Time Error 1009 in mx:Combobox in destoryDropdown > - > > Key: FLEX-33382 > URL: https://issues.apache.org/jira/browse/FLEX-33382 > Project: Apache Flex > Issue Type: Bug > Components: mx: ComboBox >Affects Versions: Adobe Flex SDK 4.6 (Release) >Reporter: Justin Mclean >Assignee: Justin Mclean >Priority: Minor > Fix For: Apache Flex 4.10.0 > > > Run Time Error 1009 in destroyDropdown(), occurs infrequently and not easy to > reproduce. > Sample stack trace (from 11.5 release player). > TypeError: Error #1009 > at mx.controls::ComboBox/destroyDropdown() > at mx.controls::ComboBox/removedFromStageHandler() > at > mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::$removeChild() > at mx.core::UIComponent/removeChild() > at mx.core::UIComponent/addChild() > at mx.controls::AdvancedDataGrid/addRendererToContentArea() > at mx.controls::AdvancedDataGrid/createHeaderItems() > at mx.controls::AdvancedDataGrid/createHeaders() > at > mx.controls.advancedDataGridClasses::AdvancedDataGridBase/makeRowsAndColumns() > at mx.controls::AdvancedDataGridBaseEx/makeRowsAndColumns() > at mx.controls::AdvancedDataGrid/makeRowsAndColumns() > at > mx.controls.listClasses::AdvancedListBase/makeRowsAndColumnsWithExtraRows() > at mx.controls.listClasses::AdvancedListBase/updateDisplayList() > at mx.controls::AdvancedDataGridBaseEx/updateDisplayList() > at mx.controls::AdvancedDataGrid/updateDisplayList() > at mx.controls.listClasses::AdvancedListBase/validateDisplayList() > at mx.managers::LayoutManager/validateDisplayList() > at mx.managers::LayoutManager/doPhasedInstantiation() > at mx.managers::LayoutManager/validateNow() > at mx.controls::ComboBox/displayDropdown() > at mx.controls::ComboBox/downArrowButton_buttonDownHandler() > at flash.events::EventDispatcher/dispatchEvent() > at mx.core::UIComponent/dispatchEvent() > at > mx.controls::Button/http://www.adobe.com/2006/flex/mx/internal::buttonPressed() > at mx.controls::Button/mouseDownHandler() > at flash.events::EventDispatcher/dispatchEvent() > at mx.core::UIComponent/dispatchEvent() > at mx.managers::SystemManager/mouseEventHandler() -- 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-33383) List is Flickering on mobile when different number of lines in message
Merten P. created FLEX-33383:
Summary: List is Flickering on mobile when different number of
lines in message
Key: FLEX-33383
URL: https://issues.apache.org/jira/browse/FLEX-33383
Project: Apache Flex
Issue Type: Bug
Components: Mobile: List
Affects Versions: Apache Flex 4.9.0
Reporter: Merten P.
On a List with an IconItemRenderer in it. When beginning to scroll on mobile,
the list is flickering on the first time (gets white for one frame). This only
happens when the messageField/messageFunction is set and there is a different
number of lines in the message areas.
Sample Code:
http://ns.adobe.com/mxml/2009";
xmlns:s="library://ns.adobe.com/flex/spark" title="HomeView">
Solution:
Either in the list component:
Or via Skinning:
package skins
{
import spark.layouts.HorizontalAlign;
import spark.layouts.VerticalLayout;
import spark.skins.mobile.ListSkin;
public class MyListSkin extends ListSkin
{
public function MyListSkin()
{
super();
}
//create children
override protected function createChildren():void
{
super.createChildren();
//change align on vertical layout
if(dataGroup && dataGroup.layout && dataGroup.layout is
VerticalLayout)
{
var layout:VerticalLayout = dataGroup.layout as VerticalLayout;
layout.horizontalAlign = HorizontalAlign.CONTENT_JUSTIFY;
}
}
}
}
with CSS:
s|List
{
skinClass: ClassReference("skins.MyListSkin");
horizontalScrollPolicy: off;
}
See:
http://stackoverflow.com/questions/10490117/flex-mobile-list-flickers/14714690
for more info
--
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-33384) Caret visible in all textinputs after they've been selected once.
Mikko Torniainen created FLEX-33384: --- Summary: Caret visible in all textinputs after they've been selected once. Key: FLEX-33384 URL: https://issues.apache.org/jira/browse/FLEX-33384 Project: Apache Flex Issue Type: Bug Components: Spark: TextArea Affects Versions: Apache Flex 4.9.0 Environment: Windows 7 64bit, verified on many different hardware configurations Reporter: Mikko Torniainen Caret will stay blinking on textinputs and textareas after they have been once visited (focused) and the parent component loses focus. To produce: Then for example switch to another application and back. Workaround is to switch back to 4.6 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] [Created] (FLEX-33385) titleText SkinPart in TitleBar is NOT Required but exception is thrown if not implemented.
Fabio Todaro created FLEX-33385:
---
Summary: titleText SkinPart in TitleBar is NOT Required but
exception is thrown if not implemented.
Key: FLEX-33385
URL: https://issues.apache.org/jira/browse/FLEX-33385
Project: Apache Flex
Issue Type: Improvement
Components: Spark: WindowedApplication
Affects Versions: Apache Flex 4.9.0
Reporter: Fabio Todaro
Original:
override protected function commitProperties():void
{
super.commitProperties();
if (titleChanged)
{
titleText.text = _title;
titleChanged = false;
}
if (titleIconChanged)
{
if (titleIconObject)
{
titleIconImage.source = null;
titleIconObject = null;
}
if (_titleIcon && titleIconImage)
{
titleIconObject = new _titleIcon();
titleIconImage.source = titleIconObject;
}
titleIconChanged = false;
}
}
Solution:
override protected function commitProperties():void
{
super.commitProperties();
if (titleChanged)
{
if(titleText)
{
titleText.text = _title;
titleChanged = false;
}
}
if (titleIconChanged)
{
if (titleIconObject)
{
titleIconImage.source = null;
titleIconObject = null;
}
if (_titleIcon && titleIconImage)
{
titleIconObject = new _titleIcon();
titleIconImage.source = titleIconObject;
}
titleIconChanged = false;
}
}
--
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-33383) List is Flickering on mobile when different number of lines in message
[
https://issues.apache.org/jira/browse/FLEX-33383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Merten P. updated FLEX-33383:
-
Description:
On a List with an IconItemRenderer in it. When beginning to scroll on mobile,
the list is flickering on the first time (gets white for one frame). This only
happens when the messageField/messageFunction is set and there is a different
number of lines in the message areas.
Sample Code:
http://ns.adobe.com/mxml/2009";
xmlns:s="library://ns.adobe.com/flex/spark" title="HomeView">
Workaround:
(Reset the layout in the initialize event)
http://ns.adobe.com/mxml/2009";
xmlns:s="library://ns.adobe.com/flex/spark"
initialize="initializeHandler(event)">
See:
http://stackoverflow.com/questions/10490117/flex-mobile-list-flickers/14714690
for more info
was:
On a List with an IconItemRenderer in it. When beginning to scroll on mobile,
the list is flickering on the first time (gets white for one frame). This only
happens when the messageField/messageFunction is set and there is a different
number of lines in the message areas.
Sample Code:
http://ns.adobe.com/mxml/2009";
xmlns:s="library://ns.adobe.com/flex/spark" title="HomeView">
Solution:
Either in the list component:
Or via Skinning:
package skins
{
import spark.layouts.HorizontalAlign;
import spark.layouts.VerticalLayout;
import spark.skins.mobile.ListSkin;
public class MyListSkin extends ListSkin
{
public function MyListSkin()
{
super();
}
//create children
override protected function createChildren():void
{
super.createChildren();
//change align on vertical layout
if(dataGroup && dataGroup.layout && dataGroup.layout is
VerticalLayout)
{
var layout:VerticalLayout = dataGroup.layout as VerticalLayout;
layout.horizontalAlign = HorizontalAlign.CONTENT_JUSTIFY;
}
}
}
}
with CSS:
s|List
{
skinClass: ClassReference("skins.MyListSkin");
horizontalScrollPolicy: off;
}
See:
http://stackoverflow.com/questions/10490117/flex-mobile-list-flickers/14714690
for more info
> List is Flickering on mobile when different number of lines in message
> --
>
> Key: FLEX-33383
> URL: https://issues.apache.org/jira/browse/FLEX-33383
> Project: Apache Flex
> Issue Type: Bug
> Components: Mobile: List
>Affects Versions: Apache Flex 4.9.0
>Reporter: Merten P.
> Labels: flicker, list, listskin, mobile, solution
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> On a List with an IconItemRenderer in it. When beginning to scroll on mobile,
> the list is flickering on the first time (gets white for one frame). This
> only happens when the messageField/messageFunction is set and there is a
> different number of lines in the message areas.
> Sample Code:
> http://ns.adobe.com/mxml/2009";
> xmlns:s="library://ns.adobe.com/flex/spark" title="HomeView">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Workaround:
> (Reset the layout in the initialize event)
> http://ns.adobe.com/mxml/2009";
> xmlns:s="library://ns.adobe.com/flex/spark"
> initialize="initializeHandler(event)">
>
>
>
>
> See:
> http://stackoverflow.com/questions/10490117/flex-mobile-list-flickers/14714690
> for more info
--
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-33383) List is Flickering on mobile when different number of lines in message
[ https://issues.apache.org/jira/browse/FLEX-33383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Merten P. updated FLEX-33383: - Description: On a List with an IconItemRenderer in it. When beginning to scroll on mobile, the list is flickering on the first time you scroll (gets white for one frame). This only happens when the messageField/messageFunction is set and there is a different number of lines in the message areas. Sample Code: http://ns.adobe.com/mxml/2009"; xmlns:s="library://ns.adobe.com/flex/spark" title="HomeView"> Workaround: (Reset the layout in the initialize event) http://ns.adobe.com/mxml/2009"; xmlns:s="library://ns.adobe.com/flex/spark" initialize="initializeHandler(event)"> See: http://stackoverflow.com/questions/10490117/flex-mobile-list-flickers/14714690 for more info was: On a List with an IconItemRenderer in it. When beginning to scroll on mobile, the list is flickering on the first time (gets white for one frame). This only happens when the messageField/messageFunction is set and there is a different number of lines in the message areas. Sample Code: http://ns.adobe.com/mxml/2009"; xmlns:s="library://ns.adobe.com/flex/spark" title="HomeView"> Workaround: (Reset the layout in the initialize event) http://ns.adobe.com/mxml/2009"; xmlns:s="library://ns.adobe.com/flex/spark" initialize="initializeHandler(event)"> See: http://stackoverflow.com/questions/10490117/flex-mobile-list-flickers/14714690 for more info > List is Flickering on mobile when different number of lines in message > -- > > Key: FLEX-33383 > URL: https://issues.apache.org/jira/browse/FLEX-33383 > Project: Apache Flex > Issue Type: Bug > Components: Mobile: List >Affects Versions: Apache Flex 4.9.0 >Reporter: Merten P. > Labels: flicker, list, listskin, mobile, solution > Original Estimate: 168h > Remaining Estimate: 168h > > On a List with an IconItemRenderer in it. When beginning to scroll on mobile, > the list is flickering on the first time you scroll (gets white for one > frame). This only happens when the messageField/messageFunction is set and > there is a different number of lines in the message areas. > Sample Code: > http://ns.adobe.com/mxml/2009"; > xmlns:s="library://ns.adobe.com/flex/spark" title="HomeView"> > > > > > > > > > > > > > > > Workaround: > (Reset the layout in the initialize event) > http://ns.adobe.com/mxml/2009"; > xmlns:s="library://ns.adobe.com/flex/spark" > initialize="initializeHandler(event)"> > > > > > See: > http://stackoverflow.com/questions/10490117/flex-mobile-list-flickers/14714690 > for more info -- 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-33366) The candidate input method can not follow
[ https://issues.apache.org/jira/browse/FLEX-33366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573196#comment-13573196 ] Alex Harui commented on FLEX-33366: --- I reviewed the code and don't see any obvious cause of a memory leak. Each text widget does use an additional TextField so your app will use more memory, but it shouldn't be that much. Does the simple test case show a memory leak, or is it some other scenario? How are you determining there is a leak, and what does the Flash Builder Profiler show? > The candidate input method can not follow > - > > Key: FLEX-33366 > URL: https://issues.apache.org/jira/browse/FLEX-33366 > Project: Apache Flex > Issue Type: Bug > Components: Spark: TextArea, Spark: TextInput >Affects Versions: Apache Flex 4.8 (parity release) > Environment: windows,IE8 >Reporter: zy > Attachments: IMETest.mxml, IMETest.zip, QQSparkTextArea.as, > QQSparkTextInput.as, QQTextAreaSkin.mxml, QQTextInputSkin.mxml > > > The spark:TextArea and TextInput Chinese candidate input method can not > follow. > But mx:TextArea and TextInput not this issue. > I guess you only test the English input method, Chinese input methods all > have this problem, it is affecting the user experience. > you can test this Chinese input method.all chinese use this. > http://dl_dir.qq.com/invc/qqpinyin/QQPinyin_Setup_1.1.1224.400.exe > I made a picture to illustrate the problem. > http://img.my.csdn.net/uploads/201301/24/1359028348_2400.jpg > If you are unclear, please let me know. I don't know english.I am very sorry. > Thank you! -- 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-33377) Focus can be transferred from a modal window to a non-modal window open in the background if clicked on some specific dimension of the non-modal window in the backgroun
[ https://issues.apache.org/jira/browse/FLEX-33377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573226#comment-13573226 ] Alex Harui commented on FLEX-33377: --- It appears that the transform.pixelBounds of the non-modal extends into negative coordinates (left == -2) and that causes it to be targetable at x=0. Probably a player bug or idiosyncracy. The modal window appears to be correctly sized and positioned. It appears to be safe to extend the size of the modal window by an extra pixel or maybe set a linestyle so a border extends out into negative coordinates. Most other code should be using stageWidth instead of stage.width so they shouldn't be affected by such a change. > Focus can be transferred from a modal window to a non-modal window open in > the background if clicked on some specific dimension of the non-modal window > in the background i.e. by clicking on the extreme left i.e. x=0 dimension of > the application. > - > > Key: FLEX-33377 > URL: https://issues.apache.org/jira/browse/FLEX-33377 > Project: Apache Flex > Issue Type: Bug > Components: mx: Window >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: Web application, flex SDK 4.6. and 4.9 > Flash player version: 11.5.502.146 > Mozilla firefox and IE >Reporter: rahul singh rawat >Priority: Minor > Attachments: Modal_mxTest.fxp, Modal_mxTest-MonkeyPatched.fxp > > > Focus can be transferred from a modal window to a non-modal window open in > the background if clicked ONLY on some specific dimension of the non-modal > window in the background i.e. by clicking on the extreme left i.e. x=0 > dimension of the application. Issue varies with flash player versions and > browser used. The non-modal window is coded to listen to a click event. > However it can be easily reproduced with any browser or flash player version > by setting the x dimension of the non-modal window between-10 to 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] [Commented] (FLEX-33377) Focus can be transferred from a modal window to a non-modal window open in the background if clicked on some specific dimension of the non-modal window in the backgroun
[ https://issues.apache.org/jira/browse/FLEX-33377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573628#comment-13573628 ] Alex Harui commented on FLEX-33377: --- I put a breakpoint in the app's down_handler. Then I examined various properties. I think there are other places in the code where folks want to know the visual size of the stage and use stageWidth/stageHeight (or systemManager.screen.width/height). There is centering logic, bounds for drag/drop, etc. I wanted to feel comfortable that if you extend the modal rectangle into negative coordinates that it would not affect that other logic. Doing so would definitely affect stage.width/height, but it appears that the other code uses stageWidth/stageHeight so will be unaffected, which is what we want. So yes, I think you can just extend the modal rectangle to -1, or maybe try adding a 1-pixel border instead (that might be a safer code change). I don't think you need to determine the actual bounds (the non-modal actually extends to -2 and something else is extending to -10). > Focus can be transferred from a modal window to a non-modal window open in > the background if clicked on some specific dimension of the non-modal window > in the background i.e. by clicking on the extreme left i.e. x=0 dimension of > the application. > - > > Key: FLEX-33377 > URL: https://issues.apache.org/jira/browse/FLEX-33377 > Project: Apache Flex > Issue Type: Bug > Components: mx: Window >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: Web application, flex SDK 4.6. and 4.9 > Flash player version: 11.5.502.146 > Mozilla firefox and IE >Reporter: rahul singh rawat >Priority: Minor > Attachments: Modal_mxTest.fxp, Modal_mxTest-MonkeyPatched.fxp > > > Focus can be transferred from a modal window to a non-modal window open in > the background if clicked ONLY on some specific dimension of the non-modal > window in the background i.e. by clicking on the extreme left i.e. x=0 > dimension of the application. Issue varies with flash player versions and > browser used. The non-modal window is coded to listen to a click event. > However it can be easily reproduced with any browser or flash player version > by setting the x dimension of the non-modal window between-10 to 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] [Commented] (FLEX-33377) Focus can be transferred from a modal window to a non-modal window open in the background if clicked on some specific dimension of the non-modal window in the backgroun
[ https://issues.apache.org/jira/browse/FLEX-33377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573828#comment-13573828 ] Alex Harui commented on FLEX-33377: --- I think you only need to do: g.clear(); g.beginFill(c, 100); g.lineStyle(1, c, 100, true); g.drawRect(screen.x, screen.y, screen.width, screen.height); g.endFill(); DrawRect should use the prevailing lineStyle, although you may want to verify the corners are square. The reason I thought this was simpler was because it was less likely you would make a mistake. For example, I think your proposal of g.drawRect(screen.x-1, screen.y-1, screen.width+1, screen.height+1) is incorrect. I think it should be: g.drawRect(screen.x-1, screen.y-1, screen.width+2, screen.height+2) because I think you need to overflow the right and bottom edges as well. So use either the lineStyle if the corners are square or width+2/height+2. > Focus can be transferred from a modal window to a non-modal window open in > the background if clicked on some specific dimension of the non-modal window > in the background i.e. by clicking on the extreme left i.e. x=0 dimension of > the application. > - > > Key: FLEX-33377 > URL: https://issues.apache.org/jira/browse/FLEX-33377 > Project: Apache Flex > Issue Type: Bug > Components: mx: Window >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: Web application, flex SDK 4.6. and 4.9 > Flash player version: 11.5.502.146 > Mozilla firefox and IE >Reporter: rahul singh rawat >Priority: Minor > Attachments: Modal_mxTest.fxp, Modal_mxTest-MonkeyPatched.fxp > > > Focus can be transferred from a modal window to a non-modal window open in > the background if clicked ONLY on some specific dimension of the non-modal > window in the background i.e. by clicking on the extreme left i.e. x=0 > dimension of the application. Issue varies with flash player versions and > browser used. The non-modal window is coded to listen to a click event. > However it can be easily reproduced with any browser or flash player version > by setting the x dimension of the non-modal window between-10 to 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] [Commented] (FLEX-33377) Focus can be transferred from a modal window to a non-modal window open in the background if clicked on some specific dimension of the non-modal window in the backgroun
[ https://issues.apache.org/jira/browse/FLEX-33377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573856#comment-13573856 ] Alex Harui commented on FLEX-33377: --- The corners of the screen are always square, but the line caps and joins that create the corners of a rectangular border don't have to be square. That's why lineStyle has so many parameters. I can never remember what the default is, and whether a single-pixel line degenerates to being effectively square. Somewhere in Adobe documentation or the internet is a picture of the difference between lines and fills. IIRC, lines are drawn on the true edge, so a single-pixel line is half-way in one pixel and half-way on the other, but fills go the edge of the pixel. If you take some graph paper, a fill fills up one or more squares on the graph paper, but a line is like taking a pen or brush that has the thickness of one of the squares and tracing down one of the lines on the graph paper. > Focus can be transferred from a modal window to a non-modal window open in > the background if clicked on some specific dimension of the non-modal window > in the background i.e. by clicking on the extreme left i.e. x=0 dimension of > the application. > - > > Key: FLEX-33377 > URL: https://issues.apache.org/jira/browse/FLEX-33377 > Project: Apache Flex > Issue Type: Bug > Components: mx: Window >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: Web application, flex SDK 4.6. and 4.9 > Flash player version: 11.5.502.146 > Mozilla firefox and IE >Reporter: rahul singh rawat >Priority: Minor > Attachments: Modal_mxTest.fxp, Modal_mxTest-MonkeyPatched.fxp > > > Focus can be transferred from a modal window to a non-modal window open in > the background if clicked ONLY on some specific dimension of the non-modal > window in the background i.e. by clicking on the extreme left i.e. x=0 > dimension of the application. Issue varies with flash player versions and > browser used. The non-modal window is coded to listen to a click event. > However it can be easily reproduced with any browser or flash player version > by setting the x dimension of the non-modal window between-10 to 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] [Commented] (FLEX-33377) Focus can be transferred from a modal window to a non-modal window open in the background if clicked on some specific dimension of the non-modal window in the backgroun
[ https://issues.apache.org/jira/browse/FLEX-33377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573859#comment-13573859 ] Alex Harui commented on FLEX-33377: --- I'm fine with your choice. ;-) > Focus can be transferred from a modal window to a non-modal window open in > the background if clicked on some specific dimension of the non-modal window > in the background i.e. by clicking on the extreme left i.e. x=0 dimension of > the application. > - > > Key: FLEX-33377 > URL: https://issues.apache.org/jira/browse/FLEX-33377 > Project: Apache Flex > Issue Type: Bug > Components: mx: Window >Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: Web application, flex SDK 4.6. and 4.9 > Flash player version: 11.5.502.146 > Mozilla firefox and IE >Reporter: rahul singh rawat >Priority: Minor > Attachments: Modal_mxTest.fxp, Modal_mxTest-MonkeyPatched.fxp > > > Focus can be transferred from a modal window to a non-modal window open in > the background if clicked ONLY on some specific dimension of the non-modal > window in the background i.e. by clicking on the extreme left i.e. x=0 > dimension of the application. Issue varies with flash player versions and > browser used. The non-modal window is coded to listen to a click event. > However it can be easily reproduced with any browser or flash player version > by setting the x dimension of the non-modal window between-10 to 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-33383) List is Flickering on mobile when different number of lines in message
[
https://issues.apache.org/jira/browse/FLEX-33383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Merten P. updated FLEX-33383:
-
Description:
On a List with an IconItemRenderer in it. When beginning to scroll on mobile,
the list is flickering on the first time you scroll (gets white for one frame).
This only happens when the messageField/messageFunction is set and there is a
different number of lines in the message areas.
Sample Code:
http://ns.adobe.com/mxml/2009";
xmlns:s="library://ns.adobe.com/flex/spark" title="HomeView">
Workaround:
I eventually found a workaround. Basically it's just faking a drag event when
the list dispatches the updateComplete event. This prevents the flickering when
the user first starts to scroll and since updateComplete is called before the
list is initially shown, there is no flickering at all. The positive side
effect is that every time you change to a view with this list in it or when the
list gets another data provider, the scroll bar is shown for a moment, so you
can guess how large the list is without touching it.
So here's the code. I use this list as a superclass for all of my lists:
import mx.events.FlexEvent;
import mx.events.TouchInteractionEvent;
import spark.components.List;
public class MyList extends List
{
public function MyList()
{
super();
//add event listeners
addEventListener(FlexEvent.UPDATE_COMPLETE, updateCompleteHandler);
}
//update complete
protected function updateCompleteHandler(event:FlexEvent):void
{
//fake touch start
fakeTouchEvent(TouchInteractionEvent.TOUCH_INTERACTION_START);
callLater(endTouch);
}
//quit touch event
protected function endTouch():void {
//fake touch end
fakeTouchEvent(TouchInteractionEvent.TOUCH_INTERACTION_END);
}
//fake touch event
protected function fakeTouchEvent(type:String):void {
var evt:TouchInteractionEvent = new TouchInteractionEvent(type);
evt.relatedObject = scroller;
scroller.dispatchEvent(evt);
}
}
See:
http://stackoverflow.com/questions/10490117/flex-mobile-list-flickers/14714690
for more info
was:
On a List with an IconItemRenderer in it. When beginning to scroll on mobile,
the list is flickering on the first time you scroll (gets white for one frame).
This only happens when the messageField/messageFunction is set and there is a
different number of lines in the message areas.
Sample Code:
http://ns.adobe.com/mxml/2009";
xmlns:s="library://ns.adobe.com/flex/spark" title="HomeView">
Workaround:
(Reset the layout in the initialize event)
http://ns.adobe.com/mxml/2009";
xmlns:s="library://ns.adobe.com/flex/spark"
initialize="initializeHandler(event)">
See:
http://stackoverflow.com/questions/10490117/flex-mobile-list-flickers/14714690
for more info
> List is Flickering on mobile when different number of lines in message
> --
>
> Key: FLEX-33383
> URL: https://issues.apache.org/jira/browse/FLEX-33383
> Project: Apache Flex
> Issue Type: Bug
> Components: Mobile: List
>Affects Versions: Apache Flex 4.9.0
>Reporter: Merten P.
> Labels: flicker, list, listskin, mobile, solution
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> On a List with an IconItemRenderer in it. When beginning to scroll on mobile,
> the list is flickering on the first time you scroll (gets white for one
> frame). This only happens when the messageField/messageFunction is set and
> there is a different number of lines in the message areas.
> Sample Code:
> http://ns.adobe.com/mxml/2009";
> xmlns:s="library://ns.adobe.com/flex/spark" title="HomeView">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Workaround:
> I eventually found a workaround. Basically it's just faking a drag event when
> the list dispatches the updateComplete event. This prevents the flickering
> when the user first starts to scroll and since updateComplete is called
> before the list is initially shown, there is no flickering at all. The
> positive side effect is that every time you change to a view with this list
> in it or whe
[jira] [Created] (FLEX-33386) Style Declaration Matching Tuning - Inlining
RJ Camarillo created FLEX-33386: --- Summary: Style Declaration Matching Tuning - Inlining Key: FLEX-33386 URL: https://issues.apache.org/jira/browse/FLEX-33386 Project: Apache Flex Issue Type: Improvement Components: Styles Reporter: RJ Camarillo Priority: Minor Fix For: Adobe Flex SDK Next Attachments: mx.styles - inlined.zip One of the most executed calls during the lifetime of a Flex UIComponent is the matching of style declarations. As such, it is one that the community has monkey-patched often in order to attain speed-ups even for just a little. This is one of the things done to achieve that end. Instead of doing functional calls to the different style classes (i.e. CSSCondition, CSSSelector, CSSStyleDeclaration), the StyleProtoChain class has been modified to perform matching inline as much as possible. -- 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-33386) Style Declaration Matching Tuning - Inlining
[ https://issues.apache.org/jira/browse/FLEX-33386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RJ Camarillo updated FLEX-33386: Attachment: mx.styles - inlined.zip > Style Declaration Matching Tuning - Inlining > > > Key: FLEX-33386 > URL: https://issues.apache.org/jira/browse/FLEX-33386 > Project: Apache Flex > Issue Type: Improvement > Components: Styles >Reporter: RJ Camarillo >Priority: Minor > Labels: Performance > Fix For: Adobe Flex SDK Next > > Attachments: mx.styles - inlined.zip > > > One of the most executed calls during the lifetime of a Flex UIComponent is > the matching of style declarations. > As such, it is one that the community has monkey-patched often in order to > attain speed-ups even for just a little. > This is one of the things done to achieve that end. Instead of doing > functional calls to the different style classes (i.e. CSSCondition, > CSSSelector, CSSStyleDeclaration), the StyleProtoChain class has been > modified to perform matching inline as much as possible. -- 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-33273) CSSCondition.matchesStyleClient() is slow and creates excessive garbage
[
https://issues.apache.org/jira/browse/FLEX-33273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574123#comment-13574123
]
RJ Camarillo commented on FLEX-33273:
-
FLEX-33273 has been created in order to consider this idea.
> CSSCondition.matchesStyleClient() is slow and creates excessive garbage
> ---
>
> Key: FLEX-33273
> URL: https://issues.apache.org/jira/browse/FLEX-33273
> Project: Apache Flex
> Issue Type: Improvement
> Components: Styles
>Affects Versions: Adobe Flex SDK 4.1 (Release), Adobe Flex SDK 4.5
> (Release), Adobe Flex SDK 4.5.1 (Release), Adobe Flex SDK 4.6 (Release)
>Reporter: Maurice Nicholson
>Assignee: Frédéric THOMAS
> Labels: patch, performance
> Attachments: FLEX-33273.patch, mx.styles - inlined.zip,
> PerformanceTest.zip
>
>
> CSSCondition.matchesStyleClient() is called *very* frequently during layout
> of components in many different scenarios.
> I've done a lot of profiling of Flex apps and it comes up again and again.
> The current implementation is slow and creates unnecessary garbage (which
> slows down the runtime further, since it needs to collect the garbage instead
> of doing more useful things).
> Here is the current implementation:
> {code}
> public function matchesStyleClient(object:IAdvancedStyleClient):Boolean
> {
> var match:Boolean = false;
> if (kind == CSSConditionKind.CLASS)
> {
> if (object.styleName != null && object.styleName is String)
> {
> // Look for a match in a potential list of styleNames
> var styleNames:Array = object.styleName.split(/\s+/);
> for (var i:uint = 0; i < styleNames.length; i++)
> {
> if (styleNames[i] == value)
> {
> match = true;
> break;
> }
> }
> }
> }
> else if (kind == CSSConditionKind.ID)
> {
> if (object.id == value)
> match = true;
> }
> else if (kind == CSSConditionKind.PSEUDO)
> {
> if (object.matchesCSSState(value))
> match = true;
> }
> return match;
> }
> {code}
> Here is what I suggest instead:
> {code}
> public function matchesStyleClient(object:IAdvancedStyleClient):Boolean
> {
> var match:Boolean = false;
> if (kind == CSSConditionKind.CLASS)
> {
> const styleName:String = object.styleName as String;
> if (styleName)
> {
> // Look for a match in a potential list of styleNames
> FIND:
> {
> var index:int = styleName.indexOf(value);
> if (index == -1)
> {
> break FIND;
> }
> if (index != 0 && styleName.charAt(index - 1) != ' ')
> {
> break FIND;
> }
> const next:int = index + value.length;
> if (next != styleName.length && styleName.charAt(next) !=
> ' ')
> {
> break FIND;
> }
> match = true;
> }
> }
> }
> else if (kind == CSSConditionKind.ID)
> {
> if (object.id == value)
> match = true;
> }
> else if (kind == CSSConditionKind.PSEUDO)
> {
> if (object.matchesCSSState(value))
> match = true;
> }
> return match;
> }
> {code}
> There are obviously more concise ways to express this code, but the above
> seems to match the current style more or less.
> Here is the output from a benchmark I created using Grant Skinner's
> PerformanceTest v2 Beta, comparing the current version and the suggested
> version:
> {noformat}
> Comparing speed of matching a string in space delimited string. 100 loops.
> Test Old ms New
> ms Speedup Old mem New mem Change
> matchesStyleClient(styleName: "foo", value: "foo")1006.00
[jira] [Comment Edited] (FLEX-33273) CSSCondition.matchesStyleClient() is slow and creates excessive garbage
[
https://issues.apache.org/jira/browse/FLEX-33273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574123#comment-13574123
]
RJ Camarillo edited comment on FLEX-33273 at 2/8/13 1:03 AM:
-
FLEX-33386 has been created in order to consider this idea.
was (Author: rj.camarillo):
FLEX-33273 has been created in order to consider this idea.
> CSSCondition.matchesStyleClient() is slow and creates excessive garbage
> ---
>
> Key: FLEX-33273
> URL: https://issues.apache.org/jira/browse/FLEX-33273
> Project: Apache Flex
> Issue Type: Improvement
> Components: Styles
>Affects Versions: Adobe Flex SDK 4.1 (Release), Adobe Flex SDK 4.5
> (Release), Adobe Flex SDK 4.5.1 (Release), Adobe Flex SDK 4.6 (Release)
>Reporter: Maurice Nicholson
>Assignee: Frédéric THOMAS
> Labels: patch, performance
> Attachments: FLEX-33273.patch, mx.styles - inlined.zip,
> PerformanceTest.zip
>
>
> CSSCondition.matchesStyleClient() is called *very* frequently during layout
> of components in many different scenarios.
> I've done a lot of profiling of Flex apps and it comes up again and again.
> The current implementation is slow and creates unnecessary garbage (which
> slows down the runtime further, since it needs to collect the garbage instead
> of doing more useful things).
> Here is the current implementation:
> {code}
> public function matchesStyleClient(object:IAdvancedStyleClient):Boolean
> {
> var match:Boolean = false;
> if (kind == CSSConditionKind.CLASS)
> {
> if (object.styleName != null && object.styleName is String)
> {
> // Look for a match in a potential list of styleNames
> var styleNames:Array = object.styleName.split(/\s+/);
> for (var i:uint = 0; i < styleNames.length; i++)
> {
> if (styleNames[i] == value)
> {
> match = true;
> break;
> }
> }
> }
> }
> else if (kind == CSSConditionKind.ID)
> {
> if (object.id == value)
> match = true;
> }
> else if (kind == CSSConditionKind.PSEUDO)
> {
> if (object.matchesCSSState(value))
> match = true;
> }
> return match;
> }
> {code}
> Here is what I suggest instead:
> {code}
> public function matchesStyleClient(object:IAdvancedStyleClient):Boolean
> {
> var match:Boolean = false;
> if (kind == CSSConditionKind.CLASS)
> {
> const styleName:String = object.styleName as String;
> if (styleName)
> {
> // Look for a match in a potential list of styleNames
> FIND:
> {
> var index:int = styleName.indexOf(value);
> if (index == -1)
> {
> break FIND;
> }
> if (index != 0 && styleName.charAt(index - 1) != ' ')
> {
> break FIND;
> }
> const next:int = index + value.length;
> if (next != styleName.length && styleName.charAt(next) !=
> ' ')
> {
> break FIND;
> }
> match = true;
> }
> }
> }
> else if (kind == CSSConditionKind.ID)
> {
> if (object.id == value)
> match = true;
> }
> else if (kind == CSSConditionKind.PSEUDO)
> {
> if (object.matchesCSSState(value))
> match = true;
> }
> return match;
> }
> {code}
> There are obviously more concise ways to express this code, but the above
> seems to match the current style more or less.
> Here is the output from a benchmark I created using Grant Skinner's
> PerformanceTest v2 Beta, comparing the current version and the suggested
> version:
> {noformat}
> Comparing speed of matching a string in space delimited string. 100 loops.
> Test
[jira] [Updated] (FLEX-33386) Style Declaration Matching Tuning - Inlining
[ https://issues.apache.org/jira/browse/FLEX-33386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RJ Camarillo updated FLEX-33386: Description: One of the most executed calls during the lifetime of a Flex UIComponent is the matching of style declarations (i.e. state change, component initialization, etc). As such, it is one that the community has monkey-patched often in order to attain speed-ups even for just a little. This is one of the things done to achieve that end. Instead of doing functional calls to the different style classes (i.e. CSSCondition, CSSSelector, CSSStyleDeclaration), the StyleProtoChain class has been modified to perform matching inline as much as possible. was: One of the most executed calls during the lifetime of a Flex UIComponent is the matching of style declarations. As such, it is one that the community has monkey-patched often in order to attain speed-ups even for just a little. This is one of the things done to achieve that end. Instead of doing functional calls to the different style classes (i.e. CSSCondition, CSSSelector, CSSStyleDeclaration), the StyleProtoChain class has been modified to perform matching inline as much as possible. > Style Declaration Matching Tuning - Inlining > > > Key: FLEX-33386 > URL: https://issues.apache.org/jira/browse/FLEX-33386 > Project: Apache Flex > Issue Type: Improvement > Components: Styles >Reporter: RJ Camarillo >Priority: Minor > Labels: Performance > Fix For: Adobe Flex SDK Next > > Attachments: mx.styles - inlined.zip > > > One of the most executed calls during the lifetime of a Flex UIComponent is > the matching of style declarations (i.e. state change, component > initialization, etc). > As such, it is one that the community has monkey-patched often in order to > attain speed-ups even for just a little. > This is one of the things done to achieve that end. Instead of doing > functional calls to the different style classes (i.e. CSSCondition, > CSSSelector, CSSStyleDeclaration), the StyleProtoChain class has been > modified to perform matching inline as much as possible. -- 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-33386) Style Declaration Matching Tuning - Inlining
[ https://issues.apache.org/jira/browse/FLEX-33386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574126#comment-13574126 ] RJ Camarillo commented on FLEX-33386: - I attached the sources for now since I don't have a workspace setup for Apache Flex in order to export a patch. Apologies. > Style Declaration Matching Tuning - Inlining > > > Key: FLEX-33386 > URL: https://issues.apache.org/jira/browse/FLEX-33386 > Project: Apache Flex > Issue Type: Improvement > Components: Styles >Reporter: RJ Camarillo >Priority: Minor > Labels: Performance > Fix For: Adobe Flex SDK Next > > Attachments: mx.styles - inlined.zip > > > One of the most executed calls during the lifetime of a Flex UIComponent is > the matching of style declarations (i.e. state change, component > initialization, etc). > As such, it is one that the community has monkey-patched often in order to > attain speed-ups even for just a little. > This is one of the things done to achieve that end. Instead of doing > functional calls to the different style classes (i.e. CSSCondition, > CSSSelector, CSSStyleDeclaration), the StyleProtoChain class has been > modified to perform matching inline as much as possible. -- 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-33386) Style Declaration Matching Tuning - Inlining
[ https://issues.apache.org/jira/browse/FLEX-33386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RJ Camarillo updated FLEX-33386: Description: One of the most executed calls during the lifetime of a Flex UIComponent is the matching of style declarations (i.e. state change, component initialization, etc). As such, it is one that the community has monkey-patched often in order to attain speed-ups even for just a little. This is one of the improvements done to achieve that end. Instead of doing method calls to the different style classes (i.e. CSSCondition, CSSSelector, CSSStyleDeclaration), the StyleProtoChain class has been modified to perform matching inline as much as possible. The implementation is not perfect and I'm sure it can be improved further with the help of the bigger community. was: One of the most executed calls during the lifetime of a Flex UIComponent is the matching of style declarations (i.e. state change, component initialization, etc). As such, it is one that the community has monkey-patched often in order to attain speed-ups even for just a little. This is one of the things done to achieve that end. Instead of doing functional calls to the different style classes (i.e. CSSCondition, CSSSelector, CSSStyleDeclaration), the StyleProtoChain class has been modified to perform matching inline as much as possible. > Style Declaration Matching Tuning - Inlining > > > Key: FLEX-33386 > URL: https://issues.apache.org/jira/browse/FLEX-33386 > Project: Apache Flex > Issue Type: Improvement > Components: Styles >Reporter: RJ Camarillo >Priority: Minor > Labels: Performance > Fix For: Adobe Flex SDK Next > > Attachments: mx.styles - inlined.zip > > > One of the most executed calls during the lifetime of a Flex UIComponent is > the matching of style declarations (i.e. state change, component > initialization, etc). > As such, it is one that the community has monkey-patched often in order to > attain speed-ups even for just a little. > This is one of the improvements done to achieve that end. Instead of doing > method calls to the different style classes (i.e. CSSCondition, CSSSelector, > CSSStyleDeclaration), the StyleProtoChain class has been modified to perform > matching inline as much as possible. > The implementation is not perfect and I'm sure it can be improved further > with the help of the bigger community. -- 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-33386) Style Declaration Matching Tuning - Inlining
[
https://issues.apache.org/jira/browse/FLEX-33386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
RJ Camarillo updated FLEX-33386:
Description:
One of the most executed calls during the lifetime of a Flex UIComponent is the
matching of style declarations (i.e. state change, component initialization,
etc).
As such, it is one that the community has monkey-patched often in order to
attain speed-ups even for just a little.
This is one of the improvements done to achieve that end. Instead of doing
method calls to the different style classes (i.e. CSSCondition, CSSSelector,
CSSStyleDeclaration), the StyleProtoChain class has been modified to perform
matching inline as much as possible.
The implementation is not perfect and I'm sure it can be improved further with
the help of the bigger community. For example, the
matchingDecls.sortOn("selectorIndex", Array.NUMERIC) call could be improve to
use one of the faster sort algorithms out there. There are also some methods
calls that are not inlined.
was:
One of the most executed calls during the lifetime of a Flex UIComponent is the
matching of style declarations (i.e. state change, component initialization,
etc).
As such, it is one that the community has monkey-patched often in order to
attain speed-ups even for just a little.
This is one of the improvements done to achieve that end. Instead of doing
method calls to the different style classes (i.e. CSSCondition, CSSSelector,
CSSStyleDeclaration), the StyleProtoChain class has been modified to perform
matching inline as much as possible.
The implementation is not perfect and I'm sure it can be improved further with
the help of the bigger community.
> Style Declaration Matching Tuning - Inlining
>
>
> Key: FLEX-33386
> URL: https://issues.apache.org/jira/browse/FLEX-33386
> Project: Apache Flex
> Issue Type: Improvement
> Components: Styles
>Reporter: RJ Camarillo
>Priority: Minor
> Labels: Performance
> Fix For: Adobe Flex SDK Next
>
> Attachments: mx.styles - inlined.zip
>
>
> One of the most executed calls during the lifetime of a Flex UIComponent is
> the matching of style declarations (i.e. state change, component
> initialization, etc).
> As such, it is one that the community has monkey-patched often in order to
> attain speed-ups even for just a little.
> This is one of the improvements done to achieve that end. Instead of doing
> method calls to the different style classes (i.e. CSSCondition, CSSSelector,
> CSSStyleDeclaration), the StyleProtoChain class has been modified to perform
> matching inline as much as possible.
> The implementation is not perfect and I'm sure it can be improved further
> with the help of the bigger community. For example, the
> matchingDecls.sortOn("selectorIndex", Array.NUMERIC) call could be improve to
> use one of the faster sort algorithms out there. There are also some methods
> calls that are not inlined.
--
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-33388) TLF Error
Robbyn Gerhardt created FLEX-33388: -- Summary: TLF Error Key: FLEX-33388 URL: https://issues.apache.org/jira/browse/FLEX-33388 Project: Apache Flex Issue Type: Bug Components: Spark: TextArea Affects Versions: Apache Flex 4.9.0 Environment: Win 7 processor: Intel(R) Xeon(R) 2.40 GHz 6GB RAM Reporter: Robbyn Gerhardt When you paste text flow will get this error: TypeError: Error #1009: Cannot access a property or method of a null object reference. at flashx.textLayout.container::TextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:583] at spark.components.supportClasses::RichEditableTextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:347] at flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:763] at spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] at flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:772] at spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] at spark.components::RichEditableText/commitProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/RichEditableText.as:2561] at mx.core::UIComponent/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/core/UIComponent.as:8227] at mx.managers::LayoutManager/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:605] at mx.managers::LayoutManager/doPhasedInstantiation()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:821] at mx.managers::LayoutManager/doPhasedInstantiationCallback()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:1188] -- 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-33388) Add TextFlow to TextArea - Error
[ https://issues.apache.org/jira/browse/FLEX-33388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbyn Gerhardt updated FLEX-33388: --- Summary: Add TextFlow to TextArea - Error (was: TLF Error) > Add TextFlow to TextArea - Error > > > Key: FLEX-33388 > URL: https://issues.apache.org/jira/browse/FLEX-33388 > Project: Apache Flex > Issue Type: Bug > Components: Spark: TextArea >Affects Versions: Apache Flex 4.9.0 > Environment: Win 7 > processor: Intel(R) Xeon(R) 2.40 GHz > 6GB RAM >Reporter: Robbyn Gerhardt > > When you paste text flow will get this error: > TypeError: Error #1009: Cannot access a property or method of a null object > reference. > at > flashx.textLayout.container::TextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:583] > at > spark.components.supportClasses::RichEditableTextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:347] > at > flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:763] > at > spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] > at > flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:772] > at > spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] > at > spark.components::RichEditableText/commitProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/RichEditableText.as:2561] > at > mx.core::UIComponent/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/core/UIComponent.as:8227] > at > mx.managers::LayoutManager/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:605] > at > mx.managers::LayoutManager/doPhasedInstantiation()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:821] > at > mx.managers::LayoutManager/doPhasedInstantiationCallback()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:1188] -- 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-33388) Add TextFlow to TextArea - Error
[ https://issues.apache.org/jira/browse/FLEX-33388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbyn Gerhardt updated FLEX-33388: --- Labels: TLF TextArea textFlow (was: ) > Add TextFlow to TextArea - Error > > > Key: FLEX-33388 > URL: https://issues.apache.org/jira/browse/FLEX-33388 > Project: Apache Flex > Issue Type: Bug > Components: Spark: TextArea >Affects Versions: Apache Flex 4.9.0 > Environment: Win 7 > processor: Intel(R) Xeon(R) 2.40 GHz > 6GB RAM >Reporter: Robbyn Gerhardt > Labels: TLF, TextArea, textFlow > > When you paste text flow will get this error: > TypeError: Error #1009: Cannot access a property or method of a null object > reference. > at > flashx.textLayout.container::TextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:583] > at > spark.components.supportClasses::RichEditableTextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:347] > at > flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:763] > at > spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] > at > flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:772] > at > spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] > at > spark.components::RichEditableText/commitProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/RichEditableText.as:2561] > at > mx.core::UIComponent/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/core/UIComponent.as:8227] > at > mx.managers::LayoutManager/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:605] > at > mx.managers::LayoutManager/doPhasedInstantiation()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:821] > at > mx.managers::LayoutManager/doPhasedInstantiationCallback()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:1188] -- 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-33388) Add TextFlow to TextArea - Error
[ https://issues.apache.org/jira/browse/FLEX-33388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbyn Gerhardt updated FLEX-33388: --- Description: When you paste text flow will get this error: TypeError: Error #1009: Cannot access a property or method of a null object reference. at flashx.textLayout.container::TextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:583] at spark.components.supportClasses::RichEditableTextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:347] at flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:763] at spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] at flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:772] at spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] at spark.components::RichEditableText/commitProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/RichEditableText.as:2561] at mx.core::UIComponent/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/core/UIComponent.as:8227] at mx.managers::LayoutManager/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:605] at mx.managers::LayoutManager/doPhasedInstantiation()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:821] at mx.managers::LayoutManager/doPhasedInstantiationCallback()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:1188] I use TLF 3.0.33 in Apache Flex 4.9.0 In version Apache Flex 4.8.0 it works without problems. was: When you paste text flow will get this error: TypeError: Error #1009: Cannot access a property or method of a null object reference. at flashx.textLayout.container::TextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:583] at spark.components.supportClasses::RichEditableTextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:347] at flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:763] at spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] at flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:772] at spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] at spark.components::RichEditableText/commitProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/RichEditableText.as:2561] at mx.core::UIComponent/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/core/UIComponent.as:8227] at mx.managers::LayoutManager/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:605] at mx.managers::LayoutManager/doPhasedInstantiation()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:821] at mx.managers::LayoutManager/doPhasedInstantiationCallback()[/Users/justinmclean/Documents
[jira] [Created] (FLEX-33389) The width of the last column header on a horizontally scrolling datagrid
Mikko Torniainen created FLEX-33389: --- Summary: The width of the last column header on a horizontally scrolling datagrid Key: FLEX-33389 URL: https://issues.apache.org/jira/browse/FLEX-33389 Project: Apache Flex Issue Type: Bug Components: Spark: DataGrid Affects Versions: Apache Flex 4.9.0, Adobe Flex SDK 4.6 (Release) Environment: Windows 7 64bit Reporter: Mikko Torniainen Priority: Minor To reproduce: Create a spark datagrid with more columns than fit in the width of the datagrid. A horizontal scrollbar is shown. You'll see the last column header will wrap when it's scolled in and out of view. It's width changes based on how much of it is visible all the way down to zero. The other columns do not do that. Setting minwidth does not change it. -- 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-33388) Add TextFlow to TextArea - Error
[ https://issues.apache.org/jira/browse/FLEX-33388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbyn Gerhardt updated FLEX-33388: --- Labels: AIR TLF TextArea textFlow (was: TLF TextArea textFlow) > Add TextFlow to TextArea - Error > > > Key: FLEX-33388 > URL: https://issues.apache.org/jira/browse/FLEX-33388 > Project: Apache Flex > Issue Type: Bug > Components: Spark: TextArea >Affects Versions: Apache Flex 4.9.0 > Environment: Win 7 > processor: Intel(R) Xeon(R) 2.40 GHz > 6GB RAM >Reporter: Robbyn Gerhardt > Labels: AIR, TLF, TextArea, textFlow > > When you paste text flow will get this error: > TypeError: Error #1009: Cannot access a property or method of a null object > reference. > at > flashx.textLayout.container::TextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:583] > at > spark.components.supportClasses::RichEditableTextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:347] > at > flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:763] > at > spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] > at > flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:772] > at > spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] > at > spark.components::RichEditableText/commitProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/RichEditableText.as:2561] > at > mx.core::UIComponent/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/core/UIComponent.as:8227] > at > mx.managers::LayoutManager/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:605] > at > mx.managers::LayoutManager/doPhasedInstantiation()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:821] > at > mx.managers::LayoutManager/doPhasedInstantiationCallback()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:1188] > I use TLF 3.0.33 in Apache Flex 4.9.0 > In version Apache Flex 4.8.0 it works without problems. -- 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-33388) Add TextFlow to TextArea - Error
[ https://issues.apache.org/jira/browse/FLEX-33388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbyn Gerhardt updated FLEX-33388: --- Environment: Win 7 Intel(R) Xeon(R) 2.40 GHz 6GB RAM was: Win 7 processor: Intel(R) Xeon(R) 2.40 GHz 6GB RAM > Add TextFlow to TextArea - Error > > > Key: FLEX-33388 > URL: https://issues.apache.org/jira/browse/FLEX-33388 > Project: Apache Flex > Issue Type: Bug > Components: Spark: TextArea >Affects Versions: Apache Flex 4.9.0 > Environment: Win 7 > Intel(R) Xeon(R) 2.40 GHz > 6GB RAM >Reporter: Robbyn Gerhardt > Labels: AIR, TLF, TextArea, textFlow > > When you paste text flow will get this error: > TypeError: Error #1009: Cannot access a property or method of a null object > reference. > at > flashx.textLayout.container::TextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:583] > at > spark.components.supportClasses::RichEditableTextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:347] > at > flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:763] > at > spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] > at > flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:772] > at > spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] > at > spark.components::RichEditableText/commitProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/RichEditableText.as:2561] > at > mx.core::UIComponent/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/core/UIComponent.as:8227] > at > mx.managers::LayoutManager/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:605] > at > mx.managers::LayoutManager/doPhasedInstantiation()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:821] > at > mx.managers::LayoutManager/doPhasedInstantiationCallback()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:1188] > I use TLF 3.0.33 in Apache Flex 4.9.0 > In version Apache Flex 4.8.0 it works without problems. -- 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-33388) Add TextFlow to TextArea - Error
[ https://issues.apache.org/jira/browse/FLEX-33388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Harui resolved FLEX-33388. --- Resolution: Incomplete Please provide a simple test case. > Add TextFlow to TextArea - Error > > > Key: FLEX-33388 > URL: https://issues.apache.org/jira/browse/FLEX-33388 > Project: Apache Flex > Issue Type: Bug > Components: Spark: TextArea >Affects Versions: Apache Flex 4.9.0 > Environment: Win 7 > Intel(R) Xeon(R) 2.40 GHz > 6GB RAM >Reporter: Robbyn Gerhardt > Labels: AIR, TLF, TextArea, textFlow > > When you paste text flow will get this error: > TypeError: Error #1009: Cannot access a property or method of a null object > reference. > at > flashx.textLayout.container::TextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:583] > at > spark.components.supportClasses::RichEditableTextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:347] > at > flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:763] > at > spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] > at > flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:772] > at > spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] > at > spark.components::RichEditableText/commitProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/RichEditableText.as:2561] > at > mx.core::UIComponent/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/core/UIComponent.as:8227] > at > mx.managers::LayoutManager/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:605] > at > mx.managers::LayoutManager/doPhasedInstantiation()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:821] > at > mx.managers::LayoutManager/doPhasedInstantiationCallback()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:1188] > I use TLF 3.0.33 in Apache Flex 4.9.0 > In version Apache Flex 4.8.0 it works without problems. -- 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-33388) Add TextFlow to TextArea - Error
[ https://issues.apache.org/jira/browse/FLEX-33388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbyn Gerhardt reopened FLEX-33388: Here a simple example: var newText:TextArea= new TextArea(); newText.textFlow= new TextFlow(); addElement(newText); > Add TextFlow to TextArea - Error > > > Key: FLEX-33388 > URL: https://issues.apache.org/jira/browse/FLEX-33388 > Project: Apache Flex > Issue Type: Bug > Components: Spark: TextArea >Affects Versions: Apache Flex 4.9.0 > Environment: Win 7 > Intel(R) Xeon(R) 2.40 GHz > 6GB RAM >Reporter: Robbyn Gerhardt > Labels: AIR, TLF, TextArea, textFlow > > When you paste text flow will get this error: > TypeError: Error #1009: Cannot access a property or method of a null object > reference. > at > flashx.textLayout.container::TextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:583] > at > spark.components.supportClasses::RichEditableTextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:347] > at > flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:763] > at > spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] > at > flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:772] > at > spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] > at > spark.components::RichEditableText/commitProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/RichEditableText.as:2561] > at > mx.core::UIComponent/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/core/UIComponent.as:8227] > at > mx.managers::LayoutManager/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:605] > at > mx.managers::LayoutManager/doPhasedInstantiation()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:821] > at > mx.managers::LayoutManager/doPhasedInstantiationCallback()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:1188] > I use TLF 3.0.33 in Apache Flex 4.9.0 > In version Apache Flex 4.8.0 it works without problems. -- 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-33388) Add TextFlow to TextArea - Error
[ https://issues.apache.org/jira/browse/FLEX-33388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576788#comment-13576788 ] Alex Harui commented on FLEX-33388: --- Hi Robbyn, A test case is a complete but small application that we can download or cut and paste that compiles and runs. That way we can be sure there isn't some side-effect that is the cause of the problem. > Add TextFlow to TextArea - Error > > > Key: FLEX-33388 > URL: https://issues.apache.org/jira/browse/FLEX-33388 > Project: Apache Flex > Issue Type: Bug > Components: Spark: TextArea >Affects Versions: Apache Flex 4.9.0 > Environment: Win 7 > Intel(R) Xeon(R) 2.40 GHz > 6GB RAM >Reporter: Robbyn Gerhardt > Labels: AIR, TLF, TextArea, textFlow > > When you paste text flow will get this error: > TypeError: Error #1009: Cannot access a property or method of a null object > reference. > at > flashx.textLayout.container::TextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:583] > at > spark.components.supportClasses::RichEditableTextContainerManager/setText()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:347] > at > flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:763] > at > spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] > at > flashx.textLayout.container::TextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/textLayout/3.0.33/src/flashx/textLayout/container/TextContainerManager.as:772] > at > spark.components.supportClasses::RichEditableTextContainerManager/setTextFlow()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/supportClasses/RichEditableTextContainerManager.as:358] > at > spark.components::RichEditableText/commitProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/RichEditableText.as:2561] > at > mx.core::UIComponent/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/core/UIComponent.as:8227] > at > mx.managers::LayoutManager/validateProperties()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:605] > at > mx.managers::LayoutManager/doPhasedInstantiation()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:821] > at > mx.managers::LayoutManager/doPhasedInstantiationCallback()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/LayoutManager.as:1188] > I use TLF 3.0.33 in Apache Flex 4.9.0 > In version Apache Flex 4.8.0 it works without problems. -- 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-33389) The width of the last column header on a horizontally scrolling datagrid
[ https://issues.apache.org/jira/browse/FLEX-33389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576823#comment-13576823 ] Carol Frampton commented on FLEX-33389: --- If you'd like someone to look at this please include a small example program. > The width of the last column header on a horizontally scrolling datagrid > - > > Key: FLEX-33389 > URL: https://issues.apache.org/jira/browse/FLEX-33389 > Project: Apache Flex > Issue Type: Bug > Components: Spark: DataGrid >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: Windows 7 64bit >Reporter: Mikko Torniainen >Priority: Minor > Labels: column, datagrid, header > > To reproduce: > Create a spark datagrid with more columns than fit in the width of the > datagrid. A horizontal scrollbar is shown. You'll see the last column header > will wrap when it's scolled in and out of view. It's width changes based on > how much of it is visible all the way down to zero. The other columns do not > do that. Setting minwidth does not change it. -- 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-33389) The width of the last column header on a horizontally scrolling datagrid
[ https://issues.apache.org/jira/browse/FLEX-33389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikko Torniainen updated FLEX-33389: Attachment: FLEX33389.mxml Flex-33389.air Example app and sourcecode. See the problem by resizing the window. > The width of the last column header on a horizontally scrolling datagrid > - > > Key: FLEX-33389 > URL: https://issues.apache.org/jira/browse/FLEX-33389 > Project: Apache Flex > Issue Type: Bug > Components: Spark: DataGrid >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: Windows 7 64bit >Reporter: Mikko Torniainen >Priority: Minor > Labels: column, datagrid, header > Attachments: Flex-33389.air, FLEX33389.mxml > > > To reproduce: > Create a spark datagrid with more columns than fit in the width of the > datagrid. A horizontal scrollbar is shown. You'll see the last column header > will wrap when it's scolled in and out of view. It's width changes based on > how much of it is visible all the way down to zero. The other columns do not > do that. Setting minwidth does not change it. -- 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-33389) The width of the last column header on a horizontally scrolling datagrid
[ https://issues.apache.org/jira/browse/FLEX-33389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577007#comment-13577007 ] Carol Frampton commented on FLEX-33389: --- I ran your app. I do not see anything wrong. Will you please attach a screenshot of the wrap? What version of AIR are you using? > The width of the last column header on a horizontally scrolling datagrid > - > > Key: FLEX-33389 > URL: https://issues.apache.org/jira/browse/FLEX-33389 > Project: Apache Flex > Issue Type: Bug > Components: Spark: DataGrid >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: Windows 7 64bit >Reporter: Mikko Torniainen >Priority: Minor > Labels: column, datagrid, header > Attachments: Flex-33389.air, FLEX33389.mxml > > > To reproduce: > Create a spark datagrid with more columns than fit in the width of the > datagrid. A horizontal scrollbar is shown. You'll see the last column header > will wrap when it's scolled in and out of view. It's width changes based on > how much of it is visible all the way down to zero. The other columns do not > do that. Setting minwidth does not change it. -- 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-33389) The width of the last column header on a horizontally scrolling datagrid
[ https://issues.apache.org/jira/browse/FLEX-33389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikko Torniainen updated FLEX-33389: Attachment: lastcolumn.png Screenshot as requested. I'm running air 3.5. Here you can see when the last column is partly visible it's width gets smaller to fit the area and cause the label to use the three dots, where the other columns do not do this. This is more of a pain if you modify the skin to have multirow headers. > The width of the last column header on a horizontally scrolling datagrid > - > > Key: FLEX-33389 > URL: https://issues.apache.org/jira/browse/FLEX-33389 > Project: Apache Flex > Issue Type: Bug > Components: Spark: DataGrid >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: Windows 7 64bit >Reporter: Mikko Torniainen >Priority: Minor > Labels: column, datagrid, header > Attachments: Flex-33389.air, FLEX33389.mxml, lastcolumn.png > > > To reproduce: > Create a spark datagrid with more columns than fit in the width of the > datagrid. A horizontal scrollbar is shown. You'll see the last column header > will wrap when it's scolled in and out of view. It's width changes based on > how much of it is visible all the way down to zero. The other columns do not > do that. Setting minwidth does not change it. -- 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-33389) The width of the last column header on a horizontally scrolling datagrid
[ https://issues.apache.org/jira/browse/FLEX-33389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Frampton resolved FLEX-33389. --- Resolution: Not A Problem Fix Version/s: Apache Flex 4.9.0 Since you did not provide a typicalItem the first data item is used. The first column is sized for 'Pavement', the second column is sized for ''Slanted and Enchanted' and the third column is sized for '11.99'. For the first and second columns the data is longer than the headerText so you don't notice. For the third column, the data is much shorter than the headerText so the headerText is truncated. You can either specify a typicalItem, explicitly size the column, or provide a custom headerRenderer for the DataGridColumn to wrap the text. > The width of the last column header on a horizontally scrolling datagrid > - > > Key: FLEX-33389 > URL: https://issues.apache.org/jira/browse/FLEX-33389 > Project: Apache Flex > Issue Type: Bug > Components: Spark: DataGrid >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: Windows 7 64bit >Reporter: Mikko Torniainen >Priority: Minor > Labels: column, datagrid, header > Fix For: Apache Flex 4.9.0 > > Attachments: Flex-33389.air, FLEX33389.mxml, lastcolumn.png > > > To reproduce: > Create a spark datagrid with more columns than fit in the width of the > datagrid. A horizontal scrollbar is shown. You'll see the last column header > will wrap when it's scolled in and out of view. It's width changes based on > how much of it is visible all the way down to zero. The other columns do not > do that. Setting minwidth does not change it. -- 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-33389) The width of the last column header on a horizontally scrolling datagrid
[ https://issues.apache.org/jira/browse/FLEX-33389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikko Torniainen updated FLEX-33389: Attachment: (was: Flex-33389.air) > The width of the last column header on a horizontally scrolling datagrid > - > > Key: FLEX-33389 > URL: https://issues.apache.org/jira/browse/FLEX-33389 > Project: Apache Flex > Issue Type: Bug > Components: Spark: DataGrid >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: Windows 7 64bit >Reporter: Mikko Torniainen >Priority: Minor > Labels: column, datagrid, header > Fix For: Apache Flex 4.9.0 > > Attachments: FLEX33389.mxml, lastcolumn.png > > > To reproduce: > Create a spark datagrid with more columns than fit in the width of the > datagrid. A horizontal scrollbar is shown. You'll see the last column header > will wrap when it's scolled in and out of view. It's width changes based on > how much of it is visible all the way down to zero. The other columns do not > do that. Setting minwidth does not change it. -- 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-33389) The width of the last column header on a horizontally scrolling datagrid
[ https://issues.apache.org/jira/browse/FLEX-33389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikko Torniainen updated FLEX-33389: Attachment: Flex-33389.air I feel my message isn't getting trough. I've added a new version of the demo app. By scrolling the horizontal scroller you should see what I mean. This time all columns are defined to be width 200. I've also made a custom skin with the label truncate removed to make the problem more dramatically visible. > The width of the last column header on a horizontally scrolling datagrid > - > > Key: FLEX-33389 > URL: https://issues.apache.org/jira/browse/FLEX-33389 > Project: Apache Flex > Issue Type: Bug > Components: Spark: DataGrid >Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 > Environment: Windows 7 64bit >Reporter: Mikko Torniainen >Priority: Minor > Labels: column, datagrid, header > Fix For: Apache Flex 4.9.0 > > Attachments: Flex-33389.air, FLEX33389.mxml, lastcolumn.png > > > To reproduce: > Create a spark datagrid with more columns than fit in the width of the > datagrid. A horizontal scrollbar is shown. You'll see the last column header > will wrap when it's scolled in and out of view. It's width changes based on > how much of it is visible all the way down to zero. The other columns do not > do that. Setting minwidth does not change it. -- 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
