Fix line explanation bug (hack)

Probably should be fixed in a better way but...

Author: lee-naish

src/algorithms/index.js

@@ -27,7 +27,21 @@ import * as Instructions from './instructions';
  { pseudocode: String, explanation: String, run: Function }
  */
 
-// Very Important: The key for the algorithms must be unique!
+// Very Important: The key for each algorithm MUST be unique!
+// Also: the key for the algorithm MUST be the same as the "name"
+// of the top level Param block returned by the parameter function.
+// Eg, parameters/msort_arr_td.js has
+// 
+// function MergesortParam() {
+// ...
+// return (
+//     // <>
+//       <div className="form">
+//         <ListParam
+//           name="msort_arr_td"  <---- ****SAME AS KEY****
+// ...
+// export default MergesortParam
+
 const allalgs = {
 
   'heapSort': {

src/context/actions.js

@@ -253,6 +253,13 @@ export const GlobalActions = {
     } = data;
     const procedurePseudocode = pseudocode[params.mode];
 
+    // Previously if we switched modes from insert to search, the search
+    // code had no in-line explanations built.
+    // XXX It seems a bit of overkill to redo the explanations whenever
+    // the algorithm is re-run (changing mode probable should LOAD the
+    // algorithm then separately RUN it) but this works for now...
+    addLineExplanation(procedurePseudocode);
+
     // here we pass a function reference to Chunker() because we may want to initialise
     // a visualiser using a previous one
     const chunker = new Chunker(() =>