From b7f192eea34e0bd36abcd457333ab37eb221789f Mon Sep 17 00:00:00 2001 From: Simon Tatham Date: Sat, 22 Oct 2005 16:35:23 +0000 Subject: Cleanup: the `mouse_priorities' field in the back end has been a more general-purpose flags word for some time now. Rename it to `flags'. [originally from svn r6414] --- devel.but | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) (limited to 'devel.but') diff --git a/devel.but b/devel.but index 88ff947..66413ec 100644 --- a/devel.but +++ b/devel.but @@ -1166,8 +1166,7 @@ State changes as a result of a Restart operation are never animated; the mid-end will handle them internally and never consult this function at all. State changes as a result of Solve operations are also not animated by default, although you can change this for a -particular game by setting a flag in \c{mouse_priorities} -(\k{backend-mouse-priorities}). +particular game by setting a flag in \c{flags} (\k{backend-flags}). The function is also passed a pointer to the local \c{game_ui}. It may refer to information in here to help with its decision (see @@ -1441,12 +1440,12 @@ the game was first completed (by setting a flag in freeze the timer thereafter so that the user can undo back through their solution process without altering their time. -\S{backend-mouse-priorities} \c{mouse_priorities} +\S{backend-flags} \c{flags} -\c int mouse_priorities; +\c int flags; -This field is badly named. It is in fact a generic flags word. It -consists of the bitwise OR of the following flags: +This field contains miscellaneous per-backend flags. It consists of +the bitwise OR of some combination of the following: \dt \cw{BUTTON_BEATS(x,y)} -- cgit v1.1