Comments on: ArrayCollection.getItemAt() doesn’t return null http://www.rubenswieringa.com/blog/arraycollectiongetitemat-doesnt-return-null Ruben Swieringa on Actionscript and a whole lot of other stuff.. Wed, 14 Jul 2010 10:22:27 +0200 http://wordpress.org/?v=2.8.2 hourly 1 By: Patrick http://www.rubenswieringa.com/blog/arraycollectiongetitemat-doesnt-return-null/comment-page-1#comment-92327 Patrick Wed, 30 Sep 2009 21:07:13 +0000 http://www.rubenswieringa.com/blog/arraycollectiongetitemat-doesnt-return-null#comment-92327 wow, two years and the docs are still wrong. :( They could've at least given us a "containsItemAt" function to match the "contains" function so we don't need to rely on wonky exception handling. wow, two years and the docs are still wrong. :( They could’ve at least given us a “containsItemAt” function to match the “contains” function so we don’t need to rely on wonky exception handling.

]]> By: Ruben http://www.rubenswieringa.com/blog/arraycollectiongetitemat-doesnt-return-null/comment-page-1#comment-52402 Ruben Fri, 29 Aug 2008 07:28:08 +0000 http://www.rubenswieringa.com/blog/arraycollectiongetitemat-doesnt-return-null#comment-52402 Hey Carl, [quote comment="52268"]What DOES it return?[/quote] Well it doesn't really return anything, the getItemAt()-method is canceled and the error is thrown. If you would set the returned value to a variable called <em>'someValue'</em> and test the value after having tried/caught the RangeError, then you'd see that the value of <em>someValue</em> would still be what it was before. Hey Carl,

quote from carl:

What DOES it return?

Well it doesn’t really return anything, the getItemAt()-method is canceled and the error is thrown. If you would set the returned value to a variable called ’someValue’ and test the value after having tried/caught the RangeError, then you’d see that the value of someValue would still be what it was before.

]]> By: carl http://www.rubenswieringa.com/blog/arraycollectiongetitemat-doesnt-return-null/comment-page-1#comment-52300 carl Thu, 28 Aug 2008 18:20:12 +0000 http://www.rubenswieringa.com/blog/arraycollectiongetitemat-doesnt-return-null#comment-52300 This is possibly old news for you. However, there is a solution to this problem. Since it's not on here - figured I'd at least post my findings. Use Try/Catch: function myFunction():void{ try{ myArrayCollection.getItemAt(0); trace('the item is there'); } catch(e:RangeError){ trace('the item is out of bounds'); //or alert.show if you choose } } This is possibly old news for you. However, there is a solution to this problem. Since it’s not on here – figured I’d at least post my findings. Use Try/Catch:

function myFunction():void{
try{
myArrayCollection.getItemAt(0);
trace(’the item is there’);
}
catch(e:RangeError){
trace(’the item is out of bounds’); //or alert.show if you choose
}
}

]]> By: carl http://www.rubenswieringa.com/blog/arraycollectiongetitemat-doesnt-return-null/comment-page-1#comment-52268 carl Thu, 28 Aug 2008 14:49:29 +0000 http://www.rubenswieringa.com/blog/arraycollectiongetitemat-doesnt-return-null#comment-52268 Just a question as I'm sort of running into the same problem. What DOES it return? Just a question as I’m sort of running into the same problem. What DOES it return?

]]> By: berryblitz http://www.rubenswieringa.com/blog/arraycollectiongetitemat-doesnt-return-null/comment-page-1#comment-17696 berryblitz Sat, 02 Feb 2008 05:09:26 +0000 http://www.rubenswieringa.com/blog/arraycollectiongetitemat-doesnt-return-null#comment-17696 We all know that Adobe Flex still have lots of errors that are quite weird that we don't get on other tools. Maybe we give Flex some more time. Maybe on Adobe Flex 5 some of the "weird" issues would be solve. We all know that Adobe Flex still have lots of errors that are quite weird that we don’t get on other tools. Maybe we give Flex some more time. Maybe on Adobe Flex 5 some of the “weird” issues would be solve.

]]> By: Ruben http://www.rubenswieringa.com/blog/arraycollectiongetitemat-doesnt-return-null/comment-page-1#comment-9806 Ruben Thu, 08 Nov 2007 21:15:36 +0000 http://www.rubenswieringa.com/blog/arraycollectiongetitemat-doesnt-return-null#comment-9806 ..but you do get a RangeError, right? ..but you do get a RangeError, right?

]]> By: Andrew http://www.rubenswieringa.com/blog/arraycollectiongetitemat-doesnt-return-null/comment-page-1#comment-9805 Andrew Thu, 08 Nov 2007 20:57:57 +0000 http://www.rubenswieringa.com/blog/arraycollectiongetitemat-doesnt-return-null#comment-9805 Actually, I have the same problem, if you try and test it against null it passes the test, and never returns null. (myArrayCollection.getItemAt(invalidLocation) == null) never returns false. Actually, I have the same problem, if you try and test it against null it passes the test, and never returns null.

(myArrayCollection.getItemAt(invalidLocation) == null) never returns false.

]]> By: Ruben http://www.rubenswieringa.com/blog/arraycollectiongetitemat-doesnt-return-null/comment-page-1#comment-8249 Ruben Fri, 26 Oct 2007 18:42:43 +0000 http://www.rubenswieringa.com/blog/arraycollectiongetitemat-doesnt-return-null#comment-8249 Hmm, maybe, but it still sounds kinda shady to me ;) Hmm, maybe, but it still sounds kinda shady to me ;)

]]> By: boon http://www.rubenswieringa.com/blog/arraycollectiongetitemat-doesnt-return-null/comment-page-1#comment-8213 boon Fri, 26 Oct 2007 08:14:07 +0000 http://www.rubenswieringa.com/blog/arraycollectiongetitemat-doesnt-return-null#comment-8213 I think what the livedoc is trying to say is that if there is an object at that index, it will be returned, otherwise null is returned. But if you try to access things outside of the valid range, of course you should get an exception. It would be bad if the framework silently lets you do that without alarming you of your bug. I think what the livedoc is trying to say is that if there is an object at that index, it will be returned, otherwise null is returned. But if you try to access things outside of the valid range, of course you should get an exception. It would be bad if the framework silently lets you do that without alarming you of your bug.

]]>