-
```
Currently, HOXChess allows a Move which results in a King-facing-King
situation. This is against
common Xiangqi rules.
```
Original issue reported on code.google.com by `huypha...@gmail.com` on…
-
```
we should be able to select multiple chess engine
```
Original issue reported on code.google.com by `Sakur.de...@gmail.com` on 28 Aug 2009 at 2:14
-
```
Currently, HOXChess allows a Move which results in a King-facing-King
situation. This is against
common Xiangqi rules.
```
Original issue reported on code.google.com by `huypha...@gmail.com` on…
-
```
we should be able to select multiple chess engine
```
Original issue reported on code.google.com by `Sakur.de...@gmail.com` on 28 Aug 2009 at 2:14
-
```
these member variavles of xiangqi should be replaced with an
aPieces[$sColor] type array.
```
Original issue reported on code.google.com by `martyn.eggleton@gmail.com` on 9 Jan 2010 at 12:16
-
```
Currently, HOXChess allows a Move which results in a King-facing-King
situation. This is against
common Xiangqi rules.
```
Original issue reported on code.google.com by `huypha...@gmail.com` on…
-
```
Currently, HOXChess allows a Move which results in a King-facing-King
situation. This is against
common Xiangqi rules.
```
Original issue reported on code.google.com by `huypha...@gmail.com` on…
-
Adding a combined print statement to my successfully compiling program
print ["value1: " value1 "value2:" value2]
Causes a compile error
**\* Compilation Error: undefined symbol: ts610
**\* in file…
-