Hi Serkan, In the emulation components, you may have to catch certain events and redispatch them with the appropriate type. In the event handler that calls Alert, what is the type of the event parameter. Is it an HTTPStatusEvent or a browser event?
If it is an HTTPStatusEvent, then the emulation may be as simple as adding a “status” getter that returns the event’s value property. If it is a browser event, then look at the call stack to see who is dispatching the event. The code that dispatches the event might need to create an HTTPStatusEvent, copy the browser event properties into it, and then dispatch the HTTPStatusEvent. If you are not sure, post the call stack. HTH, -Alex From: Serkan Taş <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Tuesday, February 12, 2019 at 11:52 AM To: "[email protected]" <[email protected]> Subject: Re: Work on Emulation Hi Alex (only you are interested in emulation, right ?) :))) While debugging my code, I realized that there is a conflict between in status and httpStatus values of the event HTTPStatusEvent, at least in my mind. My old flex code, ported to royale, registers and event listener for HTTPStatusEvent.HTTP_STATUS and handler httpResult as below (loader is initialized somewhere) : loader.addEventListener(HTTPStatusEvent.HTTP_STATUS, httpResult); After making http request, the handler returns as below on screen : [cid:[email protected]] This is where it fires window : [cid:[email protected]] It is normally expected that the status holds real value, but here it is not, httpStatus contains the value in "value" as below : [cid:[email protected]] As the HTTPStatusEvent is emulated, I am not sure how to go to solve the issue. Thanks, Serkan
