Description Stefan Spasojčević 2017-12-12 04:47:37 EST

Dear Sir/Madam,
I believe that an additional functionality in the debugger, which would stop at very first line that will be executed after a user makes an action, would be of great benefit in many situations.
To make a dummy explanation - if we would theoretically put an break-point on  each single line of a project, the debugger would stop at the first line to be reached after an action is taken from the application, and from there all breakpoints should be removed immediately after the debugger stopped at the first line. This off-course is just a more plastic explanation, and instead of putting breakpoints all over the place, a button should be provided to tell the debugger to listen and see which is the first line to be executed next.
I think that this would help in many ways in the development and especially maintenance of the application.
To name an example of an benefit, it could help a developer identify what is happening and where in the code, without the need to pinpoint a break point based on previous knowledge of the code and project structure or trust in the naming conventions. 
Kind regards and thank you for reviewing my suggestion,
Stefan Spasojcevic
stefanspasojcevic@yahoo.com
+381604090700