Closed dtg3 closed 5 years ago
Tracing the issue back, this feature was broken starting with the first commit after the 0.0.1 release tag (096385a0a5a52d3d4ef2ee287e95d94f3b9ab0fa) .
Investigating restoring functionality.
A new branch fixed_develop
has been created which contains a working version of line/col functionality (token highlighting is/was not functioning) and has been updated to meet the new core input and XML output specification. Since all the other branches (with the exception of master) were affected by the
feature breaking commits, the work in those branches may need to be scrapped. Additionally, if a replay based solution is the future of iTrace, this work will also prove to be outdated and not worth the time necessary to debug and fix the problem.
In order to cut further time loss, I propose we simply use the fixed_develop
branch for generating our test data so progress can be made on the post processing application. Bug fixes ONLY should be applied to this branch when necessary and testing using the mouse tracker for precise line/col mapping check will be required. While this may not make the VS plugin suitable for a release, this should be sufficient for the May demo/workshop.
Post conference, we can explore the replay approach which may fundamentally change the plugins anyway, and/or use that time to further refine the tool for a follow-up release.
If this is satisfactory, we can discuss branch closures (or at least renames) and close this issue.
Since this is in the old work and we are not using it for the demo, I'm going to close this issue.
When compared to mouse tracking positions, the line/col values are not correct. This may also be related to part of Issue #24 regarding highlighted tokens.