0 Replies Latest reply: Mar 15, 2013 7:19 AM by 4everJang RSS

    Strange behavior of breakpoints

    4everJang Community Member

      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.