Closed johschmitz closed 1 month ago
Tell me what you think (I think I wrote the truth, but actually I did not check):
You can debug addon code by setting breakpoints in the VS Code debugger (red dot). By default debug breakpoints work only for folders opened in current workspace.
If you want to hit breakpoints set in third party modules (for example: site-packages
or Blender internal python files) you need to disable VS code setting blender.addon.justMyCode
### How can I debug into third party library code from within my addon code?
You can debug addon code by setting breakpoints in the VS Code debugger (red dot).
By default debug breakpoints work only for folders opened in current workspace.
If you want to hit breakpoints set in third party modules (for example: `site-packages` or Blender internal python files) you need to disable VS code setting [`blender.addon.justMyCode`](vscode://settings/blender.addon.justMyCode)
Alright, gave it another try combining your ideas and some other things I saw.
Sidenote: Thanks for maintaining this. I am using it to work on https://github.com/johschmitz/blender-driving-scenario-creator and debug into https://github.com/pyoscx/scenariogeneration
Good catch, I thought this was documented already.
I have some suggestions, will write --tomorrow-- later
On 20 Sept 2024, 21:24, at 21:24, Johannes Schmitz @.***> wrote: