Skip navigation
Currently Being Moderated

Strange behavior of breakpoints

Mar 15, 2013 7:19 AM

Hello fellow scripters,


I have a problem with the behavior of breakpoints in the ESTK. If I set breakpoints inside an if / else construct and start the script, the ESTK automatically changes those breakpoints to an inactive state. If this is a feature, I would REALLY like to understand the rationale for this, as I completely fail to see how any automatic overrule by the ESTK could help me debug my scripts.


Is this something I can tell the ESTK to NOT do this ? I don't see why I would not be able to set breakpoints inside code that may or may not be visited.


Any insight in this would be appreciated. If no satisfying rationale can be given I will register it as a bug with Adobe.






More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points