Yup thats what u have to do... pass a flag to the command to tell it to execute the next one or not. Thats what I do, works like a charm because the SequenceCommand is exactly what u need for your work. Dimitrios Gianninas RIA Developer Optimal Payments Inc.
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of thegiffman Sent: Tuesday, December 19, 2006 4:40 PM To: [email protected] Subject: [flexcoders] SequenceCommands ... is there a point to their existence? I'm building a live charting application which uses the Cairngorm design pattern. I'm running into a bit of an issue which I thought a SequenceCommand might be just the ticket. However, further investigation has lead me to question not just the use of SequenceCommands in this case, but their usefulness in general. For me to create a new data set for the chart (which actually involves two charts - one zoomed out fully and one zoomed in on an area), I need to do several commands in sequence: 1 - create a data set with a unique id from the back end. 2 - query the back end for the coarse grain data. 3 - query the back end for the fine grain data. 4 - add the data set to the document model. Basically these are four different commands that should be executed in sequence. And it makes sense from an architectural standpoint for them to be separate - I can see wanting to query for fine data in other situations than data set creation (like an update). But here's the kicker - sequence commands don't really seem set up to do this. I can't really get at the commands themselves to set the next event with the constructor, since the front controller handles all this. As such, the sequence command can really just do one action - querying the back end for fine grain data will ALWAYS trigger an event to add the data set. To avoid this, I might include a flag in the event whether to stop or go on to the next command. But this raises the question - can't I do this anyway with a call to the event dispatcher? The value of having sequence commands seems to be the ability to move to the next sequence without the sequence being hardcoded. Yet this functionality doesn't really exist - it is hidden by the front controller. Could someone set me straight here? -- 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.
