Seems like a reason for the problem might be because of getting too many
alert.show() going one after another.
When application starts I am loading some images.
Here is relevant code:
private var imageArrayIndex:int = 0;
public function PreloadImages():void
{
imageArrayIndex++;
var request:URLRequest = new URLRequest("PathToImage");
var imageLoader:Loader = new Loader();
var loaderContext:LoaderContext = new LoaderContext();
loaderContext.checkPolicyFile = true;
imageLoader.contentLoaderInfo.removeEventListener(Event.COMPLETE,
PreloadImage_CompleteHandler);
imageLoader.contentLoaderInfo.removeEventListener(IOErrorEvent.IO_ERROR,
PreloadImage_ErrorHandler);
imageLoader.contentLoaderInfo.addEventListener(Event.COMPLETE,
PreloadImage_CompleteHandler);
imageLoader.contentLoaderInfo.addEventListener(IOErrorEvent.IO_ERROR,
PreloadImage_ErrorHandler);
imageLoader.load(request,loaderContext);
}
private function PreloadImage_CompleteHandler(event:Event):void
{
imageArray.addItem(event.currentTarget.content.bitmapData);
// Check to see if there are still images that need to be loaded.
if (imageArrayIndex < imagesToLoad.length)
{
PreloadImages();
}
else
{
event.target.loader.contentLoaderInfo.removeEventListener(Event.COMPLETE,
PreloadImage_CompleteHandler);
event.target.loader.contentLoaderInfo.removeEventListener(IOErrorEvent.IO_ERROR,
PreloadImage_ErrorHandler);
}
}
// Called when the Loader we declared in PreloadImages() encountered an
error trying to load the image.
private function PreloadImage_ErrorHandler(event:Event):void
{
Alert.show(_iconStateName + " could not be loaded.\n\nPlease make sure the
file exists.");
// Check to see if there's still images that need to be loaded.
if (imageArrayIndex < imagesToLoad.length)
{
PreloadImages();
}
}
So, if a specific system cannot load images I am going to have a lot of
alerts because I am loading about 30 files.
What would you suggest? And why it mostly works? Definitely none of
computers running it in-house have any problem.
Thanks
On Tue, Nov 1, 2016 at 11:14 AM mark goldin <[email protected]> wrote:
> Great, will try.
>
> On Tue, Nov 1, 2016 at 10:48 AM Clint M <[email protected]> wrote:
>
> Some ideas:
>
> - compile the app with -verbose-stacktraces=true
> - get them to install the debug player… it'll show a dialog when an error
> occurs
> - or you could trap the uncaughtErrorEvent and display a message (
> http://stackoverflow.com/a/6597046/3384609)
>
> Sometimes a null pointer in flex's validation methods (updateDisplayList,
> commitProperties) can cause an app to crash.
> You can listen for errors on those methods like this.
>
> import mx.core.UIComponentGlobals
> import mx.managers.SystemManagerGlobals
> import mx.events.DynamicEvent
>
> private function app_preinit(event:Event):void {
> UIComponentGlobals.catchCallLaterExceptions = true;
>
>
> SystemManagerGlobals.topLevelSystemManagers[0].addEventListener("callLaterError",
> systemManager_callLaterError);
> }
>
> private function systemManager_callLaterError(event:DynamicEvent):void {
> Alert.show(event.error.message + "\n" + event.error.getStackTrace());
> }
>
>
> On Tue, Nov 1, 2016 at 8:11 AM, mark goldin <[email protected]> wrote:
>
> > We have flex 3 app compiled with 4.13 SDK. in our development environment
> > everything works fine. But on the customer site some users are having
> > problems running it in IE. The app starts loading showing a progress bar
> > but then the whole screen becomes black. Any idea what that might be? Any
> > debuging suggestions?
> >
> > Thanks
> >
>
>
