From scolella at qorvis.com Thu Jan 22 06:02:54 2009 From: scolella at qorvis.com (Shane Colella) Date: Thu, 22 Jan 2009 09:02:54 -0500 Subject: [Golist] loop error Message-ID: Any one encountered this error from Go and HydroTween. TypeError: Error #1009: Cannot access a property or method of a null object reference. at MethodInfo-1412() at Function/http://adobe.com/AS3/2006/builtin::apply() at com.hydrotik.go::HydroTween/onUpdate() at org.goasap.items::LinearGo/update() at org.goasap::GoEngine$/update() I have had everything working well and this is now randomly cropping up,... I under stand the 1009 error, but I cannot track it down, that's why I am asking about this for GO or Hydro... or is this my mistake somewhere,..? btw, once triggered, this error endlessly loops? It's not a onetime throw. Thanks... Shane -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at gomedia.us Thu Jan 22 06:16:48 2009 From: chris at gomedia.us (Christopher Wilson) Date: Thu, 22 Jan 2009 09:16:48 -0500 Subject: [Golist] loop error In-Reply-To: References: Message-ID: <6CDCB98EFE31584A9449991A5E524EBB568DDA75C4@MAIL113.mail.lan> As you know, the error is from attempting to change a property of an object that has not been instantiated. Somewhere in your sequence of events there is an object that is not ready to be manipulated. You might want to try adding a listener for the ADDED_TO_STAGE event that all Sprites dispatch. This can add an extra layer of insurance that the object you are messing with is ready to be tweened or whatever you're doing. -Wilson ________________________________ From: golist-bounces at goasap.org [golist-bounces at goasap.org] On Behalf Of Shane Colella [scolella at qorvis.com] Sent: Thursday, January 22, 2009 9:02 AM To: Mailing list for the Go ActionScript Animation Platform Subject: [Golist] loop error Any one encountered this error from Go and HydroTween. TypeError: Error #1009: Cannot access a property or method of a null object reference. at MethodInfo-1412() at Function/http://adobe.com/AS3/2006/builtin::apply() at com.hydrotik.go::HydroTween/onUpdate() at org.goasap.items::LinearGo/update() at org.goasap::GoEngine$/update() I have had everything working well and this is now randomly cropping up,? I under stand the 1009 error, but I cannot track it down, that?s why I am asking about this for GO or Hydro? or is this my mistake somewhere,..? btw, once triggered, this error endlessly loops? It?s not a onetime throw. Thanks? Shane -------------- next part -------------- An HTML attachment was scrubbed... URL: From scolella at qorvis.com Fri Jan 23 08:35:50 2009 From: scolella at qorvis.com (Shane Colella) Date: Fri, 23 Jan 2009 11:35:50 -0500 Subject: [Golist] loop error In-Reply-To: <6CDCB98EFE31584A9449991A5E524EBB568DDA75C4@MAIL113.mail.lan> References: <6CDCB98EFE31584A9449991A5E524EBB568DDA75C4@MAIL113.mail.lan> Message-ID: Thanks Wilson for the input, but I think the issue is one sequence I'm running,... It seems to be playing out of order. Any ideas what am I doing incorrectly here? When I trace out some items like so : var goItem4 : HydroSequence = new HydroSequence( [ { func:trace, args:["11"]}, { target:tmpClicked, scaleX:1.8, scaleY:1.8, x:650, y:150, duration:catCloudZoomDuration, easing:Quintic.easeOut }, { target:tmpOther1, scaleX:.5, scaleY:.5, alpha:0, duration:catCloudZoomDuration/2, easing:Quintic.easeOut }, { target:tmpOther2, scaleX:.5, scaleY:.5, alpha:0, duration:catCloudZoomDuration/2, easing:Quintic.easeOut }, { target:tmpOther3, scaleX:.5, scaleY:.5, alpha:0, duration:catCloudZoomDuration / 2, easing:Quintic.easeOut }, { func:trace, args:["22"]}], [ { func:hideOthers, delay: 0, args:[tmpClicked] } ], [ { func:hider, delay:.2 } ] ) My trace statements fire 22 11 wha???????? Should I be setting duration props in the func calls? I'm due to launch today, and this one bug keeps randomly popping up, and I can't even recreate it consistently. I am noticing that my hydro sequences are all firing out of order though.... Any insight or help would be greatly appreciated. Thanks Shane ________________________________ From: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] On Behalf Of Christopher Wilson Sent: Thursday, January 22, 2009 9:17 AM To: Mailing list for the Go ActionScript Animation Platform Subject: Re: [Golist] loop error As you know, the error is from attempting to change a property of an object that has not been instantiated. Somewhere in your sequence of events there is an object that is not ready to be manipulated. You might want to try adding a listener for the ADDED_TO_STAGE event that all Sprites dispatch. This can add an extra layer of insurance that the object you are messing with is ready to be tweened or whatever you're doing. -Wilson ________________________________ From: golist-bounces at goasap.org [golist-bounces at goasap.org] On Behalf Of Shane Colella [scolella at qorvis.com] Sent: Thursday, January 22, 2009 9:02 AM To: Mailing list for the Go ActionScript Animation Platform Subject: [Golist] loop error Any one encountered this error from Go and HydroTween. TypeError: Error #1009: Cannot access a property or method of a null object reference. at MethodInfo-1412() at Function/http://adobe.com/AS3/2006/builtin::apply() at com.hydrotik.go::HydroTween/onUpdate() at org.goasap.items::LinearGo/update() at org.goasap::GoEngine$/update() I have had everything working well and this is now randomly cropping up,... I under stand the 1009 error, but I cannot track it down, that's why I am asking about this for GO or Hydro... or is this my mistake somewhere,..? btw, once triggered, this error endlessly loops? It's not a onetime throw. Thanks... Shane -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at gomedia.us Fri Jan 23 08:58:10 2009 From: chris at gomedia.us (Christopher Wilson) Date: Fri, 23 Jan 2009 11:58:10 -0500 Subject: [Golist] loop error In-Reply-To: References: <6CDCB98EFE31584A9449991A5E524EBB568DDA75C4@MAIL113.mail.lan> Message-ID: <6CDCB98EFE31584A9449991A5E524EBB568DE78C16@MAIL113.mail.lan> Sorry bro, I haven't touched the GoASAP, Hydro classes at all. By the name of the class "HydroSequence", I assume it is designed to run all those tweens in sequence one after the other. However, your trace function might not be handled in the same way because it does not have the properties like a displayObject would, so they may get handled generically in the object parsing. Generic Objects in AS are not handled sequentially. There is nothing unusual or contingent on timing in the properties your are effecting with the sequence. However, if the function hideOthers or hider actually sets a displayObject to visible=false, it's standard properties will become inaccessible after that. If you are using visble=false, try changing it to alpha=0 instead and see if that does the trick of relieving the error. From: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] On Behalf Of Shane Colella Sent: Friday, January 23, 2009 11:36 AM To: Mailing list for the Go ActionScript Animation Platform Subject: Re: [Golist] loop error Thanks Wilson for the input, but I think the issue is one sequence I'm running,... It seems to be playing out of order. Any ideas what am I doing incorrectly here? When I trace out some items like so : var goItem4 : HydroSequence = new HydroSequence( [ { func:trace, args:["11"]}, { target:tmpClicked, scaleX:1.8, scaleY:1.8, x:650, y:150, duration:catCloudZoomDuration, easing:Quintic.easeOut }, { target:tmpOther1, scaleX:.5, scaleY:.5, alpha:0, duration:catCloudZoomDuration/2, easing:Quintic.easeOut }, { target:tmpOther2, scaleX:.5, scaleY:.5, alpha:0, duration:catCloudZoomDuration/2, easing:Quintic.easeOut }, { target:tmpOther3, scaleX:.5, scaleY:.5, alpha:0, duration:catCloudZoomDuration / 2, easing:Quintic.easeOut }, { func:trace, args:["22"]}], [ { func:hideOthers, delay: 0, args:[tmpClicked] } ], [ { func:hider, delay:.2 } ] ) My trace statements fire 22 11 wha???????? Should I be setting duration props in the func calls? I'm due to launch today, and this one bug keeps randomly popping up, and I can't even recreate it consistently. I am noticing that my hydro sequences are all firing out of order though.... Any insight or help would be greatly appreciated. Thanks Shane ________________________________ From: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] On Behalf Of Christopher Wilson Sent: Thursday, January 22, 2009 9:17 AM To: Mailing list for the Go ActionScript Animation Platform Subject: Re: [Golist] loop error As you know, the error is from attempting to change a property of an object that has not been instantiated. Somewhere in your sequence of events there is an object that is not ready to be manipulated. You might want to try adding a listener for the ADDED_TO_STAGE event that all Sprites dispatch. This can add an extra layer of insurance that the object you are messing with is ready to be tweened or whatever you're doing. -Wilson ________________________________ From: golist-bounces at goasap.org [golist-bounces at goasap.org] On Behalf Of Shane Colella [scolella at qorvis.com] Sent: Thursday, January 22, 2009 9:02 AM To: Mailing list for the Go ActionScript Animation Platform Subject: [Golist] loop error Any one encountered this error from Go and HydroTween. TypeError: Error #1009: Cannot access a property or method of a null object reference. at MethodInfo-1412() at Function/http://adobe.com/AS3/2006/builtin::apply() at com.hydrotik.go::HydroTween/onUpdate() at org.goasap.items::LinearGo/update() at org.goasap::GoEngine$/update() I have had everything working well and this is now randomly cropping up,... I under stand the 1009 error, but I cannot track it down, that's why I am asking about this for GO or Hydro... or is this my mistake somewhere,..? btw, once triggered, this error endlessly loops? It's not a onetime throw. Thanks... Shane -------------- next part -------------- An HTML attachment was scrubbed... URL: From scolella at qorvis.com Fri Jan 23 09:31:52 2009 From: scolella at qorvis.com (Shane Colella) Date: Fri, 23 Jan 2009 12:31:52 -0500 Subject: [Golist] loop error In-Reply-To: <6CDCB98EFE31584A9449991A5E524EBB568DE78C16@MAIL113.mail.lan> References: <6CDCB98EFE31584A9449991A5E524EBB568DDA75C4@MAIL113.mail.lan> <6CDCB98EFE31584A9449991A5E524EBB568DE78C16@MAIL113.mail.lan> Message-ID: Thanks again,. I'm using visible=false to disable any mouseEvents I've got on them. But I guess I can workaround by just removing the listeners instead and using alpha = 0 with that,... I will try that out,... Thanks for your attention to my questions so quickly,... ________________________________ From: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] On Behalf Of Christopher Wilson Sent: Friday, January 23, 2009 11:58 AM To: Mailing list for the Go ActionScript Animation Platform Subject: Re: [Golist] loop error Sorry bro, I haven't touched the GoASAP, Hydro classes at all. By the name of the class "HydroSequence", I assume it is designed to run all those tweens in sequence one after the other. However, your trace function might not be handled in the same way because it does not have the properties like a displayObject would, so they may get handled generically in the object parsing. Generic Objects in AS are not handled sequentially. There is nothing unusual or contingent on timing in the properties your are effecting with the sequence. However, if the function hideOthers or hider actually sets a displayObject to visible=false, it's standard properties will become inaccessible after that. If you are using visble=false, try changing it to alpha=0 instead and see if that does the trick of relieving the error. From: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] On Behalf Of Shane Colella Sent: Friday, January 23, 2009 11:36 AM To: Mailing list for the Go ActionScript Animation Platform Subject: Re: [Golist] loop error Thanks Wilson for the input, but I think the issue is one sequence I'm running,... It seems to be playing out of order. Any ideas what am I doing incorrectly here? When I trace out some items like so : var goItem4 : HydroSequence = new HydroSequence( [ { func:trace, args:["11"]}, { target:tmpClicked, scaleX:1.8, scaleY:1.8, x:650, y:150, duration:catCloudZoomDuration, easing:Quintic.easeOut }, { target:tmpOther1, scaleX:.5, scaleY:.5, alpha:0, duration:catCloudZoomDuration/2, easing:Quintic.easeOut }, { target:tmpOther2, scaleX:.5, scaleY:.5, alpha:0, duration:catCloudZoomDuration/2, easing:Quintic.easeOut }, { target:tmpOther3, scaleX:.5, scaleY:.5, alpha:0, duration:catCloudZoomDuration / 2, easing:Quintic.easeOut }, { func:trace, args:["22"]}], [ { func:hideOthers, delay: 0, args:[tmpClicked] } ], [ { func:hider, delay:.2 } ] ) My trace statements fire 22 11 wha???????? Should I be setting duration props in the func calls? I'm due to launch today, and this one bug keeps randomly popping up, and I can't even recreate it consistently. I am noticing that my hydro sequences are all firing out of order though.... Any insight or help would be greatly appreciated. Thanks Shane ________________________________ From: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] On Behalf Of Christopher Wilson Sent: Thursday, January 22, 2009 9:17 AM To: Mailing list for the Go ActionScript Animation Platform Subject: Re: [Golist] loop error As you know, the error is from attempting to change a property of an object that has not been instantiated. Somewhere in your sequence of events there is an object that is not ready to be manipulated. You might want to try adding a listener for the ADDED_TO_STAGE event that all Sprites dispatch. This can add an extra layer of insurance that the object you are messing with is ready to be tweened or whatever you're doing. -Wilson ________________________________ From: golist-bounces at goasap.org [golist-bounces at goasap.org] On Behalf Of Shane Colella [scolella at qorvis.com] Sent: Thursday, January 22, 2009 9:02 AM To: Mailing list for the Go ActionScript Animation Platform Subject: [Golist] loop error Any one encountered this error from Go and HydroTween. TypeError: Error #1009: Cannot access a property or method of a null object reference. at MethodInfo-1412() at Function/http://adobe.com/AS3/2006/builtin::apply() at com.hydrotik.go::HydroTween/onUpdate() at org.goasap.items::LinearGo/update() at org.goasap::GoEngine$/update() I have had everything working well and this is now randomly cropping up,... I under stand the 1009 error, but I cannot track it down, that's why I am asking about this for GO or Hydro... or is this my mistake somewhere,..? btw, once triggered, this error endlessly loops? It's not a onetime throw. Thanks... Shane -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at gomedia.us Fri Jan 23 10:19:41 2009 From: chris at gomedia.us (Christopher Wilson) Date: Fri, 23 Jan 2009 13:19:41 -0500 Subject: [Golist] loop error In-Reply-To: References: <6CDCB98EFE31584A9449991A5E524EBB568DDA75C4@MAIL113.mail.lan> <6CDCB98EFE31584A9449991A5E524EBB568DE78C16@MAIL113.mail.lan> Message-ID: <6CDCB98EFE31584A9449991A5E524EBB568DE78C7E@MAIL113.mail.lan> That's cool, well if you determine that this is where the error was arising from, maybe you could add event listeners that would be certain all those tweens are absolutely complete before running the function with the visible change. Maybe Hydrotween has an onComplete method... Good luck! From: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] On Behalf Of Shane Colella Sent: Friday, January 23, 2009 12:32 PM To: Mailing list for the Go ActionScript Animation Platform Subject: Re: [Golist] loop error Thanks again,. I'm using visible=false to disable any mouseEvents I've got on them. But I guess I can workaround by just removing the listeners instead and using alpha = 0 with that,... I will try that out,... Thanks for your attention to my questions so quickly,... ________________________________ From: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] On Behalf Of Christopher Wilson Sent: Friday, January 23, 2009 11:58 AM To: Mailing list for the Go ActionScript Animation Platform Subject: Re: [Golist] loop error Sorry bro, I haven't touched the GoASAP, Hydro classes at all. By the name of the class "HydroSequence", I assume it is designed to run all those tweens in sequence one after the other. However, your trace function might not be handled in the same way because it does not have the properties like a displayObject would, so they may get handled generically in the object parsing. Generic Objects in AS are not handled sequentially. There is nothing unusual or contingent on timing in the properties your are effecting with the sequence. However, if the function hideOthers or hider actually sets a displayObject to visible=false, it's standard properties will become inaccessible after that. If you are using visble=false, try changing it to alpha=0 instead and see if that does the trick of relieving the error. From: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] On Behalf Of Shane Colella Sent: Friday, January 23, 2009 11:36 AM To: Mailing list for the Go ActionScript Animation Platform Subject: Re: [Golist] loop error Thanks Wilson for the input, but I think the issue is one sequence I'm running,... It seems to be playing out of order. Any ideas what am I doing incorrectly here? When I trace out some items like so : var goItem4 : HydroSequence = new HydroSequence( [ { func:trace, args:["11"]}, { target:tmpClicked, scaleX:1.8, scaleY:1.8, x:650, y:150, duration:catCloudZoomDuration, easing:Quintic.easeOut }, { target:tmpOther1, scaleX:.5, scaleY:.5, alpha:0, duration:catCloudZoomDuration/2, easing:Quintic.easeOut }, { target:tmpOther2, scaleX:.5, scaleY:.5, alpha:0, duration:catCloudZoomDuration/2, easing:Quintic.easeOut }, { target:tmpOther3, scaleX:.5, scaleY:.5, alpha:0, duration:catCloudZoomDuration / 2, easing:Quintic.easeOut }, { func:trace, args:["22"]}], [ { func:hideOthers, delay: 0, args:[tmpClicked] } ], [ { func:hider, delay:.2 } ] ) My trace statements fire 22 11 wha???????? Should I be setting duration props in the func calls? I'm due to launch today, and this one bug keeps randomly popping up, and I can't even recreate it consistently. I am noticing that my hydro sequences are all firing out of order though.... Any insight or help would be greatly appreciated. Thanks Shane ________________________________ From: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] On Behalf Of Christopher Wilson Sent: Thursday, January 22, 2009 9:17 AM To: Mailing list for the Go ActionScript Animation Platform Subject: Re: [Golist] loop error As you know, the error is from attempting to change a property of an object that has not been instantiated. Somewhere in your sequence of events there is an object that is not ready to be manipulated. You might want to try adding a listener for the ADDED_TO_STAGE event that all Sprites dispatch. This can add an extra layer of insurance that the object you are messing with is ready to be tweened or whatever you're doing. -Wilson ________________________________ From: golist-bounces at goasap.org [golist-bounces at goasap.org] On Behalf Of Shane Colella [scolella at qorvis.com] Sent: Thursday, January 22, 2009 9:02 AM To: Mailing list for the Go ActionScript Animation Platform Subject: [Golist] loop error Any one encountered this error from Go and HydroTween. TypeError: Error #1009: Cannot access a property or method of a null object reference. at MethodInfo-1412() at Function/http://adobe.com/AS3/2006/builtin::apply() at com.hydrotik.go::HydroTween/onUpdate() at org.goasap.items::LinearGo/update() at org.goasap::GoEngine$/update() I have had everything working well and this is now randomly cropping up,... I under stand the 1009 error, but I cannot track it down, that's why I am asking about this for GO or Hydro... or is this my mistake somewhere,..? btw, once triggered, this error endlessly loops? It's not a onetime throw. Thanks... Shane -------------- next part -------------- An HTML attachment was scrubbed... URL: From jakemdunn at gmail.com Fri Jan 23 11:49:59 2009 From: jakemdunn at gmail.com (Jacob Dunn) Date: Fri, 23 Jan 2009 13:49:59 -0600 Subject: [Golist] loop error In-Reply-To: <6CDCB98EFE31584A9449991A5E524EBB568DE78C7E@MAIL113.mail.lan> References: <6CDCB98EFE31584A9449991A5E524EBB568DDA75C4@MAIL113.mail.lan> <6CDCB98EFE31584A9449991A5E524EBB568DE78C16@MAIL113.mail.lan> <6CDCB98EFE31584A9449991A5E524EBB568DE78C7E@MAIL113.mail.lan> Message-ID: If you're just trying to stop people from clicking a button, you could also set sprite.mouseEnabled = false; as well.... Just throwing in my two cents, Jake On Fri, Jan 23, 2009 at 12:19 PM, Christopher Wilson wrote: > That's cool, well if you determine that this is where the error was > arising from, maybe you could add event listeners that would be certain all > those tweens are absolutely complete before running the function with the > visible change. Maybe Hydrotween has an onComplete method? > > > > Good luck! > > > > *From:* golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] *On > Behalf Of *Shane Colella > *Sent:* Friday, January 23, 2009 12:32 PM > > *To:* Mailing list for the Go ActionScript Animation Platform > *Subject:* Re: [Golist] loop error > > > > Thanks again,. > > I'm using visible=false to disable any mouseEvents I've got on them. But I > guess I can workaround by just removing the listeners instead and using > alpha = 0 with that,? > > I will try that out,? > > > > Thanks for your attention to my questions so quickly,? > > > > > ------------------------------ > > *From:* golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] *On > Behalf Of *Christopher Wilson > *Sent:* Friday, January 23, 2009 11:58 AM > *To:* Mailing list for the Go ActionScript Animation Platform > *Subject:* Re: [Golist] loop error > > > > Sorry bro, I haven't touched the GoASAP, Hydro classes at all. By the name > of the class "HydroSequence", I assume it is designed to run all those > tweens in sequence one after the other. However, your trace function might > not be handled in the same way because it does not have the properties like > a displayObject would, so they may get handled generically in the object > parsing. Generic Objects in AS are not handled sequentially. There is > nothing unusual or contingent on timing in the properties your are effecting > with the sequence. However, if the function hideOthers or hider actually > sets a displayObject to visible=false, it's standard properties will become > inaccessible after that. If you are using visble=false, try changing it to > alpha=0 instead and see if that does the trick of relieving the error. > > > > *From:* golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] *On > Behalf Of *Shane Colella > *Sent:* Friday, January 23, 2009 11:36 AM > *To:* Mailing list for the Go ActionScript Animation Platform > *Subject:* Re: [Golist] loop error > > > > Thanks Wilson for the input, but I think the issue is one sequence I'm > running,? > > > > It seems to be playing out of order. > > Any ideas what am I doing incorrectly here? > > > > When I trace out some items like so : > > > > var goItem4 : HydroSequence = new HydroSequence( > > > > [ { func:trace, args:["11"]}, > > { target:tmpClicked, scaleX:1.8, scaleY:1.8, x:650, y:150, > duration:catCloudZoomDuration, > easing:Quintic.easeOut }, > > { target:tmpOther1, scaleX:.5, scaleY:.5, > alpha:0, duration:catCloudZoomDuration/2, > easing:Quintic.easeOut }, > > { target:tmpOther2, scaleX:.5, scaleY:.5, alpha:0, > duration:catCloudZoomDuration/2, > easing:Quintic.easeOut }, > > { target:tmpOther3, scaleX:.5, scaleY:.5, > alpha:0, duration:catCloudZoomDuration / 2, > easing:Quintic.easeOut }, > > { func:trace, args:["22"]}], > > > > [ { func:hideOthers, delay: 0, args:[tmpClicked] } ], > > > > [ { func:hider, delay:.2 } ] > > > > ) > > > > My trace statements fire > > 22 > > 11 > > > > wha???????? > > > > Should I be setting duration props in the func calls? > > > > I'm due to launch today, and this one bug keeps randomly popping up, and I > can't even recreate it consistently. > > I am noticing that my hydro sequences are all firing out of order though?. > > Any insight or help would be greatly appreciated. > > > > Thanks > > > > > > > > Shane > > > > > ------------------------------ > > *From:* golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] *On > Behalf Of *Christopher Wilson > *Sent:* Thursday, January 22, 2009 9:17 AM > *To:* Mailing list for the Go ActionScript Animation Platform > *Subject:* Re: [Golist] loop error > > > > As you know, the error is from attempting to change a property of an object > that has not been instantiated. Somewhere in your sequence of events there > is an object that is not ready to be manipulated. You might want to try > adding a listener for the ADDED_TO_STAGE event that all Sprites dispatch. > This can add an extra layer of insurance that the object you are messing > with is ready to be tweened or whatever you're doing. > > > > -Wilson > ------------------------------ > > *From:* golist-bounces at goasap.org [golist-bounces at goasap.org] On Behalf Of > Shane Colella [scolella at qorvis.com] > *Sent:* Thursday, January 22, 2009 9:02 AM > *To:* Mailing list for the Go ActionScript Animation Platform > *Subject:* [Golist] loop error > > Any one encountered this error from Go and HydroTween. > > > > TypeError: Error #1009: Cannot access a property or method of a null object > reference. > > at MethodInfo-1412() > > at Function/http://adobe.com/AS3/2006/builtin::apply() > > at com.hydrotik.go::HydroTween/onUpdate() > > at org.goasap.items::LinearGo/update() > > at org.goasap::GoEngine$/update() > > > > > > I have had everything working well and this is now randomly cropping up,? > > I under stand the 1009 error, but I cannot track it down, that's why I am > asking about this for GO or Hydro? > > or is this my mistake somewhere,..? > > > > btw, once triggered, this error endlessly loops? It's not a onetime throw. > > > > Thanks? > > > > Shane > > > > _______________________________________________ > GoList mailing list > GoList at goasap.org > http://goasap.org/mailman/listinfo/golist_goasap.org > > -------------- next part -------------- An HTML attachment was scrubbed... URL: