Oleg, Thanks for the help I do appreciate it!
I followed the instructions outlined ( http://labs.adobe.com/technologies/flashplayer10/ ) on labs... and my expectation is that updating to a more recent version of the Flash Player should be, more or less, transparent. In working through this, there seems to be some interdependency between Flash Player 10.1 and AIR 2 (this is an AIR app). I can¹t confirm this... but for posterity, I was able to eliminate the runtime errors I was experiencing by compiling against a patched (I merged AIR 2 bits with the latest) 3.5 Flex SDK. This resolves my first question mark... now just to confirm that each version of AIR is an island unto itself.¹ For that, I¹m satisfied with J.Housers explanation. Thanks again to all for taking the time to calm my nerves. Cheers, Rick Winscot www.quilix.com On 4/7/10 9:58 AM, "Oleg Sivokon" <[email protected]> wrote: > > > > Hi. > You must be seeing RSL conflicts (the classes built into FlashPlayer won't > behave in that way, since they aren't actually loaded from SWF), and if that's > the RSL conflict, like you've loaded a newer version of RSLs into oldish > application, then, well, that's the developer's problem, he should've specify > the correct RSL url, or, if we are talking about AIR, shouldn't have used RSLs > at all. > > Best. > > Oleg > > > >
