Flexers -

If you ever want to log a bug on Flex or other Macromedia products, you should use the Feature Request/Bug Report Form at

            http://www.macromedia.com/support/email/wishform/

 

Thanks for catching this, Steven!

-e

-----Original Message-----
From: Alex Glosband [mailto:[EMAIL PROTECTED]
Sent:
Thursday, May 06, 2004 11:51 AM
To: '[email protected]'
Subject: RE: [flexcoders] Profiler - found a bug I'm afraid...

 

>>So -- Macromedia, it's a bug with a workaround I'm afraid; should I raise

>>this somewhere ?

 

I'd say you just did. I'll loga bug on your behalf.

 

-Alex

-----Original Message-----
From: Steven Webster [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 06, 20042:44 PM
To: [EMAIL PROTECTED]
Subject: RE: [flexcoders] Profiler - found a bug I'm afraid...

OK, after a frustrating afternoon, I've nailed it in typical "10 minutes after

final act of desparation mailing flexcoders" fashion....

 

If you profile your application as follows it won't work:

 

 

However if you do the following:

 

 

and instead ensure that you have the following entry in flex-config.xml

 

        <!-- generate swfs and swfs for profiling -->
        <!-- query parameter override- ?asprofile=true/?asprofile=false -->
        <generate-profile-swfs>true</generate-profile-swfs>

 

then everything works as advertised.....

 

The reason for this I'm afraid, is that the profiler.war app has a bug,

and isn't encoding the URLs properly - ie if you have a query parameter

appended to your URL, it's not encoding the ?asprofile=true correctly,

and then to drill down, is trying to open a URL like:

 

 

See how that URL has a double "?" in it (the latter ? should have been

encoded)  ... that's enough to cause the profiler to bug out I'm afraid.

 

So -- Macromedia, it's a bug with a workaround I'm afraid; should I raise

this somewhere ?

 

Hope this helps,

 

Steven

 

--

Steven Webster

Technical Director

iteration::two

 




Reply via email to