Well, I changed this file over to be a pure class file instead of an MXML
that links to a .AS file.  Works fine with the breakpoints now.  Definitely
seems like a bug related to <Script> and external source files.

On 6/7/07, beecee1977 <[EMAIL PROTECTED]> wrote:

  I'll just echo that I see the same thing (again only in .as files
included by <script> tags).

For me it's usually after line 500 or so, but no amount of cleaning
the project or closing reopening Flex fixes it for me. So I do lots
of moving functions to where I can debug them! :-)

--- In [email protected] <flexcoders%40yahoogroups.com>, Tom
Chiverton <[EMAIL PROTECTED]>

wrote:
>
> On Thursday 07 Jun 2007, Pan Troglodytes wrote:
> > Realized some info that might be relevant. This seems to happen
in a .as
> > file included by a <Script> tag. Not sure if I've run into it in
a regular
> > AS class file.
>
> I certainly recall other people having the same problem, but not a
solution.
>
> --
> Tom Chiverton
> Helping to centrally introduce bleeding-edge channels
> on: http://thefalken.livejournal.com
>
> ****************************************************
>
> This email is sent for and on behalf of Halliwells LLP.
>
> Halliwells LLP is a limited liability partnership registered in
England and Wales under registered number OC307980 whose registered
office address is at St James's Court Brown Street Manchester M2
2JF. A list of members is available for inspection at the registered
office. Any reference to a partner in relation to Halliwells LLP
means a member of Halliwells LLP. Regulated by the Law Society.
>
> CONFIDENTIALITY
>
> This email is intended only for the use of the addressee named
above and may be confidential or legally privileged. If you are not
the addressee you must not read it and must not use any information
contained in nor copy it nor inform any person other than Halliwells
LLP or the addressee of its existence or contents. If you have
received this email in error please delete it and notify Halliwells
LLP IT Department on 0870 365 8008.
>
> For more information about Halliwells LLP visit www.halliwells.com.
>




--
Jason

Reply via email to