Lots better than the Beta!

Question

This is so much better than the beta I used!  I am really enjoying using it.

These are my requests/feedback:

• Bug: If I have a catch with no variable then I can't see the exception info when stepping over it in the Debbuger Canvas (but I can just fine in a normal file)
• After I am done debugging, it is distracting to have my Debugger Canvas still open.  I would like a way to set a flag (or even better, have a persisted check a box on the canvas) that will control if the canvas closes automatically after the debugging session ends.
• If I start editing or click in a window/bubble (what ever you call the little code windows) it would be nice if it would center better.  I have a few large methods that were a bit tricky (a lot of back and forth to the mouse) to debug in conjuction with the smaller methods around it.

Answer 1

Hi,

Thanks for the feedback! It is great to hear that you're enjoying using it.

Great bug! We'll have to look more closely at our exception behavior!  

The feature to close the canvas when you're done debugging is often requested. I like the idea of having something in the canvas itself that users can click on to make it go away after debugging stops. By the way, it would be good to hear more ideas for how to do this without creating too much risk that someone would inadvertently lose a canvas that they wanted to keep around.

Also thanks for pointing out the centering issues. How would you like us to center on large bubbles when you edit them?

Thanks!

--Jens

Answer 2

>> How would you like us to center on large bubbles when you edit them?

Just make sure that the full width of the bubble is on screen and that at least 5 (or so) lines of code below/above the current point of execution are on screen (assuming there are that many lines left in the method). 

>> it would be good to hear more ideas for how to do this

I like the idea of a persitant small toggle button in the top corner of the window.  (Like a  picture of a garbage can or something)

I have noticed two other things that annoy me:

1. If you double click on a find result and the Canvas is the active window, it will open the method in a bubble, but not take you to the line of the find result.  (It just takes you to the top of the method.)+
2. It would be really nice to have a way to open the actual file from a bubble.   I have times I would like to see what the constructor looks like, or some other part of the class.  Now I have to do a search or some other method to find the class and then get to where I was in the the class when I was looking at the bubble.  A simple way to switch to the file/tab of the current bubble would be nice.  (Maybe next to the arrow buttons at the top of each bubble or over next to the "Locals" button.
   

Answer 3

Hi again!

I have good news. There is a way to get to the file! Just right click in the Code bubble and selec "Navigate to file" and it will take you right there. Or if you want to continue debugging in files from where you are, you can click the Debugger Canvas button, which will switch the Debugger to file mode.

It is also an interesting question if we could do better in supporting the scenario of looking at constructors, fields and other class elements directly in the canvas. Currently the closest you can get is by opening the constructor as a bubble in the canvas. You do that by right clicking on the canvas and typing in the name of the class. That will give you a drop down of the constructors.

Thanks again for your feedback, and also thanks for pointing out the problem with lost selection from the Find results!

--Jens