Fixed bug LT-85 (Location Response Selections). Work on LT-9 and LT-12

Packages/lesiontracker/client/components/lesionTableRow/lesionTableRow.js

@@ -3,3 +3,40 @@ Template.lesionTableRow.helpers({
         return Timepoints.find({}, {sort: {timepointName: 1}});
     }
 });
+
+function doneCallback(measurementData, deleteTool) {
+    // If a Lesion or Non-Target is removed via a dialog
+    // opened by the Lesion Table, we should clear the data for
+    // the specified Timepoint Cell
+    if (deleteTool === true) {
+        Meteor.call("removeMeasurement", measurementData.id, function(error, response) {
+            console.log('Removed!');
+        });
+    }
+}
+
+Template.lesionTableRow.events({
+    'dblclick .location': function() {
+        log.info('Double clicked on Lesion Location cell');
+
+        var measurementData = this;
+
+        // TODO = Fix this weird issue? Need to set toolData's ID properly..
+        measurementData.id = this._id;
+
+        changeLesionLocationCallback(measurementData, null, doneCallback);
+    },
+    'keypress .location': function(e) {
+        var keyCode = e.keyCode;
+        if (keyCode === keys.DELETE ||
+            (keyCode === keys.D && e.ctrlKey === true)) {
+            var currentMeasurement = Template.parentData(1);
+            var currentTimepointID = this.timepointID;
+
+            showConfirmDialog(function() {
+                log.info('Removing Lesion: ' + currentMeasurement._id);
+                clearMeasurementTimepointData(currentMeasurement._id, currentTimepointID);
+            });
+        }
+    }
+});