FYI, I put up a movie to demonstrate the bug. You'll see me double-clicking on a line and see where the breakpoint pops up.http://three.fsphost.com/flex2/breakpointsbug.wmv
(can be slow)http://rapidshare.de/files/26597362/breakpointsbug.wmv.htmlNote: Even though its in the middle of debugging,
On Thursday 29 June 2006 05:31, Pan Troglodytes wrote:
Flex marks all breakpoints after the first switch to be invalid.
FDB will attempt to look upto 10 lines further down from an invalid break
point to find a valid place to set one before giving up.
Maybe you could add a return or trace after
Yes, I had this problem with F2B3. Often found that closing FlexBuilder and reopening would let me put the breakpoint where I wanted. Also had problems a few times getting the debugger to start - it would not break on breakpoints.
I didn't see anyone else with the same problems so I uninstalled
If you add a trace and put a breakpoint on it, it just jumps off that one, too. These are perfectly valid lines of code.Personally, the look-ahead thing seems very bad UI to me. I would much rather it keep the breakpoint where I put it and flag it as invalid. Otherwise, you have to be watching
Anyone else got jumpy breakpoints - meaning you set it on a line of code at design-time and Flex moves it when you hit run? Anyone set breakpoints on perfectly valid code only to have Flex claim the line contains no executable code?
I have ran into this problem several times. Combatting it
5 matches
Mail list logo
