No, the Applet always considers the King royal, and keeps the order as it is in the selection table (so that Pawns will lead the list). This is just because I tried to keep the interface as simple as possible, and an overwhelming majority of all variants would need it this way.
When making a Diagram it is easy enough to edit the generated HTML definition for swapping the order of the piece lines, or altering the royal parameter value. In the generated GAME code such post-editing is also the easiest solution to the rare cases where you would want it differently. I described this in the Game-code-generation tutorial ('Multiple royals' section). You just have to put your own assignments to the (array) variables wroyal and broyal, to overrule the default setting the include file gives them:
No, the Applet always considers the King royal, and keeps the order as it is in the selection table (so that Pawns will lead the list). This is just because I tried to keep the interface as simple as possible, and an overwhelming majority of all variants would need it this way.
When making a Diagram it is easy enough to edit the generated HTML definition for swapping the order of the piece lines, or altering the royal parameter value. In the generated GAME code such post-editing is also the easiest solution to the rare cases where you would want it differently. I described this in the Game-code-generation tutorial ('Multiple royals' section). You just have to put your own assignments to the (array) variables wroyal and broyal, to overrule the default setting the include file gives them: