search

behindthebeats / glomaker

Automatically exported from code.google.com/p/glomaker
1 stars 0 forks source link

SWFLoaderPlugin remaining issues. #221

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Load an AVM1 movie (AS2)
2. Load a MovieClip (AS3)

The AMV1 loader can now control AVM1 movies and seems stable between pages.
However, its dimensions are not being read correctly resulting in layout
issues.

Both the AVM1 and MovieClip loaders will lose the loaded movie if the
project is packaged and reopened. This seems to happen on pages after page
one. Could be a file paths issue or relates to XML.

Original issue reported on code.google.com by martinag...@googlemail.com on 21 Jul 2009 at 4:35

GoogleCodeExporter commented 9 years ago 
There remain some possible ways of creating a successful bridge between GLO 
Maker and
AS2 content but there are significant problems here. Unfortunately Local 
Connection
seems to fail if more than one connection is set-up simultaneously, as can 
happen if
several component instances make a call together. In the end I have concluded 
Local
Connection cannot be relied upon within the GLO Maker framework. However, the
SWFLoaderPlugin will still load AS2 movies. It will not be able to control them 
however.

Original comment by martinag...@googlemail.com on 11 Aug 2009 at 3:54

GoogleCodeExporter commented 9 years ago 
Issue 189 has been merged into this issue.

Original comment by martinag...@googlemail.com on 11 Aug 2009 at 4:00