Icenium Graphite won't stop on debug breakpoints in Simulation mode

8 posts, 0 answers
  1. Ken
    Ken avatar
    4 posts
    Member since:
    May 2013

    Posted 01 May 2013 Link to this post

    So, I installed Graphite  in Windows SP SP3 and worked thru Rob's tutorial.   All very impressive, but when I run the simulator and go into debug mode, it will let me set breakpoints on valid JavaScript locations, but it will never stop on them.

    What am I missing...?
  2. Kristina
    Admin
    Kristina avatar
    57 posts

    Posted 01 May 2013 Link to this post

    Hey Ken,

    Would you please check if the code that you are trying to debug is ever executed? It would also be great if you could provide us with some simple scenario, so that we could reproduce your problem.

    All the best,
    Kristina
    the Telerik team

    Share feedback and vote for features on our Feedback Portal.
    Want some Kendo UI online training - head over to Kendo UI Dojo.
  3. Ken
    Ken avatar
    4 posts
    Member since:
    May 2013

    Posted 02 May 2013 Link to this post

    Hi Kristina,

       Thanks for the speedy reply.  So the code I'm using is the  icenium-reddit  example from Rob Lauer's 3 part tutorial, which I cloned from GitHub.  I can set breakpoints in onDeviceReady() in app.js, which I think must be executed, as well as other functions in app.js and db.js, and when I hit reload, it never pauses on these.  The app looks like it runs just fine in the simulator, but breakpoints never break, even though the Breakpoints panel shows them as being set...
  4. Jan-Dirk
    Jan-Dirk avatar
    327 posts
    Member since:
    Jun 2012

    Posted 02 May 2013 Link to this post

    In my experience, any code that is executed before onDeviceReady() will not 'break' in the debugger. Is that what you are experiencing too?
  5. Ken
    Ken avatar
    4 posts
    Member since:
    May 2013

    Posted 03 May 2013 Link to this post

    No, it isn't.   I can't break on any statement inside  onDeviceReady(),  or any other valid statement in any other function...
  6. Kristian D. Dimitrov
    Admin
    Kristian D. Dimitrov avatar
    68 posts

    Posted 06 May 2013 Link to this post

    Hi Ken,

    We used the same example to test, but we couldn't reproduce your issue on our end.

    In order to break inside the onDeviceReady() handler you must put the breakpoints and hit the Refresh (not the Reload) button of the Simulator. Breakpoints inside the other functions, triggered by user actions, work as expected.

    We'd be really grateful, if you could provide us with a short video illustrating your issue. 

    Regards,
    Kristian D. Dimitrov
    the Telerik team

    Share feedback and vote for features on our Feedback Portal.
    Want some Kendo UI online training - head over to Kendo UI Dojo.
  7. Ken
    Ken avatar
    4 posts
    Member since:
    May 2013

    Posted 07 May 2013 Link to this post

    Hi Kristian,

       Ah, mystery solved!    I'm used to hitting reload when browser debugging to hit breakpoints I've set.

      I'm little curious, though, as to why reload won't accomplish the same thing?    That's not immediately obvious to me...

    Best Regards,
    Ken
  8. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 07 May 2013 Link to this post

    Hi Ken,

    Reload basically reloads the whole application and the debugging tools are not yet available at this time, you can see them being redrawn as you've hit reload. Refresh on the other hand as the name suggests, refreshes the current view and the debugging tools are at your disposal.

    Greetings,
    Steve
    the Telerik team

    Share feedback and vote for features on our Feedback Portal.
    Want some Kendo UI online training - head over to Kendo UI Dojo.
Back to Top