[flexcoders] jumpy breakpoints

[Pan Troglodytes]

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 right now in a very specific case:        switch (periodText) {
          case "Day": periodEnd.date++; break;          case "Week": periodEnd.date += 7; break;          case "Month": periodEnd.month++; break;          case "Year": 
periodEnd.fullYear++; break;        }        periodData = history.getPeriod(periodStart, periodEnd);        switch (groupingText) {          case "Site": chartData = periodData; break;          case "Risk": chartData = 
history.getRisks(periodData); break;          case "Category": chartData = history.getCategories(periodData); break;        }Flex marks all breakpoints after the first switch to be invalid.  Unfortunately, I don't have a small reproducible test unit.  But it does happen and can totally wreck my debugging.
-- Jason

__._,_.___





--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com








   



    


  
  
    SPONSORED LINKS
  
          
                  
            
        Web site design development
      
                      
        Computer software development
      
                      
        Software design and development
      
              
                        
            
        Macromedia flex
      
                      
        Software development best practice
      
                    
           
  







  
  
  YAHOO! GROUPS LINKS



   Visit your group "flexcoders" on the web. 
   To unsubscribe from this group, send an email to: [EMAIL PROTECTED] 
   Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



  






__,_._,___