peiklk - Developer IT

Search Results

Search found 2 results on 1 pages for 'peiklk'.

Page 1/1 | 1

Flex Flash Action Script Form Events

- by peiklk

Doing some development in Flash Builder 4 using Action Script 3.0. I'm trying to have some code run each time the form is displayed. The form is not always recreated, but sometimes hidden and reused. Visual Basic used to have an Activate event that does similar to what I want. I tried Render, but that fires every time the form changes (via click, text-edit, etc.) We tried the FlexEvent.ADD, but it only fires when the form is first created, same as creation_complete. Is there a good resource that shows the form "life cycle" and all the events and when they are fired and in what order? TIA! NOTE: I'm trying to get our forms to close when the ESC is pressed.

Read the article

IE History Tracking, IFRAMES, and Cross Domain error...

- by peiklk

So here's the deal. We have a Flash application that is running within an HTML file. For one page we call a legacy reporting system in ASP.NET that is within an IFRAME. This page then communicates back to the Flash application using cross-domain scripting (document.domain = "domain" is set in both pages. THIS ALL WORKS. Now the kicker. Flash has history tracking enabled. This loads the history.js file that created a div tag to store page changes so the back and forward buttons work in the browser. Which works for Firefox and Chrome as they create a div tag. HOWEVER In Internet Explorer, history.js creates another IFRAME (instead of a DIV) called ie_historyFrame. When the ScriptResource.axd code attempts to access this with: var frameDoc = this._historyFrame.contentWindow.document; we get an "Access is Denied" error message. ARGH! We've tried getting a handle to this IFRAME and inserting the document.domain code. FAIL. We've tried editing the historytemplate.html file that flex also uses to include document.domain... FAIL. I've tried to edit the underlying ASP.NET page to disable history tracking in the ScriptManager control. FAIL. At my wit's end on this one. We have users who need to use IE to access this site. They are big clients who we cannot tell to just use Firefox. Any suggestions would be greatly appreciated.