diff options
Diffstat (limited to 'kpat')
| -rw-r--r-- | kpat/freecell-solver/USAGE | 4 | ||||
| -rw-r--r-- | kpat/gamestats.ui | 4 |
2 files changed, 4 insertions, 4 deletions
diff --git a/kpat/freecell-solver/USAGE b/kpat/freecell-solver/USAGE index 16f5c93d..f78295b2 100644 --- a/kpat/freecell-solver/USAGE +++ b/kpat/freecell-solver/USAGE @@ -502,7 +502,7 @@ If you are working on a UNIX or a similar system then you can set some run-time options in "fc-solve" by sending it some signal combinations. -If you send the signal USR1, without sending any other Q_SIGNALS before +If you send the signal USR1, without sending any other signals before that, then "fc-solve" will output the present number of iterations. This method is a good way to monitor an instance that takes a long time to solve. @@ -512,7 +512,7 @@ will print the iteration number and depth on every state that it checks. It is the equivalent of specifying (or unspecifying) the option -i/--iter-output. -If you send it two USR2 Q_SIGNALS and then USR1, then "fc-solve" +If you send it two USR2 signals and then USR1, then "fc-solve" will also print the board of every state. Again, this will only be done assuming the iteration output is turned on. diff --git a/kpat/gamestats.ui b/kpat/gamestats.ui index 9ecf23b4..f5144f00 100644 --- a/kpat/gamestats.ui +++ b/kpat/gamestats.ui @@ -262,8 +262,8 @@ <slot>setGameType(int)</slot> </connection> </connections> -<Q_SLOTS> +<slots> <slot>setGameType(int)</slot> -</Q_SLOTS> +</slots> <layoutdefaults spacing="6" margin="11"/> </UI> |