Adobe Seminar Feedback - (Curse of WiFi)

« [OT] US Remake of Battle Royale - Trailer

Adobe Seminar ("3 Briefs") Feb 07 - Source code »

Feb 28

Adobe Seminar Feedback - (Curse of WiFi)

To all of those that just joined us in the Adobe Seminar, I must apologize for losing connection 3 times, I can't remember the last time I lost connection in my house, and I haven't lost it since, but for those 20 minutes it was cursed. Also note to self, Dual Screen on Windows means issues.

What we are going to do however is record the whole thing for you to play back at your leisure, the slides and source are up in the forums of http://www.flashmobilebook.com (at the bottom), for you to get familiar with the code, and I'll post on here as well as the Adobe Seminar web page as soon as we have the full recording, hopefully this time with Weyert in there for completeness.

So thank you all that attended, and please look out for the full recording...any extra questions please drop them below.

6 comments

§ Alessandro said on : 28/02/07 @ 14:31
Ciao Richard,

keep it up!!!
Alessandro
§ Abdul Qabiz said on : 28/02/07 @ 14:34
Richard,

It happens and sometimes when you don't want it to :)

BTW! Thanks for session, it was useful...

Yup! Dual screen has issues, not sure if Adobe Connect work with that?

-abdul
§ Richard Leggett® said on : 28/02/07 @ 14:50
It seems not, I picked the wrong screen. As a thankyou I'd like to take more time to really go through the information and code I wanted to show. So it may not all be bad :)
§ cisnky said on : 28/02/07 @ 16:07
Forum spam protection thing doesn't work. Couldn't register :(
§ Richard Leggett® said on : 28/02/07 @ 16:09
Hi Cinsky, I'll forward this on to Scott. Cheers for pointing it out...
§ Scott Janousek said on : 28/02/07 @ 19:33
I apologize. Give it a go again.

I reverted back to picking 20 images until I can figure out where the plugin was crapping out.

I was trying to do everyone a favor by limiting to 5 images, but apparently that causes an issue elsewhere in the plugin. Have to track it down.

Anyways, should be fixed. I just did a test registration.

:)