Yes, it does seem a problem - hence me trying to figure out if it was a
'burned in' limitation of the flash runtime, or something I could find a
workaround for.
On Wed, Oct 2, 2013 at 6:58 PM, Alex Harui aha...@adobe.com wrote:
**
Even generating shim classes would result in conflicts if
A class's identifier is only as unique as its fully qualified name. You can
think of an ApplicationDomain as an Object with slots for each class as in:
var appdom:Object = {
flash.display.DisplayObject : flash.display.DisplayObject;
mx.core.UIComponent: mx.core.UIComponent;
}
with the
My first though is that it is likely something to do with the context of
the application. Likely you are not using the WAR as the root context, so
that will change the pathing. Your best bet is to use relative paths if
possible .
On Wed, Oct 2, 2013 at 10:06 AM, rabi...@yahoo.com wrote:
**
3 matches
Mail list logo
