So my client… Laine Gabriel has been contacting you about trying to get a SWF working with iScreensaver for which they have/purchased.
I do not own the software myself as I am just a developer contracted to make the SWF. I am very familiar with designing software for liquid layouts and very fluent with ActionScript and OOP practices. However this situation has been an ankle biting problem.
For one, I am not even sure what the issue is… apparently they get a blank screen with no error being thrown or warning or anything on their PCs. Though I have never seen this myself as I do not own a PC. I have only read descriptions from the client.
I am attaching the source files without any of the changes you had me make to avoid any confusion:
[ private URL redacted ]
This screensaver isn’t as easy as just making a timeline, although a significant portion does contain a timeline, the requirements are that the stage resizes to fit any screen and the Date class is used to dynamically query the system time to display a countdown.
The main ‘Application’ class is the SWF’s document class. It has an event listener for Event.RESIZE and I adjust the scale of the side bars and main animation to fit any size screen. The only other thing it does is set up stage.align=StageAlign.TOP_LEFT; and stage.scaleMode=StageScaleMode.NO_SCALE; in the constructor.
Everything works as it should across every Flash player I test, except yours. To me it sounds like stage.stageWidth and stage.stageHeight is always reporting 0… which would make the resize scale down to 0 as well. This sounds like a bug with your Flash player. Any chance you got a buggy embedded player from Adobe? Or are you distributing this in some other method… like relying on the system’s Flash player?
Either way, the first thing I would try is applying a setTimeout(onResize,500); inside that constructor to wait for a period of time before calling onResize(). That would be the simplest way to ensure iScreensaver is ready before it sets its final resize.
I am not sure about how any of those other suggestions would help… Although we did try them, they seem very strange to me. Especially having one frame after the stop()… that just sounds crazy! Let me know if you can get anything up and running on your side. I am going to try some other software to see if it is iScreensaver causing the issue. If you can get it to work, we would like to know what you fixed! Thanks!
I will report back to you if I find anything. Thanks!