The statuss element is something I use while debugging; by having its object available in a variable it is easy to put error messages in the innerHTML there. After I had debugged the code the statuss element was removed (it would only be in the text part of the preset I used for debugging), and all displaying of error messages was removed, so it doesn't hurt that statuss is now undefined. I could have removed this line too, but leaving it in makes it easier to resume debugging in case of trouble.
If you changed the name of the routines called as event handlers for the mouse clicks on board squares, then you have indeed broken the presets using this code. Proper operation depends on the functions being called. That doesn't explain the non-appearence of the button bar, though, as this is done by the initialisation code, and is not triggered by mouse clicks.
I think most of the functions is the same as your originals; the reason I overruled thos was not because I wanted different behavior w.r.t. the mouse clicks. But l changed the HTML representation of the board on initialization, with the routine FixBoard: this makes the piece images background. I did that to get rid of the annoying expansion and contraction of board ranks when the rank became empty, or a piece on it got highlighted. But this means that the event handlers also have to modify the board squares in a different way in response to the clicks.
The statuss element is something I use while debugging; by having its object available in a variable it is easy to put error messages in the innerHTML there. After I had debugged the code the statuss element was removed (it would only be in the text part of the preset I used for debugging), and all displaying of error messages was removed, so it doesn't hurt that statuss is now undefined. I could have removed this line too, but leaving it in makes it easier to resume debugging in case of trouble.
If you changed the name of the routines called as event handlers for the mouse clicks on board squares, then you have indeed broken the presets using this code. Proper operation depends on the functions being called. That doesn't explain the non-appearence of the button bar, though, as this is done by the initialisation code, and is not triggered by mouse clicks.
I think most of the functions is the same as your originals; the reason I overruled thos was not because I wanted different behavior w.r.t. the mouse clicks. But l changed the HTML representation of the board on initialization, with the routine FixBoard: this makes the piece images background. I did that to get rid of the annoying expansion and contraction of board ranks when the rank became empty, or a piece on it got highlighted. But this means that the event handlers also have to modify the board squares in a different way in response to the clicks.