Hi Luke, Thanks for the nearly immediate response I'll file a bug when I have time to put together a test project to show the setup that causes this problem it's kind of complicated so I think an example will really help but I don't have time to create one outside of our project at the moment but I'll post the bug as soon as I can and drop a link in here to the bug when it's filed. Shaun
On Mar 18, 11:58 am, "Luke (Google Employee)" <[email protected]> wrote: > Hi Shaun, > > Can you please file a bug on the issue tracker so we can track it > internally. > > Thanks > > Luke > > On Mar 18, 9:47 am, Shaun <[email protected]> wrote: > > > Hi all, > > This question is pretty much directed to google employees as most of > > mine are, BTW thanks for all your help I'm highly appreciative of the > > SDK and the community around the maps. If I don't get an answer here > > I'll try contacting you through our contact with our premiere account > > but I figure the community at large could probably benefit from seeing > > the conversation. > > > I wonder why the newest releases of the maps API are compiled against > > the Flex 2.0.1 SDK. This is causing me major headaches when > > attempting to build my application against the 3.4 SDK. I did a lot > > of digging and apparently the way Flex resolves where it will get a > > particular classes bytecode is based on the time stamp in the > > catalog.xml of when the AS was compiled to bytecode into the SWF and > > subsequently into the SWC (where the catalog.xml shows the compile > > time time-stamp). > > > So here's how it breaks down, my company compiles some library or > > framework into a SWC file, say this source code references some > > UIComponent that itself depends on a class like say HaloFocusRect > > since our library is being compiled against the 3.4 SDK the bytecode > > in the produced SWC is all 3.4 and everything is good. Now say my > > project uses our library and it uses the flash maps SDK and for > > arguments sake lets say the flash maps never referenced the > > UIComponent our library referenced but it does have a reference to > > HaloFocusRect and it was compiled at a later time than our library, > > now when I compile my application it's going to use the UIComponent > > (because it isn't in the maps SWC) from our library from 3.4 and the > > HaloFocusRect from 2.0.1 because that's what the latest compiled > > version is (even though it's not the newest, even so using the newest > > wouldn't correct the problem). This causes the blendMode error that > > people complain about occasionally because a null check has been > > removed from the HaloFocusRect and moved into another class or dealt > > with in another way in the 3.4 Flex SDK (3.2 and 2.0.1 seem to handle > > this in the same way so compiling against 3.2 works out ok). > > > AHHHHHHHHHH! > > > All this is pretty confusing, a simple remedy (for me :) would be to > > have a version of the maps API compiled against 3.4 (3.2 and 3.5 would > > be nice but right now we're looking to move to 3.4). Can someone tell > > me why this isn't already happening, I know there must be a reason > > (testing, budget... something). > > > BTW I was completely lost on how Flex was determining which classes to > > use when there's an option (same class in different dependencies) and > > finally stumbled on this months after I need it of course, but still > > great to know, article is old but the info is > > relevant.http://www.adobe.com/devnet/flex/articles/link_load_08.html > > > Thanks for any insight, or other suggestions, > > Shaun > > >http://opensource.adobe.com/wiki/display/flexsdk/Download+Flex+3 > > 3.4.1 is stable according to adobe as of this writing -- You received this message because you are subscribed to the Google Groups "Google Maps API For Flash" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api-for-flash?hl=en.
