This is where it’s come, and the trip has been fun.

Nice to hear from you,
Bill

Marcel

Wouldn’t that be re-starting after the first iteration? Pause would work just like a regular pause.

Let me know if I’m missing something…

Thanks,
Bill

Glad it worked well for you. It sounds (no pun intended) that you did it just right.

Bill

Thanks for your quick and helpful reply.
I have implemented the said state pattern and got it working with sound channels.

The way I did is was by sending a reference to the playTune context class everytime the play was invoked.

Is that the best way to do it?

Thanks,

Bob

You have hit the nail on the head and identified the essence of dealing with design patterns and Flash and Flex. Namely it’s not easy and how do you deal with what amounts to either a global variable (which none of us want) or to put the whole thing into a single class (easy but not a design pattern)?

Take a look at how it was done using a State pattern in Chapter 10 or another type of use in Chapter 11 where the algorithms were used with a Flash design using the Strategy pattern. I believe it forces us to look ever more closely at the nature of relations between classes in design patterns.

I’m not being coy. Rather, I’ve been busy and haven’t had time to solve the problem I presented. The idea emerged from the example in Chapter 9 using the Template Method where it was possible to switch between a video and sound player. Once the first one was solved, the other was quite easy. In this case, you have to deal with the Channel class to start and stop the MP3 play, but how does one access the same instance to start and stop the play — or set up a pause? Hours of fun!

Cheers,
Bill

Hope I was clear, and thanks for the articles and help.