Check out Glinski's Hexagonal Chess, our featured variant for May, 2024.

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Mon, Jan 29 03:47 PM EST in reply to H. G. Muller from 02:00 PM:

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.

The functions I mentioned are only called in movePiece(), and we each have different versions of that function. So, that might not be a problem. However, I did notice that your definition of movePiece() starts like this:

movePiece = function(c) {

Is that just an alternate way of defining a function, or does it make a difference?

I think the new functions I wrote were for the purpose of handling multi-part moves with a common first move. In games like Fusion Chess, it can pop up a requester asking which full move a player wishes to make.

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.

Through testing with a copy that I can add alerts to, I found this line to be the problem:

  if(tabs.length < 2) return;

This appears just before AddButtons(); in GetPieces(). An alert works before this line but not after. Using an alert to report the value of tabs.length, it is 1.

By commenting out this line, the buttonBar shows up, but when I try to navigate through a game, it does nothing but clear the board.


Edit Form

Comment on the page About Game Courier

Conduct Guidelines
This is a Chess variants website, not a general forum.
Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.
Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.
Quick Markdown Guide

By default, new comments may be entered as Markdown, simple markup syntax designed to be readable and not look like markup. Comments stored as Markdown will be converted to HTML by Parsedown before displaying them. This follows the Github Flavored Markdown Spec with support for Markdown Extra. For a good overview of Markdown in general, check out the Markdown Guide. Here is a quick comparison of some commonly used Markdown with the rendered result:

Top level header: <H1>

Block quote

Second paragraph in block quote

First Paragraph of response. Italics, bold, and bold italics.

Second Paragraph after blank line. Here is some HTML code mixed in with the Markdown, and here is the same <U>HTML code</U> enclosed by backticks.

Secondary Header: <H2>

  • Unordered list item
  • Second unordered list item
  • New unordered list
    • Nested list item

Third Level header <H3>

  1. An ordered list item.
  2. A second ordered list item with the same number.
  3. A third ordered list item.
Here is some preformatted text.
  This line begins with some indentation.
    This begins with even more indentation.
And this line has no indentation.

Alt text for a graphic image

A definition list
A list of terms, each with one or more definitions following it.
An HTML construct using the tags <DL>, <DT> and <DD>.
A term
Its definition after a colon.
A second definition.
A third definition.
Another term following a blank line
The definition of that term.