Replies: 4 comments
-
|
Hi @chardan
Breakpoints are identified by the red ball in the left margin of the source file. You can double-click on the line number to set the breakpoint (or delete it). You can also use RMB on the line number to do more detailed actions. This wiki entry is not complete, but it does describe some of the Breakpoint menu commands. https://github.com/epasveer/seer/wiki/Breakpoints
The current line is the yellow highlighted line. The grey highlighted line is one of the calling functions from the stack. In my example, that calling function is "main" from line 24.
|
Beta Was this translation helpful? Give feedback.
-
Are you saying when Seer reaches a breakpoint, it doesn't move the cursor to that line of code (possibly opening the file if it needs to)? |
Beta Was this translation helpful? Give feedback.
-
Where are you clicking (what window)? Screenshots of where your are clicking and seeing problems might help describe the problem. |
Beta Was this translation helpful? Give feedback.
-
|
Oh, and, thanks for trying out Seer! Any suggestions and bug fixes are welcomed! |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Please forgive me if Seer already has this feature, but one feature I miss from DDD is that when you set a breakpoint or just are tracing through the program it highlights the entire "current" line. I haven't been able to find this in Seer (and I think it would make a good default, also), nor is it moving the view to a breakpoint when it tells me it's stopped at one, leaving me to go search for it. Clicking on the line saying the break has occured does not take me to that line. I see in some of the screenshots that this is available, but I can't find it so far. In that case, I guess I'm petitioning for it to be the default. :-)
Beta Was this translation helpful? Give feedback.
All reactions