+1
Under review

Tracepoint "sets" in tracepoint manager

MBR 5 years ago updated by Omer Raviv (CTO) 4 years ago 2
It would be nice in a future version of the hopefully-arriving-soon "tracepoints manager" to have "tracepoint sets" - so there is a list of editable tracepoint set names, and each active one (from a dropdown) would change which tracepoints are checked as active. (Eg., for debugging feature "A" vs. feature "B".)
I wouldn't bother dealing with parent/child relationships or anything, but the next thing would be to allow these sets be enabled/disabled individually rather than one active set from a dropdown.
+1

Yes - so important IMHO - I want to view all the GUI tracepoints during this run - Oops - I saw a calculation error - turn off the gui info and turn on the calculation results. Programs generally group themselves into several areas and while I don't want to see any of the tracepoints firing from area A while I'm working on area B, I don't want to throw them out or laboriously turn them all off while turning all area B's on either. I want to say "Today I'm working on the GUI - turn all the calculation tracepoints off and the GUI tracepoints on" and then be able to disable the GUI tracepoints individually if I want. Otherwise you hesitate to make tracepoints since every one adds to the complexity of turning on and off just the ones you want.

Under review

Thank you for the suggestion and for explaining your scenario, I really appreciate it! We'll look into including this in the future. For now, you can use Visual Studio's Breakpoints Window (Ctrl+Alt+B). OzCode's Tracepoints will appear in this window just as all the other breakpoints do, and while they may be a bit hard to spot, you can then label each tracepoint and then easily disable/enable all the breakpoints with a given label.