I vote for the change, I ran into this issue myself. Dimitrios Gianninas RIA Developer Optimal Payments Inc.
________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of alimcleod Sent: Friday, February 02, 2007 12:58 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Modules and Cairngorm - Solution... I think Hi, This does look like a bug with SequenceCommand. I've been looking at the various options as to how to fix this. I've never been overly enamoured with SequenceCommand (it wasn't something we ever used in projects), but there was enough requests for us to add it. I suppose my initial question would be around how attached people are to the current API. We have discussed this here and can see a better implementation, but that would require changes to existing code. So, for the people who use SequenceCommand, how would you feel about having to change your client code, though it would be a relatively only small change in each place you use SequenceCommand? Thoughts? Alistair --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> , "ben.clinkinbeard" <[EMAIL PROTECTED]> wrote: > > Martin, you did give me enough of an idea to wonder if SequenceCommand > was making the same mistake you were. After some experimenting I > suspect that it was. I was setting nextEvent in the execute method of > my SequenceCommand subclass. I went and looked at the docs > (http://www.cairngormdocs.org/docs/cairngorm_2_1/index.html > <http://www.cairngormdocs.org/docs/cairngorm_2_1/index.html> ) and they > suggest setting it in the constructor, so I tried that. Same error. > Finally, I tried setting it in a handler method in my SC subclass (its > a file upload command), on the line right before executeNextCommand () > and that seems to have fixed it. > > It makes me wary of SequenceCommand though, so I am converting any > classes that subclass it to regular command classes and I will just > set and dispatch the "next event" manually. I also tried (very > briefly) switching to the Cairngorm 2.2 beta SWC and was still getting > the error. > > Hey AC guys, is there a bug in SequenceCommand? :) > > Hopefully this info helps others. > Ben > > > > --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> , > Martin Wood-Mitrovski > <flashdev@> wrote: > > > > I just had the same error and it was because i was trying to re- use > event > > instances rather than dispatching new ones each time. But i wasnt > using modules, > > just a normal Cairngorm app. > > > > I was going to look into it to find out exactly what was happening > but I just > > dont have the time at the moment. > > > > maybe this is enough of a clue for someone else to say why :) > > > > Bjorn Schultheiss wrote: > > > Hey Can anyone give me the lowdown on this error > > > > > > TypeError: Error #1034: Type Coercion failed: cannot convert > > > flash.events::[EMAIL PROTECTED] to > com.adobe.cairngorm.control.CairngormEvent. > > > -- WARNING ------- This electronic message and its attachments may contain confidential, proprietary or legally privileged information, which is solely for the use of the intended recipient. No privilege or other rights are waived by any unintended transmission or unauthorized retransmission of this message. If you are not the intended recipient of this message, or if you have received it in error, you should immediately stop reading this message and delete it and all attachments from your system. The reading, distribution, copying or other use of this message or its attachments by unintended recipients is unauthorized and may be unlawful. If you have received this e-mail in error, please notify the sender. AVIS IMPORTANT -------------- Ce message électronique et ses pièces jointes peuvent contenir des renseignements confidentiels, exclusifs ou légalement privilégiés destinés au seul usage du destinataire visé. L'expéditeur original ne renonce à aucun privilège ou à aucun autre droit si le présent message a été transmis involontairement ou s'il est retransmis sans son autorisation. Si vous n'êtes pas le destinataire visé du présent message ou si vous l'avez reçu par erreur, veuillez cesser immédiatement de le lire et le supprimer, ainsi que toutes ses pièces jointes, de votre système. La lecture, la distribution, la copie ou tout autre usage du présent message ou de ses pièces jointes par des personnes autres que le destinataire visé ne sont pas autorisés et pourraient être illégaux. Si vous avez reçu ce courrier électronique par erreur, veuillez en aviser l'expéditeur.
