Could cause an ArrayIndexOutOfBoundsException:
at org.petero.droidfish.gamelogic.Position.getPiece (Position.java:153)
at org.petero.droidfish.gamelogic.MoveGen.pseudoLegalMoves (MoveGen.java:109)
at org.petero.droidfish.gamelogic.MoveGen.legalMoves (MoveGen.java:32)
at org.petero.droidfish.gamelogic.TextIO.moveToString (TextIO.java:429)
at org.petero.droidfish.gamelogic.TextIO.moveToString (TextIO.java:339)
at org.petero.droidfish.gamelogic.DroidChessController$SearchListener.notifyCurrMove (DroidChessController.java:826)
Remove the Strength preferences setting.
Add a new left drawer menu item to set the current engine strength in
terms of Elo. Supported for all engines that implement the standard
UCI options UCI_LimitStrength and UCI_Elo.
Elo settings are remembered individually for each engine.
If both "Strength" and "UCI_Elo" is used, "UCI_Elo" tases precedence.
Internally UCI_Elo is converted to a Strength value using a lookup
table that was calculated by playing games against Stockfish 11 using
its UCI_Elo implementation. The time control was 60+0.6 on computers
where Stockfish bench reported about 1.73e6 NPS.
In many cases the pre-comment of one move is displayed at the same
position in the move text as the post-comment of the previous move.
When this is the case, don't make a distinction between pre and post
comments in the "Edit Comments" dialog.
The PGN standard does not allow the '}' character inside a comment,
because it is used to end the comment.
Therefore this character is now replaced with '｝' (fullwidth right
curly bracket) when editing comments. This does not look great but is
better than making the PGN data invalid.
This is needed to avoid problems when dragging one of the R/G/B
sliders. With the default Android conversion code, the other R/G/B
sliders sometimes move during dragging.
