Closed nspruit closed 8 years ago
Cool. Just one question, and that might be because I don't know when a case DebugEvent.CREATE or TERMINATE event is thrown: Why do you represent debugging as opposed to reading and writing? Couldn't you be debugging and writing or reading?
I was meaning to release WD-1.7 with the new bug fixes https://github.com/TestRoots/watchdog/tree/wd-v1.7; would you consider the functionality in this PR to be stable enough to make it into the new release, or would you rather like to wait and release it with the rest of the debug functionality?
From the documentation:
So you're right, you can still read or write while debugging. Therefore, the development activities in the new WDView are no longer disjoint. However, the currently shown activities in the view can all overlap with a debug interval. So: do you have an idea where to show this new activity in the view?
Based on this finding I would postpone the integration of this PR to the next release. This will also be easier for analysing the data later on, as I can then filter out all WD versions except the one containing all functionality for tracking debug activities (v2.0?).
OK, sounds good to me.
What about displaying it in a new chart row on debugging? :)
That is an appropriate solution, I'll see what might be interesting to visualize in this row in Phase 4.
For now, I'll remove the debugging statistics from the WDView.
The changes to the WDView have now been reverted, so this PR now only makes sure that debug intervals are tracked in Eclipse and IntelliJ.
Hi Niels,
Can you file this PR against the new branch wd-2.0? Then I can directly accept it .
Moritz
Sure, see #235. I'll close this PR then
This PR adds support for tracking
and visualizingdebug intervals. For this, the following steps have been performed:The results of these steps can be seen in the following two screenshots showing the WatchDogView in both IDEs: