Conflict editors opened via Compare With menu require postprocessing
CodingTracker records operations that belong to conflict editors, for which it can not detect the edited Java file. An example of such conflict editors are those opened via Compare With menu. To correctly replay such operations, the collected data require postprocessing, which should detect the edited file from the related operations (e.g. externally modified file operation preceding saved conflict editor operation) and update the open conflict editor operation accordingly. For more details, see issue #286.
@Wanderer777
What is the status of this issue? Has this issue been resolved?
@reprogrammer: This is a low priority issue, mostly a memo. The current version of CodingTracker collects sufficient information. Later, if we need to analyze code changes specific to conflict editors (or these code changes break the replay), then we will implement the required postprocessing, resolving this issue.