This content has been marked as final. Show 6 replies
What happens if you access Application.application.parameters? Do you get both params?
nope, the applications reference didn't change anything. isChannel still comes up as undefined in UNIX. In fact, using the application parameters makes it fail in Mac OS X as well.
How are you building/passing the flashvars in the html wrapper?
I'm not sure what you mean. The url is like this:
so reportID is the first parameter (with a value of 'Rep1') and channel is the second parameter (with a value of 'Y')
I'm having similar problems on Windows and it's not browser dependent. I ported a Flex 2 app to Flex 3 and url parameters no longer work.
Application.application.parameters is empty, or only contains the flashvars from the wrapper (if any, I've tried it with and without).
I also tried to fall back to the Flex 2 application, but after rebuilding it, parameter passing doesn't work there either (it did and does in the build from March 08), suggesting it's something common to both the 2 and 3 environments. I don't know -- I only know parameter passing is not working and I have a broken app.
Found a solution using ExternalInterface calls. Thanks, Mr. Qabiz!
Though I'd still like to know why Flex doesn't work as documented, I'm at least moving forward.