You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "Alexander Mazuruk (JIRA)" <ji...@apache.org> on 2013/12/16 16:03:07 UTC

[jira] [Comment Edited] (FLEX-33987) FocusManager NPE

    [ https://issues.apache.org/jira/browse/FLEX-33987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849219#comment-13849219 ] 

Alexander Mazuruk edited comment on FLEX-33987 at 12/16/13 3:02 PM:
--------------------------------------------------------------------

Unfortunately, until all patches are vanished away it's not possible to compile against 4.11. DataGrid changes since there are in critical conflict with our patches(adding freezed columns functionality).

This issue reproduced sporadically, it has an asynchronous nature. Most likely reproducible with a checkbox control as and item editor.
Sorry, guys, don't have much time to spend on this issue, I have to log some more issues for you. I have no resources to dig into deeper understanding on "why" this thing happened in real life, when it's impossible in Theory. 

One thing I know from theory: If you have a function having "return null;" in it, it will fire sooner or later, later or sooner. So I'm not brave enough to assume that it will never happened. In plain Theory it WILL occurs with 100% probability. 

In my team I'm cutting fingers for that kind of code (:



was (Author: leybniz):
Unfortunately, until all patches are vanished away it's not possible to compile against 4.11. DataGrid changes since there are in critical conflict with our patches(adding freezed columns functionality).

This issue reproduced sporadically, it has an asynchronous nature. Most likely reproducible with a checkbox control as and item editor.
Sorry, guys, don't have much time to spend on this issue, I have to log some more issues for you. I have no resources to dig into deeper understanding on "why" this thing happened in real life, when it's impossible in Theory. 

One thing I know from theory: If you have a function having "return null;" in it, it will fire sooner or later, later or sooner. So I'm not brave enough to assume that it will never will happened.

In my team I'm cutting fingers for that kind of code (:


> FocusManager NPE
> ----------------
>
>                 Key: FLEX-33987
>                 URL: https://issues.apache.org/jira/browse/FLEX-33987
>             Project: Apache Flex
>          Issue Type: Bug
>    Affects Versions: Adobe Flex SDK 4.5.1 (Release), Apache Flex 4.11.0
>            Reporter: Alexander Mazuruk
>            Priority: Critical
>
> FocusManager Null pointer exception occurs.
> This:
>     public function getNextFocusManagerComponent(
>                             backward:Boolean = false):IFocusManagerComponent
> 	{
> 		return getNextFocusManagerComponent2(backward, fauxFocus).displayObject as IFocusManagerComponent;
> 	}
> Must be rewritten as:
> public function getNextFocusManagerComponent(
>                             backward:Boolean = false):IFocusManagerComponent
> 	{
>         const focusInfo:FocusInfo = getNextFocusManagerComponent2(backward, fauxFocus);
>         return focusInfo ? focusInfo.displayObject as IFocusManagerComponent : null;
> 	}



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)