General Graphics Interface

Update of /cvsroot/ggi/ggi-libs/libggigpf/pipe/rgba
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv18849

Modified Files:
	init.c 
Log Message:
fix debug print. Makes this file compile again

Index: init.c
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libggigpf/pipe/rgba/init.c,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -d -r1.25 -r1.26
--- init.c	16 Jul 2003 17:55:19 -0000	1.25
+++ init.c	29 Oct 2004 23:36:23 -0000	1.26
@@ -85,7 +85,7 @@
 	struct rgbagpf_priv *priv;
 
 	GPFDPRINT_LIBS("GPFopen(%p, %p, %p, %s, %p, %p) called for rgba sublib\n",
-		opio, pipe, dlh, args ? args : "(NULL)", ap, dlret);
+		opio, pipeitem, dlh, args ? args : "(NULL)", ap, dlret);
 
 	LIBGPF_PIPE_PRIVATE(pipeitem) = malloc(sizeof(struct rgbagpf_priv));
 	if (LIBGPF_PIPE_PRIVATE(pipeitem) == NULL) return GGI_ENOMEM;

Update of /cvsroot/ggi/ggi-libs/libggigpf/io/libggi
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv18093

Modified Files:
	conv.c 
Log Message:
fix assertion. Makes this file compile again

Index: conv.c
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libggigpf/io/libggi/conv.c,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -d -r1.27 -r1.28
--- conv.c	16 Jul 2003 17:55:18 -0000	1.27
+++ conv.c	29 Oct 2004 23:32:53 -0000	1.28
@@ -45,7 +45,7 @@
 
 	LIB_ASSERT(handle != NULL);
 	LIB_ASSERT(hnd_pipeline != NULL);
-	LIB_ASSERT(pipe != NULL);
+	LIB_ASSERT(pipeitem != NULL);
 
 	GPFDPRINT_TRANSFER("io-libggi (input): used in handle: %p, pipeitem: %p\n",
 			handle, pipeitem);

Update of /cvsroot/ggi/ggi-libs/libggigpf/io/ppm
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv17378

Modified Files:
	funcs.c 
Log Message:
fix assertion. Makes this file compile again

Index: funcs.c
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libggigpf/io/ppm/funcs.c,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -d -r1.43 -r1.44
--- funcs.c	29 Oct 2004 23:26:18 -0000	1.43
+++ funcs.c	29 Oct 2004 23:29:38 -0000	1.44
@@ -102,7 +102,7 @@
 	int rc = GGI_OK;
 	char buf[MAX_LINELEN];
 
-	LIB_ASSERT(pipe != NULL);
+	LIB_ASSERT(pipeitem != NULL);
 	LIB_ASSERT(priv != NULL);
 
 	memset(buf, 0, MAX_LINELEN);

Update of /cvsroot/ggi/ggi-libs/libggigpf/io/raw
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv17033

Modified Files:
	funcs.c 
Log Message:
fix assertion. Make this file compile again

Index: funcs.c
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libggigpf/io/raw/funcs.c,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- funcs.c	16 Jul 2003 17:55:18 -0000	1.2
+++ funcs.c	29 Oct 2004 23:27:47 -0000	1.3
@@ -240,7 +240,7 @@
 
 	LIB_ASSERT(handle != NULL);
 	LIB_ASSERT(hnd_pipeline != NULL);
-	LIB_ASSERT(pipe != NULL);
+	LIB_ASSERT(pipeitem != NULL);
 
 	priv = RAW_PRIV(hnd_pipeline->opio_input);

Update of /cvsroot/ggi/ggi-libs/libggigpf/io/ppm
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv16690

Modified Files:
	funcs.c ppm_gpf.h 
Log Message:
Cast parameter passed to ctype(3) functions to uint8 to enforce the compiler to look at the correct piece of memory for the bit mask. Fixes some international alphabet problems.

Index: funcs.c
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libggigpf/io/ppm/funcs.c,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -d -r1.42 -r1.43
--- funcs.c	16 Jul 2003 17:55:18 -0000	1.42
+++ funcs.c	29 Oct 2004 23:26:18 -0000	1.43
@@ -248,7 +248,7 @@
 					DEBUG_INFO, strerror(rc));	\
 			goto err1;					\
 		}	/* if */					\
-	} while ( (buf[0] == COMMENT_CHAR) || (isspace((int)buf[0])));
+	} while ( (buf[0] == COMMENT_CHAR) || (isspace((uint8)buf[0])));
 
 
 	READSTR;

Index: ppm_gpf.h
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libggigpf/io/ppm/ppm_gpf.h,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -d -r1.23 -r1.24
--- ppm_gpf.h	16 Jul 2003 17:55:18 -0000	1.23
+++ ppm_gpf.h	29 Oct 2004 23:26:18 -0000	1.24
@@ -88,9 +88,9 @@
 #define COMMENT_CHAR    '#'
 #define QUOTE_CHARS     "'\""
 
-#define SKIPWHITE(str)  {while (isspace((int)*(str)) && *(str) != '\0' \
+#define SKIPWHITE(str)  {while (isspace((uint8)*(str)) && *(str) != '\0' \
 				&& *(str) != COMMENT_CHAR) { (str)++; }}
-#define SKIPNONWHITE(str) {while (!isspace((int)*(str)) && *(str) != '\0' \
+#define SKIPNONWHITE(str) {while (!isspace((uint8)*(str)) && *(str) != '\0' \
 				&& *(str) != COMMENT_CHAR) { (str)++; }}
 #define SKIPTOEND(str)  {while (*(str) != '\0' && *(str) != '\n' \
 				&& *(str) != COMMENT_CHAR) { (str)++; }}

Update of /cvsroot/ggi/ggi-libs/libggigpf/gpf
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv14804

Modified Files:
	EXPSYMS 
Log Message:
export _gpfDebugState symbol

Index: EXPSYMS
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libggigpf/gpf/EXPSYMS,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- EXPSYMS	20 Mar 2003 15:16:44 -0000	1.6
+++ EXPSYMS	29 Oct 2004 23:17:03 -0000	1.7
@@ -1,3 +1,4 @@
+_gpfDebugState
 _gpfDebugSync
 _gpfParseArgs
 _gpf_gettransfersize

Update of /cvsroot/ggi/ggi-libs/libggigpf/gpf
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv14643

Modified Files:
	init.c 
Log Message:
EXPORTVAR is for declarations, not for defintions

Index: init.c
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libggigpf/gpf/init.c,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -d -r1.36 -r1.37
--- init.c	27 Oct 2004 10:02:42 -0000	1.36
+++ init.c	29 Oct 2004 23:16:11 -0000	1.37
@@ -38,9 +38,9 @@
 
 
 /* Exported variables */
-EXPORTVAR uint32	_gpfDebugState = 0;
-EXPORTVAR int		_gpfDebugSync = 0;
-EXPORTVAR void		*_gpf_global_lock = NULL;
+uint32			_gpfDebugState = 0;
+int			_gpfDebugSync = 0;
+void			*_gpf_global_lock = NULL;
 
 /* Global variables */
 void *_gpfConfigHandle = NULL;

Update of /cvsroot/ggi/ggi-libs/libgiigic/doc/man
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv2762

Modified Files:
      Tag: branch-1-0
	gicOpen.3 
Log Message:
regenerate for pulling up revisions 1.8 - 1.9 of libgiigic-functions.txt

Index: gicOpen.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicOpen.3,v
retrieving revision 1.2.2.1
retrieving revision 1.2.2.2
diff -u -d -r1.2.2.1 -r1.2.2.2
--- gicOpen.3	18 Oct 2004 13:43:03 -0000	1.2.2.1
+++ gicOpen.3	29 Oct 2004 22:24:38 -0000	1.2.2.2
@@ -1,6 +1,6 @@
 .TH "gicOpen" 3 "2004-10-18" "libgiigic-1.0.x" GGI
 .SH NAME
-\fBgicOpen\fR, \fBgicClose\fR : Open and close a recogzizer
+\fBgicOpen\fR, \fBgicClose\fR : Open and close a recognizer
 .SH SYNOPSIS
 .nb
 .nf

Update of /cvsroot/ggi/ggi-libs/libgiigic/doc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv2370

Modified Files:
      Tag: branch-1-0
	libgiigic-functions.txt 
Log Message:
pull up revisions 1.8 - 1.9 (requested by cegger):

typo fix: recogzizer -> recognizer. Spotted by neiljp

Index: libgiigic-functions.txt
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/libgiigic-functions.txt,v
retrieving revision 1.3.2.3
retrieving revision 1.3.2.4
diff -u -d -r1.3.2.3 -r1.3.2.4
--- libgiigic-functions.txt	29 Oct 2004 20:20:11 -0000	1.3.2.3
+++ libgiigic-functions.txt	29 Oct 2004 22:22:59 -0000	1.3.2.4
@@ -85,7 +85,7 @@
 
 
 
-Open and close a recogzizer
+Open and close a recognizer
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. manpage:: 3 gicOpen gicClose

Update of /cvsroot/ggi/ggi-libs/libgiigic/doc/man
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv946

Modified Files:
	gicFeatureActivate.3 gicFeatureAllocate.3 
	gicFeatureAttachRecognizerDriver.3 gicFeatureMapActions.3 
	gicFeatureWrite.3 gicOpen.3 gicRecognizerWrite.3 
Log Message:
regen. manpages

Index: gicFeatureActivate.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicFeatureActivate.3,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- gicFeatureActivate.3	28 Oct 2004 05:31:13 -0000	1.4
+++ gicFeatureActivate.3	29 Oct 2004 22:16:59 -0000	1.5
@@ -20,5 +20,6 @@
 You can feed events to \fBgicFeatureHandleEvent()\fR to activate the relevant
 callbacks. However, usually one uses \fBgicContextHandleEvent()\fR.
 .SH RETURN VALUE
+TODO Write something useful here
 .SH SEE ALSO
 \fBgicContextHandleEvent(3)\fR

Index: gicFeatureAllocate.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicFeatureAllocate.3,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- gicFeatureAllocate.3	28 Oct 2004 05:31:13 -0000	1.3
+++ gicFeatureAllocate.3	29 Oct 2004 22:17:00 -0000	1.4
@@ -15,4 +15,5 @@
 .SH DESCRIPTION
 TODO Write something useful here
 .SH RETURN VALUE
+TODO Write something useful here
 .SH SEE ALSO

Index: gicFeatureAttachRecognizerDriver.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicFeatureAttachRecognizerDriver.3,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- gicFeatureAttachRecognizerDriver.3	28 Oct 2004 05:31:13 -0000	1.3
+++ gicFeatureAttachRecognizerDriver.3	29 Oct 2004 22:17:00 -0000	1.4
@@ -23,4 +23,5 @@
 .SH DESCRIPTION
 TODO Write something useful here
 .SH RETURN VALUE
+TODO Write something useful here
 .SH SEE ALSO

Index: gicFeatureMapActions.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicFeatureMapActions.3,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- gicFeatureMapActions.3	28 Oct 2004 05:31:13 -0000	1.3
+++ gicFeatureMapActions.3	29 Oct 2004 22:17:00 -0000	1.4
@@ -21,4 +21,5 @@
 In learning-mode, \fBgicFeatureFindConflict()\fR is useful to check, if there are
 conflicting features.
 .SH RETURN VALUE
+TODO Write something useful here
 .SH SEE ALSO

Index: gicFeatureWrite.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicFeatureWrite.3,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- gicFeatureWrite.3	28 Oct 2004 05:31:13 -0000	1.3
+++ gicFeatureWrite.3	29 Oct 2004 22:17:00 -0000	1.4
@@ -18,5 +18,6 @@
 return a feature if successful. Afterwards \fBgicFeatureMapActions()\fR should be
 called to reestablish the mapping between actions and callbacks.
 .SH RETURN VALUE
+TODO Write something useful here
 .SH SEE ALSO
 \fBgicFeatureMapActions(3)\fR

Index: gicOpen.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicOpen.3,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- gicOpen.3	28 Oct 2004 05:31:13 -0000	1.4
+++ gicOpen.3	29 Oct 2004 22:17:00 -0000	1.5
@@ -1,6 +1,6 @@
 .TH "gicOpen" 3 "2004-10-28" "libgiigic-current" GGI
 .SH NAME
-\fBgicOpen\fR, \fBgicClose\fR : Open and close a recogzizer
+\fBgicOpen\fR, \fBgicClose\fR : Open and close a recognizer
 .SH SYNOPSIS
 .nb
 .nf

Index: gicRecognizerWrite.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicRecognizerWrite.3,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- gicRecognizerWrite.3	28 Oct 2004 05:31:13 -0000	1.3
+++ gicRecognizerWrite.3	29 Oct 2004 22:17:00 -0000	1.4
@@ -12,6 +12,8 @@
 
 .SH DESCRIPTION
 Writes out a dump of the recognizer into the given file.
+
+TODO Write something useful here - be more verbose
 .SH RETURN VALUE
 \fBgicRecognizerWrite\fR returns \fB0\fR for success, otherwise an error code.
 .SH SEE ALSO

Update of /cvsroot/ggi/ggi-libs/libgiigic/doc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv367

Modified Files:
	libgiigic-functions.txt 
Log Message:
typo fix: recogzizer -> recognizer. Spotted by neiljp

Index: libgiigic-functions.txt
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/libgiigic-functions.txt,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- libgiigic-functions.txt	28 Oct 2004 06:01:04 -0000	1.8
+++ libgiigic-functions.txt	29 Oct 2004 22:13:47 -0000	1.9
@@ -85,7 +85,7 @@
 
 
 
-Open and close a recogzizer
+Open and close a recognizer
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. manpage:: 3 gicOpen gicClose

Update of /cvsroot/ggi/ggi-libs/libgiigic/doc/man
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv10083

Modified Files:
      Tag: branch-1-0
	gicContextAllocate.3 gicControlAllocate.3 gicFeatureActivate.3 
	gicFeatureAttachAction.3 gicFeatureMapActions.3 
	gicFeatureWrite.3 gicHeadAllocate.3 
Log Message:
regenerate manpages for pulling up revisions 1.5 - 1.7 of libgiigic-functions.txt

Index: gicContextAllocate.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicContextAllocate.3,v
retrieving revision 1.1.2.3
retrieving revision 1.1.2.4
diff -u -d -r1.1.2.3 -r1.1.2.4
--- gicContextAllocate.3	20 Oct 2004 23:16:33 -0000	1.1.2.3
+++ gicContextAllocate.3	29 Oct 2004 20:25:28 -0000	1.1.2.4
@@ -40,42 +40,52 @@
 It can have multiple subobjects (called features) that can further
 break that down (e.g. into up/down/left/right).
 
-Most applications will not need to handle that themselves. gicHeadRead()
+Most applications will not need to handle that themselves. \fBgicHeadRead()\fR
 will provide all they need. For those that want to build up contexts
 themselves, the following functions are provided:
 
-To allocate a new gic_context, call gicContextAllocate(). To free a
-context that is not needed anymore, call gicContextFree().
+To allocate a new gic_context, call \fBgicContextAllocate()\fR. To free a
+context that is not needed anymore, call \fBgicContextFree()\fR.
 
-gicContextAttachControl() and gicContextDetachControl() are used to 
+\fBgicContextAttachControl()\fR and \fBgicContextDetachControl()\fR are used to 
 attach and detach controls from a context. A control refers to a 
 collection of features that describe a common motion. Most contexts 
 will have multiple such controls, like one for sliding and one for
 turning a player.
 
-gicContextLookupControl() and gicContextGetControl() can be used to get 
+\fBgicContextLookupControl()\fR and \fBgicContextGetControl()\fR can be used to get 
 access to controls attached to a context. The former accesses the controls 
-by name, the latter by number. You can use gicContextNumControls() to 
+by name, the latter by number. You can use \fBgicContextNumControls()\fR to 
 query for the number of controls.
 
-gicContextGetName() can be used to query for the name of a context.
+\fBgicContextGetName()\fR can be used to query for the name of a context.
 
-gicContextWrite() writes a description of the context given to the given
-file. It can be read back with gicContextRead() which will allocate and
-return context if successful. Afterwards gicContextMapActions() should be
+\fBgicContextWrite()\fR writes a description of the context given to the given
+file. It can be read back with \fBgicContextRead()\fR which will allocate and
+return context if successful. Afterwards \fBgicContextMapActions()\fR should be
 called to reestablish the mapping between actions and callbacks.
 
-In learning-mode, gicContextFindConflict() is useful to check, if there are
+In learning-mode, \fBgicContextFindConflict()\fR is useful to check, if there are
 conflicting controls.
 
 When the context is active, you feed it with events using
-gicContextHandleEvent() which will cause it to activate the relevant
+\fBgicContextHandleEvent()\fR which will cause it to activate the relevant
 callbacks.
 
 When an application is in a context, you should feed the events to 
-gicContextHandleEvent() to activate the relevant
+\fBgicContextHandleEvent()\fR to activate the relevant
 callbacks.
-
-TODO Write more here
 .SH RETURN VALUE
+\fBgicContextRead()\fR and \fBgicContextAllocate()\fR return the read/allocated 
+context on return or NULL on failure.
+
+\fBgicContextAttachControl()\fR, \fBgicContextDetachControl()\fR, \fBgicContextWrite()\fR
+and \fBgicContextMapActions()\fR return 0 on success and an error code on failure.
+
+\fBgicContextLookupControl()\fR and \fBgicContextGetControl()\fR return the requested 
+control or NULL on failure.
+
+\fBgicContextNumControls()\fR return the number of controls attached to the 
+context.
 .SH SEE ALSO
+\fBgicHeadRead(3)\fR

Index: gicControlAllocate.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicControlAllocate.3,v
retrieving revision 1.1.2.3
retrieving revision 1.1.2.4
diff -u -d -r1.1.2.3 -r1.1.2.4
--- gicControlAllocate.3	20 Oct 2004 23:16:33 -0000	1.1.2.3
+++ gicControlAllocate.3	29 Oct 2004 20:25:28 -0000	1.1.2.4
@@ -35,36 +35,46 @@
 .fi
 
 .SH DESCRIPTION
-A gic_control is libgiigic's notion of a collection of things that control a
+A gic_control is LIBGIIGIC's notion of a collection of things that control a
 motion or similar.
 
 Usually applications do not need to handle this themselves.
 
-To allocate a new gic_control, call gicControlAllocate(). To free a
-context that is not needed anymore, call gicControlFree().
+To allocate a new gic_control, call \fBgicControlAllocate()\fR. To free a
+context that is not needed anymore, call \fBgicControlFree()\fR.
 
-gicControlAttachFeature() and gicControlDetachFeature() are used to
+\fBgicControlAttachFeature()\fR and \fBgicControlDetachFeature()\fR are used to
 attach and detach features from a control. Multiple features like
 up/down/left/right make up a control (like sliding).
 
-gicControlLookupFeature() and gicControlGetFeature() can be used to get
+\fBgicControlLookupFeature()\fR and \fBgicControlGetFeature()\fR can be used to get
 access to features attached to a control. The former accesses the features
-by name, the latter by number. You can use gicControlNumFeatures() to
+by name, the latter by number. You can use \fBgicControlNumFeatures()\fR to
 query for the number of controls.
 
-gicControlGetName() can be used to query for the name of a control.
+\fBgicControlGetName()\fR can be used to query for the name of a control.
 
-gicControlWrite() writes a description of the control given to the given
-file. It can be read back with gicContextRead() which will allocate and
-return a control if successful. Afterwards gicControlMapActions() should be
+\fBgicControlWrite()\fR writes a description of the control given to the given
+\fBfile\fR. It can be read back with \fBgicContextRead()\fR which will allocate and
+return a control if successful. Afterwards \fBgicControlMapActions()\fR should be
 called to reestablish the mapping between actions and callbacks.
 
-In learning-mode, gicControlFindConflict() is useful to check, if there are
+In learning-mode, \fBgicControlFindConflict()\fR is useful to check, if there are
 conflicting controls.
 
-You can feed events to gicControlHandleEvent() to activate the relevant
-callbacks. However, usually one uses gicContextHandleEvent().
-
-TODO Write something useful here
+You can feed events to \fBgicControlHandleEvent()\fR to activate the relevant
+callbacks. However, usually one uses \fBgicContextHandleEvent()\fR.
 .SH RETURN VALUE
+\fBgicControlRead()\fR and \fBgicControlAllocate()\fR return the read/allocated 
+context on return or NULL on failure.
+
+\fBgicControlAttachFeature()\fR, \fBgicControlDetachFeature()\fR, \fBgicControlWrite()\fR
+and \fBgicControlMapActions()\fR return \fB0\fR on success and an error code on failure.
+
+\fBgicControlLookupFeature()\fR and \fBgicControlGetFeature()\fR return the requested 
+feature or NULL on failure.
+
+\fBgicControlNumFeatures()\fR return the number of features attached to the 
+control.
 .SH SEE ALSO
+\fBgicContextRead(3)\fR

Index: gicFeatureActivate.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicFeatureActivate.3,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -d -r1.1.2.2 -r1.1.2.3
--- gicFeatureActivate.3	20 Oct 2004 23:16:33 -0000	1.1.2.2
+++ gicFeatureActivate.3	29 Oct 2004 20:25:28 -0000	1.1.2.3
@@ -14,12 +14,11 @@
 .fi
 
 .SH DESCRIPTION
-To manually activate a feature, call gicFeatureActivate(). This will 
+To manually activate a feature, call \fBgicFeatureActivate()\fR. This will 
 activate the relevant callbacks.
 
-You can feed events to gicFeatureHandleEvent() to activate the relevant
-callbacks. However, usually one uses gicContextHandleEvent().
-
-TODO Write something useful here
+You can feed events to \fBgicFeatureHandleEvent()\fR to activate the relevant
+callbacks. However, usually one uses \fBgicContextHandleEvent()\fR.
 .SH RETURN VALUE
 .SH SEE ALSO
+\fBgicContextHandleEvent(3)\fR

Index: gicFeatureAttachAction.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicFeatureAttachAction.3,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -u -d -r1.1.2.1 -r1.1.2.2
--- gicFeatureAttachAction.3	18 Oct 2004 13:43:03 -0000	1.1.2.1
+++ gicFeatureAttachAction.3	29 Oct 2004 20:25:28 -0000	1.1.2.2
@@ -22,6 +22,10 @@
 .fi
 
 .SH DESCRIPTION
-TODO Write something useful here
+\fBgicFeatureAttachAction()\fR and \fBgicFeatureDetachAction()\fR are used to bind an
+action (i.e. a callback function) to a feature. This is usually handled
+by higher layers, which map whole sets of actions using a gic_actionlist.
 .SH RETURN VALUE
+\fBgicFeatureAttachAction()\fR and \fBgicFeatureDetachAction()\fR return 0 on success
+and an errorcode on failure.
 .SH SEE ALSO

Index: gicFeatureMapActions.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicFeatureMapActions.3,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -u -d -r1.1.2.1 -r1.1.2.2
--- gicFeatureMapActions.3	18 Oct 2004 13:43:03 -0000	1.1.2.1
+++ gicFeatureMapActions.3	29 Oct 2004 20:25:28 -0000	1.1.2.2
@@ -15,6 +15,10 @@
 .fi
 
 .SH DESCRIPTION
-TODO Write something useful here
+\fBgicFeatureMapActions()\fR is called to reestablish the connection between 
+the actions and the action callbacks.
+
+In learning-mode, \fBgicFeatureFindConflict()\fR is useful to check, if there are
+conflicting features.
 .SH RETURN VALUE
 .SH SEE ALSO

Index: gicFeatureWrite.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicFeatureWrite.3,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -u -d -r1.1.2.1 -r1.1.2.2
--- gicFeatureWrite.3	18 Oct 2004 13:43:03 -0000	1.1.2.1
+++ gicFeatureWrite.3	29 Oct 2004 20:25:28 -0000	1.1.2.2
@@ -13,6 +13,10 @@
 .fi
 
 .SH DESCRIPTION
-TODO Write something useful here
+\fBgicFeatureWrite()\fR writes a description of the feature given to the given
+file. It can be read back with \fBgicFeatureRead()\fR which will allocate and
+return a feature if successful. Afterwards \fBgicFeatureMapActions()\fR should be
+called to reestablish the mapping between actions and callbacks.
 .SH RETURN VALUE
 .SH SEE ALSO
+\fBgicFeatureMapActions(3)\fR

Index: gicHeadAllocate.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicHeadAllocate.3,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -d -r1.1.2.2 -r1.1.2.3
--- gicHeadAllocate.3	20 Oct 2004 23:16:33 -0000	1.1.2.2
+++ gicHeadAllocate.3	29 Oct 2004 20:25:28 -0000	1.1.2.3
@@ -29,7 +29,7 @@
 .fi
 
 .SH DESCRIPTION
-A gic_head is libgiigics notion of a collection of contexts. Each context
+A gic_head is LIBGIIGIC's notion of a collection of contexts. Each context
 describes the mappings between inputs and actions for a given situation 
 in a program.
 
@@ -37,41 +37,41 @@
 managed by libgiigic.
 
 Usually a program will not have to bother with most functions as it will
-read its config via gicHeadRead(). However when building apps that 
+read its config via \fBgicHeadRead()\fR. However when building apps that 
 can (re)build the configuration files, the other functions become useful.
 
-A gic_head is allocated using gicHeadAllocate(), which takes the gic handle 
+A gic_head is allocated using \fBgicHeadAllocate()\fR, which takes the gic handle 
 it will be associated with and a name for the Head. It returns the allocated 
 head or NULL on failure.
 
-gicHeadFree() frees an allocated gic_head.
+\fBgicHeadFree()\fR frees an allocated gic_head.
 
-gicHeadAttachContext() and gicHeadDetachContext() are used to attach and
+\fBgicHeadAttachContext()\fR and \fBgicHeadDetachContext()\fR are used to attach and
 detach contexts from a head. A context refers to a situation in a program
 that has an input mapping attached to it. Most programs will have multiple
 such contexts, like one for accessing the menus, one for the game mode,
 etc.
 
-gicHeadLookupContext() and gicHeadGetContext() can be used to get access to
+\fBgicHeadLookupContext()\fR and \fBgicHeadGetContext()\fR can be used to get access to
 contexts attached to a head. The former accesses the contexts by name, the
-latter by number. You can use gicHeadNumContexts() to query for the number
+latter by number. You can use \fBgicHeadNumContexts()\fR to query for the number
 of contexts.
 
-gicHeadWrite() can be used to write out a textual description of the head.
+\fBgicHeadWrite()\fR can be used to write out a textual description of the head.
 This is usually used to write out a config file after it changed.
 
-gicHeadRead() will read such a file, allocate a gic_head and fill it with
-the read data. After that, you should call gicHeadMapActions() to
+\fBgicHeadRead()\fR will read such a \fBfile\fR, allocate a gic_head and fill it with
+the read data. After that, you should call \fBgicHeadMapActions()\fR to
 reestablish the connection between the actions and the action callbacks.
 .SH RETURN VALUE
-gicHeadRead() and gicHeadAllocate() return the read/allocated head on return
+\fBgicHeadRead()\fR and \fBgicHeadAllocate()\fR return the read/allocated head on return
 or NULL on failure.
 
-gicHeadAttachContext(), gicHeadDetachContext(), gicHeadWrite() and
-gicHeadMapActions() return 0 on success and an error code on failure.
+\fBgicHeadAttachContext()\fR, \fBgicHeadDetachContext()\fR, \fBgicHeadWrite()\fR and
+\fBgicHeadMapActions()\fR return 0 on success and an error code on failure.
 
-gicHeadLookupContext() and gicHeadGetContext() return the requested context
+\fBgicHeadLookupContext()\fR and \fBgicHeadGetContext()\fR return the requested context
 or NULL on failure.
 
-gicHeadNumContexts() return the number of contexts attached to the head.
+\fBgicHeadNumContexts()\fR return the number of contexts attached to the head.
 .SH SEE ALSO

Update of /cvsroot/ggi/ggi-libs/libgiigic/doc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv8650

Modified Files:
      Tag: branch-1-0
	libgiigic-functions.txt 
Log Message:
pull up revisions 1.5 - 1.7 (requested by cegger):

rev 1.6: Added more docs, added an overview article. Still needs work WRT the
config manager stuff.
rev 1.7: do some docutil formatings - mark functions, add some manpage references in the 'See Also' section

Index: libgiigic-functions.txt
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/libgiigic-functions.txt,v
retrieving revision 1.3.2.2
retrieving revision 1.3.2.3
diff -u -d -r1.3.2.2 -r1.3.2.3
--- libgiigic-functions.txt	20 Oct 2004 23:13:14 -0000	1.3.2.2
+++ libgiigic-functions.txt	29 Oct 2004 20:20:11 -0000	1.3.2.3
@@ -476,12 +476,16 @@
 Description
 -----------
 
-TODO Write something useful here
+`gicFeatureAttachAction()` and `gicFeatureDetachAction()` are used to bind an
+action (i.e. a callback function) to a feature. This is usually handled
+by higher layers, which map whole sets of actions using a gic_actionlist.
 
 
 Return value
 ------------
 
+`gicFeatureAttachAction()` and `gicFeatureDetachAction()` return 0 on success
+and an errorcode on failure.
 
 See Also
 --------
@@ -510,8 +514,10 @@
 Description
 -----------
 
-TODO Write something useful here
-
+`gicFeatureWrite()` writes a description of the feature given to the given
+file. It can be read back with `gicFeatureRead()` which will allocate and
+return a feature if successful. Afterwards `gicFeatureMapActions()` should be
+called to reestablish the mapping between actions and callbacks.
 
 Return value
 ------------
@@ -520,6 +526,7 @@
 See Also
 --------
 
+:man:`gicFeatureMapActions(3)`
 
 
 Feature mappings
@@ -546,8 +553,11 @@
 Description
 -----------
 
-TODO Write something useful here
+`gicFeatureMapActions()` is called to reestablish the connection between 
+the actions and the action callbacks.
 
+In learning-mode, `gicFeatureFindConflict()` is useful to check, if there are
+conflicting features.
 
 Return value
 ------------
@@ -581,15 +591,11 @@
 Description
 -----------
 
-To manually activate a feature, call gicFeatureActivate(). This will 
+To manually activate a feature, call `gicFeatureActivate()`. This will 
 activate the relevant callbacks.
 
-You can feed events to gicFeatureHandleEvent() to activate the relevant
-callbacks. However, usually one uses gicContextHandleEvent().
-
-
-TODO Write something useful here
-
+You can feed events to `gicFeatureHandleEvent()` to activate the relevant
+callbacks. However, usually one uses `gicContextHandleEvent()`.
 
 Return value
 ------------
@@ -598,6 +604,7 @@
 See Also
 --------
 
+:man:`gicContextHandleEvent(3)`
 
 
 Controls
@@ -644,48 +651,58 @@
 Description
 -----------
 
-A gic_control is libgiigic's notion of a collection of things that control a
+A gic_control is LIBGIIGIC's notion of a collection of things that control a
 motion or similar.
 
 Usually applications do not need to handle this themselves.
 
-To allocate a new gic_control, call gicControlAllocate(). To free a
-context that is not needed anymore, call gicControlFree().
+To allocate a new gic_control, call `gicControlAllocate()`. To free a
+context that is not needed anymore, call `gicControlFree()`.
 
-gicControlAttachFeature() and gicControlDetachFeature() are used to
+`gicControlAttachFeature()` and `gicControlDetachFeature()` are used to
 attach and detach features from a control. Multiple features like
 up/down/left/right make up a control (like sliding).
 
-gicControlLookupFeature() and gicControlGetFeature() can be used to get
+`gicControlLookupFeature()` and `gicControlGetFeature()` can be used to get
 access to features attached to a control. The former accesses the features
-by name, the latter by number. You can use gicControlNumFeatures() to
+by name, the latter by number. You can use `gicControlNumFeatures()` to
 query for the number of controls.
 
-gicControlGetName() can be used to query for the name of a control.
+`gicControlGetName()` can be used to query for the name of a control.
 
-gicControlWrite() writes a description of the control given to the given
-file. It can be read back with gicContextRead() which will allocate and
-return a control if successful. Afterwards gicControlMapActions() should be
+`gicControlWrite()` writes a description of the control given to the given
+:p:`file`. It can be read back with `gicContextRead()` which will allocate and
+return a control if successful. Afterwards `gicControlMapActions()` should be
 called to reestablish the mapping between actions and callbacks.
 
-In learning-mode, gicControlFindConflict() is useful to check, if there are
+In learning-mode, `gicControlFindConflict()` is useful to check, if there are
 conflicting controls.
 
-You can feed events to gicControlHandleEvent() to activate the relevant
-callbacks. However, usually one uses gicContextHandleEvent().
+You can feed events to `gicControlHandleEvent()` to activate the relevant
+callbacks. However, usually one uses `gicContextHandleEvent()`.
 
 
+Return value
+------------
 
-TODO Write something useful here
+`gicControlRead()` and `gicControlAllocate()` return the read/allocated 
+context on return or NULL on failure.
 
+`gicControlAttachFeature()`, `gicControlDetachFeature()`, `gicControlWrite()`
+and `gicControlMapActions()` return `0` on success and an error code on failure.
 
-Return value
-------------
+`gicControlLookupFeature()` and `gicControlGetFeature()` return the requested 
+feature or NULL on failure.
+
+`gicControlNumFeatures()` return the number of features attached to the 
+control.
 
 
 See Also
 --------
 
+:man:`gicContextRead(3)`
+
 
 
 Contexts
@@ -737,53 +754,63 @@
 It can have multiple subobjects (called features) that can further
 break that down (e.g. into up/down/left/right).
 
-Most applications will not need to handle that themselves. gicHeadRead()
+Most applications will not need to handle that themselves. `gicHeadRead()`
 will provide all they need. For those that want to build up contexts
 themselves, the following functions are provided:
 
-To allocate a new gic_context, call gicContextAllocate(). To free a
-context that is not needed anymore, call gicContextFree().
+To allocate a new gic_context, call `gicContextAllocate()`. To free a
+context that is not needed anymore, call `gicContextFree()`.
 
-gicContextAttachControl() and gicContextDetachControl() are used to 
+`gicContextAttachControl()` and `gicContextDetachControl()` are used to 
 attach and detach controls from a context. A control refers to a 
 collection of features that describe a common motion. Most contexts 
 will have multiple such controls, like one for sliding and one for
 turning a player.
 
-gicContextLookupControl() and gicContextGetControl() can be used to get 
+`gicContextLookupControl()` and `gicContextGetControl()` can be used to get 
 access to controls attached to a context. The former accesses the controls 
-by name, the latter by number. You can use gicContextNumControls() to 
+by name, the latter by number. You can use `gicContextNumControls()` to 
 query for the number of controls.
 
-gicContextGetName() can be used to query for the name of a context.
+`gicContextGetName()` can be used to query for the name of a context.
 
-gicContextWrite() writes a description of the context given to the given
-file. It can be read back with gicContextRead() which will allocate and
-return context if successful. Afterwards gicContextMapActions() should be
+`gicContextWrite()` writes a description of the context given to the given
+file. It can be read back with `gicContextRead()` which will allocate and
+return context if successful. Afterwards `gicContextMapActions()` should be
 called to reestablish the mapping between actions and callbacks.
 
-In learning-mode, gicContextFindConflict() is useful to check, if there are
+In learning-mode, `gicContextFindConflict()` is useful to check, if there are
 conflicting controls.
 
 When the context is active, you feed it with events using
-gicContextHandleEvent() which will cause it to activate the relevant
+`gicContextHandleEvent()` which will cause it to activate the relevant
 callbacks.
 
 When an application is in a context, you should feed the events to 
-gicContextHandleEvent() to activate the relevant
+`gicContextHandleEvent()` to activate the relevant
 callbacks. 
 
 
-TODO Write more here
-
-
 Return value
 ------------
 
+`gicContextRead()` and `gicContextAllocate()` return the read/allocated 
+context on return or NULL on failure.
+
+`gicContextAttachControl()`, `gicContextDetachControl()`, `gicContextWrite()`
+and `gicContextMapActions()` return 0 on success and an error code on failure.
+
+`gicContextLookupControl()` and `gicContextGetControl()` return the requested 
+control or NULL on failure.
+
+`gicContextNumControls()` return the number of controls attached to the 
+context.
+
 
 See Also
 --------
 
+:man:`gicHeadRead(3)`
 
 
 Heads
@@ -824,7 +851,7 @@
 Description
 -----------
 
-A gic_head is libgiigics notion of a collection of contexts. Each context
+A gic_head is LIBGIIGIC's notion of a collection of contexts. Each context
 describes the mappings between inputs and actions for a given situation 
 in a program.
 
@@ -832,46 +859,46 @@
 managed by libgiigic.
 
 Usually a program will not have to bother with most functions as it will
-read its config via gicHeadRead(). However when building apps that 
+read its config via `gicHeadRead()`. However when building apps that 
 can (re)build the configuration files, the other functions become useful.
 
-A gic_head is allocated using gicHeadAllocate(), which takes the gic handle 
+A gic_head is allocated using `gicHeadAllocate()`, which takes the gic handle 
 it will be associated with and a name for the Head. It returns the allocated 
 head or NULL on failure.
 
-gicHeadFree() frees an allocated gic_head.
+`gicHeadFree()` frees an allocated gic_head.
 
-gicHeadAttachContext() and gicHeadDetachContext() are used to attach and
+`gicHeadAttachContext()` and `gicHeadDetachContext()` are used to attach and
 detach contexts from a head. A context refers to a situation in a program
 that has an input mapping attached to it. Most programs will have multiple
 such contexts, like one for accessing the menus, one for the game mode,
 etc.
 
-gicHeadLookupContext() and gicHeadGetContext() can be used to get access to
+`gicHeadLookupContext()` and `gicHeadGetContext()` can be used to get access to
 contexts attached to a head. The former accesses the contexts by name, the
-latter by number. You can use gicHeadNumContexts() to query for the number
+latter by number. You can use `gicHeadNumContexts()` to query for the number
 of contexts.
 
-gicHeadWrite() can be used to write out a textual description of the head.
+`gicHeadWrite()` can be used to write out a textual description of the head.
 This is usually used to write out a config file after it changed.
 
-gicHeadRead() will read such a file, allocate a gic_head and fill it with
-the read data. After that, you should call gicHeadMapActions() to
+`gicHeadRead()` will read such a :p:`file`, allocate a gic_head and fill it with
+the read data. After that, you should call `gicHeadMapActions()` to
 reestablish the connection between the actions and the action callbacks.
 
 Return value
 ------------
 
-gicHeadRead() and gicHeadAllocate() return the read/allocated head on return
+`gicHeadRead()` and `gicHeadAllocate()` return the read/allocated head on return
 or NULL on failure.
 
-gicHeadAttachContext(), gicHeadDetachContext(), gicHeadWrite() and
-gicHeadMapActions() return 0 on success and an error code on failure.
+`gicHeadAttachContext()`, `gicHeadDetachContext()`, `gicHeadWrite()` and
+`gicHeadMapActions()` return 0 on success and an error code on failure.
 
-gicHeadLookupContext() and gicHeadGetContext() return the requested context
+`gicHeadLookupContext()` and `gicHeadGetContext()` return the requested context
 or NULL on failure.
 
-gicHeadNumContexts() return the number of contexts attached to the head.
+`gicHeadNumContexts()` return the number of contexts attached to the head.
 
 
 See Also

Update of /cvsroot/ggi/ggi-libs/libgiigic/m4
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv2644/m4

Modified Files:
      Tag: branch-1-0
	libtool.m4 
Log Message:
apply fix requested by Peter Ekberg:

Strip the import lib and not the dll.
'make install-strip' now works on cygwin and mingw

Index: libtool.m4
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/m4/libtool.m4,v
retrieving revision 1.11
retrieving revision 1.11.2.1
diff -u -d -r1.11 -r1.11.2.1
--- libtool.m4	8 Sep 2004 14:06:16 -0000	1.11
+++ libtool.m4	29 Oct 2004 19:57:07 -0000	1.11.2.1
@@ -2058,7 +2058,10 @@
     postinstall_cmds='dlpath=`bash 2>&1 -c '\''. $dir/${file}i;echo \$dlname'\''`~
       dldir=$destdir/`dirname \$dlpath`~
       test -d \$dldir || mkdir -p \$dldir~
-      $install_prog .libs/$dlname \$dldir/$dlname'
+      $install_prog .libs/$dlname \$dldir/$dlname~
+      if test -n '\''$stripme'\'' && test -n '\''$striplib'\''; then
+        $run eval '\''$striplib \$dldir/$dlname'\'' || exit \$?;
+      fi'
     postuninstall_cmds='dldll=`bash 2>&1 -c '\''. $file; echo \$dlname'\''`~
       dlpath=$dir/\$dldll~
        $rm \$dlpath'
@@ -2070,7 +2073,10 @@
     postinstall_cmds='dlpath=`sh 2>&1 -c '\''. $dir/${file}i;echo \$dlname'\''`~
       dldir=$destdir/`dirname \$dlpath`~
       test -d \$dldir || mkdir -p \$dldir~
-      $install_prog .libs/$dlname \$dldir/$dlname'
+      $install_prog .libs/$dlname \$dldir/$dlname~
+      if test -n '\''$stripme'\'' && test -n '\''$striplib'\''; then
+        $run eval '\''$striplib \$dldir/$dlname'\'' || exit \$?;
+      fi'
     postuninstall_cmds='dldll=`sh 2>&1 -c '\''. $file; echo \$dlname'\''`~
       dlpath=$dir/\$dldll~
        $rm \$dlpath'

Update of /cvsroot/ggi/ggi-libs/libgiigic
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv2644

Modified Files:
      Tag: branch-1-0
	ltmain.sh 
Log Message:
apply fix requested by Peter Ekberg:

Strip the import lib and not the dll.
'make install-strip' now works on cygwin and mingw

Index: ltmain.sh
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/ltmain.sh,v
retrieving revision 1.10
retrieving revision 1.10.2.1
diff -u -d -r1.10 -r1.10.2.1
--- ltmain.sh	13 Aug 2004 19:11:18 -0000	1.10
+++ ltmain.sh	29 Oct 2004 19:57:06 -0000	1.10.2.1
@@ -4330,7 +4330,17 @@
 	  # Install the shared library and build the symlinks.
 	  $show "$install_prog $dir/$srcname $destdir/$realname"
 	  $run eval "$install_prog $dir/$srcname $destdir/$realname" || exit $?
-	  if test -n "$stripme" && test -n "$striplib"; then
+	  tstripme="$stripme"
+	  case $host in
+	  *-*-cygwin* | *-*-mingw* | *-*-pw32*)
+	    case $realname in
+	    *.dll.a)
+	      tstripme=""
+	      ;;
+	    esac
+	    ;;
+	  esac
+	  if test -n "$tstripme" && test -n "$striplib"; then
 	    $show "$striplib $destdir/$realname"
 	    $run eval "$striplib $destdir/$realname" || exit $?
 	  fi

Update of /cvsroot/ggi/ggi-libs/libgiigic
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23442/ggi-libs/libgiigic

Modified Files:
	configure.in genlibtool.in 
Log Message:
Zap dlopen from LT_INIT, we're not using the -dlopen or -dlpreopen libtool
flags anywhere.

Index: configure.in
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/configure.in,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -d -r1.43 -r1.44
--- configure.in	27 Oct 2004 13:23:36 -0000	1.43
+++ configure.in	28 Oct 2004 07:14:10 -0000	1.44
@@ -34,7 +34,7 @@
 AC_PROG_MAKE_SET
 AC_PROG_RANLIB
 
-LT_INIT([disable-static dlopen win32-dll])
+LT_INIT([disable-static win32-dll])
 
 dnl ========================================================================
 dnl Generate libtool

Index: genlibtool.in
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/genlibtool.in,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- genlibtool.in	27 Oct 2004 13:23:36 -0000	1.4
+++ genlibtool.in	28 Oct 2004 07:14:11 -0000	1.5
@@ -46,6 +46,6 @@
 
 AM_MAINTAINER_MODE
 
-LT_INIT([disable-static dlopen win32-dll])
+LT_INIT([disable-static win32-dll])
 
 AC_OUTPUT

Update of /cvsroot/ggi/ggi-libs/libggigpf
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23442/ggi-libs/libggigpf

Modified Files:
	configure.in genlibtool.in 
Log Message:
Zap dlopen from LT_INIT, we're not using the -dlopen or -dlpreopen libtool
flags anywhere.

Index: configure.in
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libggigpf/configure.in,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -d -r1.55 -r1.56
--- configure.in	28 Oct 2004 06:25:18 -0000	1.55
+++ configure.in	28 Oct 2004 07:14:10 -0000	1.56
@@ -57,7 +57,7 @@
 AC_PROG_MAKE_SET
 AC_PROG_RANLIB
 
-LT_INIT([disable-static dlopen win32-dll])
+LT_INIT([disable-static win32-dll])
 
 dnl ========================================================================
 dnl Generate libtool

Index: genlibtool.in
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libggigpf/genlibtool.in,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- genlibtool.in	27 Oct 2004 13:23:36 -0000	1.3
+++ genlibtool.in	28 Oct 2004 07:14:10 -0000	1.4
@@ -46,6 +46,6 @@
 
 AM_MAINTAINER_MODE
 
-LT_INIT([disable-static dlopen win32-dll])
+LT_INIT([disable-static win32-dll])
 
 AC_OUTPUT

Update of /cvsroot/ggi/ggi-libs/libggibse
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23442/ggi-libs/libggibse

Modified Files:
	genlibtool.in 
Log Message:
Zap dlopen from LT_INIT, we're not using the -dlopen or -dlpreopen libtool
flags anywhere.

Index: genlibtool.in
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libggibse/genlibtool.in,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- genlibtool.in	27 Oct 2004 13:23:35 -0000	1.3
+++ genlibtool.in	28 Oct 2004 07:14:10 -0000	1.4
@@ -46,6 +46,6 @@
 
 AM_MAINTAINER_MODE
 
-LT_INIT([disable-static dlopen win32-dll])
+LT_INIT([disable-static win32-dll])
 
 AC_OUTPUT

Update of /cvsroot/ggi/ggi-libs/libggigpf
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv15221/ggi-libs/libggigpf

Modified Files:
	configure.in 
Log Message:
Use LT_INIT instead of AM_PROG_LIBTOOL.

Index: configure.in
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libggigpf/configure.in,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -d -r1.54 -r1.55
--- configure.in	23 Oct 2004 17:46:26 -0000	1.54
+++ configure.in	28 Oct 2004 06:25:18 -0000	1.55
@@ -10,7 +10,6 @@
 AM_INIT_AUTOMAKE(libggigpf,0.2.0,-)
 
 AM_MAINTAINER_MODE
-AM_DISABLE_STATIC
 
 
 dnl ========================================================================
@@ -58,8 +57,7 @@
 AC_PROG_MAKE_SET
 AC_PROG_RANLIB
 
-AC_LIBTOOL_WIN32_DLL
-AM_PROG_LIBTOOL
+LT_INIT([disable-static dlopen win32-dll])
 
 dnl ========================================================================
 dnl Generate libtool

Update of /cvsroot/ggi/ggi-libs/libggibse
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv15221/ggi-libs/libggibse

Modified Files:
	configure.in 
Log Message:
Use LT_INIT instead of AM_PROG_LIBTOOL.

Index: configure.in
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libggibse/configure.in,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -d -r1.21 -r1.22
--- configure.in	23 Oct 2004 17:37:53 -0000	1.21
+++ configure.in	28 Oct 2004 06:25:18 -0000	1.22
@@ -10,7 +10,6 @@
 AM_INIT_AUTOMAKE(libggibse,1.0,-)
 
 AM_MAINTAINER_MODE
-AM_DISABLE_STATIC
 
 
 dnl ========================================================================
@@ -29,8 +28,7 @@
 AC_PROG_MAKE_SET
 AC_PROG_RANLIB
 
-AC_LIBTOOL_WIN32_DLL
-AM_PROG_LIBTOOL
+LT_INIT([disable-static win32-dll])
 
 dnl ========================================================================
 dnl Generate libtool

Update of /cvsroot/ggi/ggi-libs/libgiigic/doc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv11126

Modified Files:
	libgiigic-functions.txt 
Log Message:
mark places, that still need some improvements

Index: libgiigic-functions.txt
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/libgiigic-functions.txt,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- libgiigic-functions.txt	28 Oct 2004 05:15:24 -0000	1.7
+++ libgiigic-functions.txt	28 Oct 2004 06:01:04 -0000	1.8
@@ -255,6 +255,8 @@
 
 Writes out a dump of the recognizer into the given file.
 
+TODO Write something useful here - be more verbose
+
 
 Return value
 ------------
@@ -397,6 +399,8 @@
 Return value
 ------------
 
+TODO Write something useful here
+
 
 See Also
 --------
@@ -439,6 +443,8 @@
 Return value
 ------------
 
+TODO Write something useful here
+
 
 See Also
 --------
@@ -522,6 +528,8 @@
 Return value
 ------------
 
+TODO Write something useful here
+
 
 See Also
 --------
@@ -559,9 +567,12 @@
 In learning-mode, `gicFeatureFindConflict()` is useful to check, if there are
 conflicting features.
 
+
 Return value
 ------------
 
+TODO Write something useful here
+
 
 See Also
 --------
@@ -597,9 +608,12 @@
 You can feed events to `gicFeatureHandleEvent()` to activate the relevant
 callbacks. However, usually one uses `gicContextHandleEvent()`.
 
+
 Return value
 ------------
 
+TODO Write something useful here
+
 
 See Also
 --------
@@ -607,6 +621,7 @@
 :man:`gicContextHandleEvent(3)`
 
 
+
 Controls
 ~~~~~~~~
 
@@ -886,6 +901,7 @@
 the read data. After that, you should call `gicHeadMapActions()` to
 reestablish the connection between the actions and the action callbacks.
 
+
 Return value
 ------------

Update of /cvsroot/ggi/ggi-libs/libgiigic/doc/man
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv6810

Modified Files:
	gicActionWrite.3 gicContextAllocate.3 gicControlAllocate.3 
	gicFeatureActivate.3 gicFeatureAllocate.3 
	gicFeatureAttachAction.3 gicFeatureAttachRecognizerDriver.3 
	gicFeatureMapActions.3 gicFeatureWrite.3 gicHeadAllocate.3 
	gicInit.3 gicInputRegister.3 gicOpen.3 
	gicRecognizerDriverRegister.3 gicRecognizerTrain.3 
	gicRecognizerWrite.3 libgiigic.7 
Log Message:
regenerate manpages

Index: gicActionWrite.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicActionWrite.3,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- gicActionWrite.3	18 Oct 2004 15:56:33 -0000	1.2
+++ gicActionWrite.3	28 Oct 2004 05:31:13 -0000	1.3
@@ -1,4 +1,4 @@
-.TH "gicActionWrite" 3 "2004-10-17" "libgiigic-current" GGI
+.TH "gicActionWrite" 3 "2004-10-28" "libgiigic-current" GGI
 .SH NAME
 \fBgicActionWrite\fR, \fBgicActionMapActions\fR : Action handling
 .SH SYNOPSIS

Index: gicContextAllocate.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicContextAllocate.3,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- gicContextAllocate.3	19 Oct 2004 14:13:53 -0000	1.3
+++ gicContextAllocate.3	28 Oct 2004 05:31:13 -0000	1.4
@@ -1,4 +1,4 @@
-.TH "gicContextAllocate" 3 "2004-10-17" "libgiigic-current" GGI
+.TH "gicContextAllocate" 3 "2004-10-28" "libgiigic-current" GGI
 .SH NAME
 \fBgicContextAllocate\fR, \fBgicContextFree\fR, \fBgicContextAttachControl\fR, \fBgicContextDetachControl\fR, \fBgicContextLookupControl\fR, \fBgicContextGetControl\fR, \fBgicContextNumControls\fR, \fBgicContextGetName\fR, \fBgicContextWrite\fR, \fBgicContextRead\fR, \fBgicContextMapActions\fR, \fBgicContextFindConflict\fR, \fBgicContextHandleEvent\fR : Contexts
 .SH SYNOPSIS
@@ -40,42 +40,52 @@
 It can have multiple subobjects (called features) that can further
 break that down (e.g. into up/down/left/right).
 
-Most applications will not need to handle that themselves. gicHeadRead()
+Most applications will not need to handle that themselves. \fBgicHeadRead()\fR
 will provide all they need. For those that want to build up contexts
 themselves, the following functions are provided:
 
-To allocate a new gic_context, call gicContextAllocate(). To free a
-context that is not needed anymore, call gicContextFree().
+To allocate a new gic_context, call \fBgicContextAllocate()\fR. To free a
+context that is not needed anymore, call \fBgicContextFree()\fR.
 
-gicContextAttachControl() and gicContextDetachControl() are used to 
+\fBgicContextAttachControl()\fR and \fBgicContextDetachControl()\fR are used to 
 attach and detach controls from a context. A control refers to a 
 collection of features that describe a common motion. Most contexts 
 will have multiple such controls, like one for sliding and one for
 turning a player.
 
-gicContextLookupControl() and gicContextGetControl() can be used to get 
+\fBgicContextLookupControl()\fR and \fBgicContextGetControl()\fR can be used to get 
 access to controls attached to a context. The former accesses the controls 
-by name, the latter by number. You can use gicContextNumControls() to 
+by name, the latter by number. You can use \fBgicContextNumControls()\fR to 
 query for the number of controls.
 
-gicContextGetName() can be used to query for the name of a context.
+\fBgicContextGetName()\fR can be used to query for the name of a context.
 
-gicContextWrite() writes a description of the context given to the given
-file. It can be read back with gicContextRead() which will allocate and
-return context if successful. Afterwards gicContextMapActions() should be
+\fBgicContextWrite()\fR writes a description of the context given to the given
+file. It can be read back with \fBgicContextRead()\fR which will allocate and
+return context if successful. Afterwards \fBgicContextMapActions()\fR should be
 called to reestablish the mapping between actions and callbacks.
 
-In learning-mode, gicContextFindConflict() is useful to check, if there are
+In learning-mode, \fBgicContextFindConflict()\fR is useful to check, if there are
 conflicting controls.
 
 When the context is active, you feed it with events using
-gicContextHandleEvent() which will cause it to activate the relevant
+\fBgicContextHandleEvent()\fR which will cause it to activate the relevant
 callbacks.
 
 When an application is in a context, you should feed the events to 
-gicContextHandleEvent() to activate the relevant
+\fBgicContextHandleEvent()\fR to activate the relevant
 callbacks.
-
-TODO Write more here
 .SH RETURN VALUE
+\fBgicContextRead()\fR and \fBgicContextAllocate()\fR return the read/allocated 
+context on return or NULL on failure.
+
+\fBgicContextAttachControl()\fR, \fBgicContextDetachControl()\fR, \fBgicContextWrite()\fR
+and \fBgicContextMapActions()\fR return 0 on success and an error code on failure.
+
+\fBgicContextLookupControl()\fR and \fBgicContextGetControl()\fR return the requested 
+control or NULL on failure.
+
+\fBgicContextNumControls()\fR return the number of controls attached to the 
+context.
 .SH SEE ALSO
+\fBgicHeadRead(3)\fR

Index: gicControlAllocate.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicControlAllocate.3,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- gicControlAllocate.3	19 Oct 2004 14:13:53 -0000	1.3
+++ gicControlAllocate.3	28 Oct 2004 05:31:13 -0000	1.4
@@ -1,4 +1,4 @@
-.TH "gicControlAllocate" 3 "2004-10-17" "libgiigic-current" GGI
+.TH "gicControlAllocate" 3 "2004-10-28" "libgiigic-current" GGI
 .SH NAME
 \fBgicControlAllocate\fR, \fBgicControlFree\fR, \fBgicControlAttachFeature\fR, \fBgicControlDetachFeature\fR, \fBgicControlLookupFeature\fR, \fBgicControlGetFeature\fR, \fBgicControlNumFeatures\fR, \fBgicControlGetName\fR, \fBgicControlWrite\fR, \fBgicControlRead\fR, \fBgicControlMapActions\fR, \fBgicControlFindConflict\fR, \fBgicControlHandleEvent\fR : Controls
 .SH SYNOPSIS
@@ -35,36 +35,46 @@
 .fi
 
 .SH DESCRIPTION
-A gic_control is libgiigic's notion of a collection of things that control a
+A gic_control is LIBGIIGIC's notion of a collection of things that control a
 motion or similar.
 
 Usually applications do not need to handle this themselves.
 
-To allocate a new gic_control, call gicControlAllocate(). To free a
-context that is not needed anymore, call gicControlFree().
+To allocate a new gic_control, call \fBgicControlAllocate()\fR. To free a
+context that is not needed anymore, call \fBgicControlFree()\fR.
 
-gicControlAttachFeature() and gicControlDetachFeature() are used to
+\fBgicControlAttachFeature()\fR and \fBgicControlDetachFeature()\fR are used to
 attach and detach features from a control. Multiple features like
 up/down/left/right make up a control (like sliding).
 
-gicControlLookupFeature() and gicControlGetFeature() can be used to get
+\fBgicControlLookupFeature()\fR and \fBgicControlGetFeature()\fR can be used to get
 access to features attached to a control. The former accesses the features
-by name, the latter by number. You can use gicControlNumFeatures() to
+by name, the latter by number. You can use \fBgicControlNumFeatures()\fR to
 query for the number of controls.
 
-gicControlGetName() can be used to query for the name of a control.
+\fBgicControlGetName()\fR can be used to query for the name of a control.
 
-gicControlWrite() writes a description of the control given to the given
-file. It can be read back with gicContextRead() which will allocate and
-return a control if successful. Afterwards gicControlMapActions() should be
+\fBgicControlWrite()\fR writes a description of the control given to the given
+\fBfile\fR. It can be read back with \fBgicContextRead()\fR which will allocate and
+return a control if successful. Afterwards \fBgicControlMapActions()\fR should be
 called to reestablish the mapping between actions and callbacks.
 
-In learning-mode, gicControlFindConflict() is useful to check, if there are
+In learning-mode, \fBgicControlFindConflict()\fR is useful to check, if there are
 conflicting controls.
 
-You can feed events to gicControlHandleEvent() to activate the relevant
-callbacks. However, usually one uses gicContextHandleEvent().
-
-TODO Write something useful here
+You can feed events to \fBgicControlHandleEvent()\fR to activate the relevant
+callbacks. However, usually one uses \fBgicContextHandleEvent()\fR.
 .SH RETURN VALUE
+\fBgicControlRead()\fR and \fBgicControlAllocate()\fR return the read/allocated 
+context on return or NULL on failure.
+
+\fBgicControlAttachFeature()\fR, \fBgicControlDetachFeature()\fR, \fBgicControlWrite()\fR
+and \fBgicControlMapActions()\fR return \fB0\fR on success and an error code on failure.
+
+\fBgicControlLookupFeature()\fR and \fBgicControlGetFeature()\fR return the requested 
+feature or NULL on failure.
+
+\fBgicControlNumFeatures()\fR return the number of features attached to the 
+control.
 .SH SEE ALSO
+\fBgicContextRead(3)\fR

Index: gicFeatureActivate.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicFeatureActivate.3,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- gicFeatureActivate.3	19 Oct 2004 14:13:54 -0000	1.3
+++ gicFeatureActivate.3	28 Oct 2004 05:31:13 -0000	1.4
@@ -1,4 +1,4 @@
-.TH "gicFeatureActivate" 3 "2004-10-17" "libgiigic-current" GGI
+.TH "gicFeatureActivate" 3 "2004-10-28" "libgiigic-current" GGI
 .SH NAME
 \fBgicFeatureActivate\fR, \fBgicFeatureHandleEvent\fR : Event handling
 .SH SYNOPSIS
@@ -14,12 +14,11 @@
 .fi
 
 .SH DESCRIPTION
-To manually activate a feature, call gicFeatureActivate(). This will 
+To manually activate a feature, call \fBgicFeatureActivate()\fR. This will 
 activate the relevant callbacks.
 
-You can feed events to gicFeatureHandleEvent() to activate the relevant
-callbacks. However, usually one uses gicContextHandleEvent().
-
-TODO Write something useful here
+You can feed events to \fBgicFeatureHandleEvent()\fR to activate the relevant
+callbacks. However, usually one uses \fBgicContextHandleEvent()\fR.
 .SH RETURN VALUE
 .SH SEE ALSO
+\fBgicContextHandleEvent(3)\fR

Index: gicFeatureAllocate.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicFeatureAllocate.3,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- gicFeatureAllocate.3	18 Oct 2004 15:56:34 -0000	1.2
+++ gicFeatureAllocate.3	28 Oct 2004 05:31:13 -0000	1.3
@@ -1,4 +1,4 @@
-.TH "gicFeatureAllocate" 3 "2004-10-17" "libgiigic-current" GGI
+.TH "gicFeatureAllocate" 3 "2004-10-28" "libgiigic-current" GGI
 .SH NAME
 \fBgicFeatureAllocate\fR, \fBgicFeatureFree\fR : Allocate Features
 .SH SYNOPSIS

Index: gicFeatureAttachAction.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicFeatureAttachAction.3,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- gicFeatureAttachAction.3	18 Oct 2004 15:56:34 -0000	1.2
+++ gicFeatureAttachAction.3	28 Oct 2004 05:31:13 -0000	1.3
@@ -1,4 +1,4 @@
-.TH "gicFeatureAttachAction" 3 "2004-10-17" "libgiigic-current" GGI
+.TH "gicFeatureAttachAction" 3 "2004-10-28" "libgiigic-current" GGI
 .SH NAME
 \fBgicFeatureAttachAction\fR, \fBgicFeatureDetachAction\fR, \fBgicFeatureWrite\fR, \fBgicFeatureRead\fR : Bind Features and Actions
 .SH SYNOPSIS
@@ -22,6 +22,10 @@
 .fi
 
 .SH DESCRIPTION
-TODO Write something useful here
+\fBgicFeatureAttachAction()\fR and \fBgicFeatureDetachAction()\fR are used to bind an
+action (i.e. a callback function) to a feature. This is usually handled
+by higher layers, which map whole sets of actions using a gic_actionlist.
 .SH RETURN VALUE
+\fBgicFeatureAttachAction()\fR and \fBgicFeatureDetachAction()\fR return 0 on success
+and an errorcode on failure.
 .SH SEE ALSO

Index: gicFeatureAttachRecognizerDriver.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicFeatureAttachRecognizerDriver.3,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- gicFeatureAttachRecognizerDriver.3	18 Oct 2004 15:56:34 -0000	1.2
+++ gicFeatureAttachRecognizerDriver.3	28 Oct 2004 05:31:13 -0000	1.3
@@ -1,4 +1,4 @@
-.TH "gicFeatureAttachRecognizerDriver" 3 "2004-10-17" "libgiigic-current" GGI
+.TH "gicFeatureAttachRecognizerDriver" 3 "2004-10-28" "libgiigic-current" GGI
 .SH NAME
 \fBgicFeatureAttachRecognizerDriver\fR, \fBgicFeatureAttachRecognizer\fR, \fBgicFeatureDetachRecognizer\fR, \fBgicFeatureGetRecognizer\fR, \fBgicFeatureNumRecognizers\fR, \fBgicFeatureGetName\fR : Bind Features with Recognizers
 .SH SYNOPSIS

Index: gicFeatureMapActions.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicFeatureMapActions.3,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- gicFeatureMapActions.3	18 Oct 2004 15:56:34 -0000	1.2
+++ gicFeatureMapActions.3	28 Oct 2004 05:31:13 -0000	1.3
@@ -1,4 +1,4 @@
-.TH "gicFeatureMapActions" 3 "2004-10-17" "libgiigic-current" GGI
+.TH "gicFeatureMapActions" 3 "2004-10-28" "libgiigic-current" GGI
 .SH NAME
 \fBgicFeatureMapActions\fR, \fBgicFeatureFindConflict\fR : Feature mappings
 .SH SYNOPSIS
@@ -15,6 +15,10 @@
 .fi
 
 .SH DESCRIPTION
-TODO Write something useful here
+\fBgicFeatureMapActions()\fR is called to reestablish the connection between 
+the actions and the action callbacks.
+
+In learning-mode, \fBgicFeatureFindConflict()\fR is useful to check, if there are
+conflicting features.
 .SH RETURN VALUE
 .SH SEE ALSO

Index: gicFeatureWrite.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicFeatureWrite.3,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- gicFeatureWrite.3	18 Oct 2004 15:56:34 -0000	1.2
+++ gicFeatureWrite.3	28 Oct 2004 05:31:13 -0000	1.3
@@ -1,4 +1,4 @@
-.TH "gicFeatureWrite" 3 "2004-10-17" "libgiigic-current" GGI
+.TH "gicFeatureWrite" 3 "2004-10-28" "libgiigic-current" GGI
 .SH NAME
 \fBgicFeatureWrite\fR, \fBgicFeatureRead\fR : Load and Save Feature
 .SH SYNOPSIS
@@ -13,6 +13,10 @@
 .fi
 
 .SH DESCRIPTION
-TODO Write something useful here
+\fBgicFeatureWrite()\fR writes a description of the feature given to the given
+file. It can be read back with \fBgicFeatureRead()\fR which will allocate and
+return a feature if successful. Afterwards \fBgicFeatureMapActions()\fR should be
+called to reestablish the mapping between actions and callbacks.
 .SH RETURN VALUE
 .SH SEE ALSO
+\fBgicFeatureMapActions(3)\fR

Index: gicHeadAllocate.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicHeadAllocate.3,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- gicHeadAllocate.3	19 Oct 2004 14:13:54 -0000	1.3
+++ gicHeadAllocate.3	28 Oct 2004 05:31:13 -0000	1.4
@@ -1,4 +1,4 @@
-.TH "gicHeadAllocate" 3 "2004-10-17" "libgiigic-current" GGI
+.TH "gicHeadAllocate" 3 "2004-10-28" "libgiigic-current" GGI
 .SH NAME
 \fBgicHeadAllocate\fR, \fBgicHeadFree\fR, \fBgicHeadAttachContext\fR, \fBgicHeadDetachContext\fR, \fBgicHeadLookupContext\fR, \fBgicHeadGetContext\fR, \fBgicHeadNumContexts\fR, \fBgicHeadWrite\fR, \fBgicHeadRead\fR, \fBgicHeadMapActions\fR : Heads
 .SH SYNOPSIS
@@ -29,7 +29,7 @@
 .fi
 
 .SH DESCRIPTION
-A gic_head is libgiigics notion of a collection of contexts. Each context
+A gic_head is LIBGIIGIC's notion of a collection of contexts. Each context
 describes the mappings between inputs and actions for a given situation 
 in a program.
 
@@ -37,41 +37,41 @@
 managed by libgiigic.
 
 Usually a program will not have to bother with most functions as it will
-read its config via gicHeadRead(). However when building apps that 
+read its config via \fBgicHeadRead()\fR. However when building apps that 
 can (re)build the configuration files, the other functions become useful.
 
-A gic_head is allocated using gicHeadAllocate(), which takes the gic handle 
+A gic_head is allocated using \fBgicHeadAllocate()\fR, which takes the gic handle 
 it will be associated with and a name for the Head. It returns the allocated 
 head or NULL on failure.
 
-gicHeadFree() frees an allocated gic_head.
+\fBgicHeadFree()\fR frees an allocated gic_head.
 
-gicHeadAttachContext() and gicHeadDetachContext() are used to attach and
+\fBgicHeadAttachContext()\fR and \fBgicHeadDetachContext()\fR are used to attach and
 detach contexts from a head. A context refers to a situation in a program
 that has an input mapping attached to it. Most programs will have multiple
 such contexts, like one for accessing the menus, one for the game mode,
 etc.
 
-gicHeadLookupContext() and gicHeadGetContext() can be used to get access to
+\fBgicHeadLookupContext()\fR and \fBgicHeadGetContext()\fR can be used to get access to
 contexts attached to a head. The former accesses the contexts by name, the
-latter by number. You can use gicHeadNumContexts() to query for the number
+latter by number. You can use \fBgicHeadNumContexts()\fR to query for the number
 of contexts.
 
-gicHeadWrite() can be used to write out a textual description of the head.
+\fBgicHeadWrite()\fR can be used to write out a textual description of the head.
 This is usually used to write out a config file after it changed.
 
-gicHeadRead() will read such a file, allocate a gic_head and fill it with
-the read data. After that, you should call gicHeadMapActions() to
+\fBgicHeadRead()\fR will read such a \fBfile\fR, allocate a gic_head and fill it with
+the read data. After that, you should call \fBgicHeadMapActions()\fR to
 reestablish the connection between the actions and the action callbacks.
 .SH RETURN VALUE
-gicHeadRead() and gicHeadAllocate() return the read/allocated head on return
+\fBgicHeadRead()\fR and \fBgicHeadAllocate()\fR return the read/allocated head on return
 or NULL on failure.
 
-gicHeadAttachContext(), gicHeadDetachContext(), gicHeadWrite() and
-gicHeadMapActions() return 0 on success and an error code on failure.
+\fBgicHeadAttachContext()\fR, \fBgicHeadDetachContext()\fR, \fBgicHeadWrite()\fR and
+\fBgicHeadMapActions()\fR return 0 on success and an error code on failure.
 
-gicHeadLookupContext() and gicHeadGetContext() return the requested context
+\fBgicHeadLookupContext()\fR and \fBgicHeadGetContext()\fR return the requested context
 or NULL on failure.
 
-gicHeadNumContexts() return the number of contexts attached to the head.
+\fBgicHeadNumContexts()\fR return the number of contexts attached to the head.
 .SH SEE ALSO

Index: gicInit.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicInit.3,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- gicInit.3	18 Oct 2004 15:56:34 -0000	1.3
+++ gicInit.3	28 Oct 2004 05:31:13 -0000	1.4
@@ -1,4 +1,4 @@
-.TH "gicInit" 3 "2004-10-17" "libgiigic-current" GGI
+.TH "gicInit" 3 "2004-10-28" "libgiigic-current" GGI
 .SH NAME
 \fBgicInit\fR, \fBgiiExit\fR : Initialize and uninitialize LibGIIGIC
 .SH SYNOPSIS

Index: gicInputRegister.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicInputRegister.3,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- gicInputRegister.3	18 Oct 2004 15:56:34 -0000	1.2
+++ gicInputRegister.3	28 Oct 2004 05:31:13 -0000	1.3
@@ -1,4 +1,4 @@
-.TH "gicInputRegister" 3 "2004-10-17" "libgiigic-current" GGI
+.TH "gicInputRegister" 3 "2004-10-28" "libgiigic-current" GGI
 .SH NAME
 \fBgicInputRegister\fR : Associate a gii handle with gic
 .SH SYNOPSIS

Index: gicOpen.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicOpen.3,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- gicOpen.3	18 Oct 2004 15:56:34 -0000	1.3
+++ gicOpen.3	28 Oct 2004 05:31:13 -0000	1.4
@@ -1,4 +1,4 @@
-.TH "gicOpen" 3 "2004-10-17" "libgiigic-current" GGI
+.TH "gicOpen" 3 "2004-10-28" "libgiigic-current" GGI
 .SH NAME
 \fBgicOpen\fR, \fBgicClose\fR : Open and close a recogzizer
 .SH SYNOPSIS

Index: gicRecognizerDriverRegister.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicRecognizerDriverRegister.3,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- gicRecognizerDriverRegister.3	18 Oct 2004 15:56:34 -0000	1.3
+++ gicRecognizerDriverRegister.3	28 Oct 2004 05:31:13 -0000	1.4
@@ -1,4 +1,4 @@
-.TH "gicRecognizerDriverRegister" 3 "2004-10-17" "libgiigic-current" GGI
+.TH "gicRecognizerDriverRegister" 3 "2004-10-28" "libgiigic-current" GGI
 .SH NAME
 \fBgicRecognizerDriverRegister\fR, \fBgicRecognizerDriverUnregister\fR, \fBgicRecognizerDriverLookup\fR : Adjust Recognizers
 .SH SYNOPSIS

Index: gicRecognizerTrain.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicRecognizerTrain.3,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- gicRecognizerTrain.3	18 Oct 2004 15:56:34 -0000	1.2
+++ gicRecognizerTrain.3	28 Oct 2004 05:31:13 -0000	1.3
@@ -1,4 +1,4 @@
-.TH "gicRecognizerTrain" 3 "2004-10-17" "libgiigic-current" GGI
+.TH "gicRecognizerTrain" 3 "2004-10-28" "libgiigic-current" GGI
 .SH NAME
 \fBgicRecognizerTrain\fR, \fBgicRecognizerTrainStart\fR, \fBgicRecognizerTrainStop\fR, \fBgicRecognizerTrainAdd\fR, \fBgicRecognizerTrainMove\fR, \fBgicRecognizerFindConflict\fR, \fBgicRecognizerGetName\fR, \fBgicRecognizerGetOpposite\fR : Train recognizers
 .SH SYNOPSIS

Index: gicRecognizerWrite.3
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/gicRecognizerWrite.3,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- gicRecognizerWrite.3	18 Oct 2004 15:56:34 -0000	1.2
+++ gicRecognizerWrite.3	28 Oct 2004 05:31:13 -0000	1.3
@@ -1,4 +1,4 @@
-.TH "gicRecognizerWrite" 3 "2004-10-17" "libgiigic-current" GGI
+.TH "gicRecognizerWrite" 3 "2004-10-28" "libgiigic-current" GGI
 .SH NAME
 \fBgicRecognizerWrite\fR : Recognizer dump
 .SH SYNOPSIS

Index: libgiigic.7
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/man/libgiigic.7,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- libgiigic.7	27 Oct 2004 12:47:16 -0000	1.5
+++ libgiigic.7	28 Oct 2004 05:31:13 -0000	1.6
@@ -1,4 +1,4 @@
-.TH "libgiigic" 7 "2004-10-17" "libgiigic-current" GGI
+.TH "libgiigic" 7 "2004-10-28" "libgiigic-current" GGI
 .SH NAME
 \fBlibgiigic\fR : A flexible library for action/event binding
 .SH DESCRIPTION

Update of /cvsroot/ggi/ggi-libs/libgiigic/doc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv5791

Modified Files:
	libgiigic-overview.txt 
Log Message:
docutil formatings: literal blocks are indented and start with ::

Index: libgiigic-overview.txt
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/libgiigic-overview.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- libgiigic-overview.txt	27 Oct 2004 23:38:40 -0000	1.1
+++ libgiigic-overview.txt	28 Oct 2004 05:25:06 -0000	1.2
@@ -84,10 +84,10 @@
 future expansion. When you are done with it, free the allocated handle using
 gicClose(handle).
 
-If you have an existing configuration file, you just read it:
+If you have an existing configuration file, you just read it::
 
-        config=fopen("demo.gic","r");                                           
-        head=gicHeadRead(handle,config);                                        
+        config = fopen("demo.gic", "r");                                           
+        head = gicHeadRead(handle, config);                                        
         fclose(config);                                                         
 
 Simple - right?
@@ -105,9 +105,9 @@
 However, you will usually work with contexts, as the application will
 normally enter different states associated with gic_contexts.
 
-You can extract the contexts from the head like this:
+You can extract the contexts from the head like this::
 
-menu=gicHeadLookupContext(handle,head,"Menu context");                  
+	menu = gicHeadLookupContext(handle, head, "Menu context");                  
 
 
 Now we have one point at needs to be cleaned up: The file also stores
@@ -119,13 +119,13 @@
 connection between a symbolic name of the action, and the actual callback
 function. This mapping is stored in a variable of type gic_actionlist.
 
-A sample list would be:
+A sample list would be::
 
-gic_actionlist actionmapping[]= {                                               
+  gic_actionlist actionmapping[]= {                                               
         {NULL,"mynextaction",   my_action,      NULL},                          
         {NULL,"myprevaction",   my_action2,     (void *)0x12345678},            
         {NULL,NULL,NULL,NULL}                                                   
-};                                                                              
+  };                                                                              
 
 The first element of each gic_actionlist-entry here is reserved for a
 chaining pointer and always NULL.
@@ -138,9 +138,9 @@
 purposes, which makes a lot of sense, as many callback functions are usually
 very similar.
 
-You can now re-map the actions using this call:
+You can now re-map the actions using this call::
 
-gicHeadMapActions(handle,head,actionmapping);
+  gicHeadMapActions(handle,head,actionmapping);
 
 This will cause LibGIIGIC to iterate through the head and its child objects
 and find any actions attached. If the action names match a name in the
@@ -150,9 +150,9 @@
 gii_event from LibGII (oder LibGGI which uses LibGII for input), or build
 one yourself, if you insist not to use LibGII.
 
-You can then feed the event to LibGIIGIC using
+You can then feed the event to LibGIIGIC using::
 
-gicContextHandleEvent(handle,menu, &event);
+  gicContextHandleEvent(handle,menu, &event);
 
 Note, that it does not make sense to send an event to a head, as the event
 might have different meanings depending on context. So you just feed it to
@@ -173,9 +173,9 @@
 If a recognizer triggers, it will activate the feature it is attached to,
 which will in turn call the actions bound to it.
 
-Action functions have the following prototype:
+Action functions have the following prototype::
 
-void my_action(gic_handle_t hand, gic_actionlist *action,
+  void my_action(gic_handle_t hand, gic_actionlist *action,
 	gic_feature *feature, gic_state newstate,gic_flag flag,
 	int recnum) 
 
@@ -237,11 +237,11 @@
 
 The privdata field must point to a gicActionLazyData variable.
 
-When using the Lazy action helpers, you usually do something like this:
+When using the Lazy action helpers, you usually do something like this::
 
-ggiEventRead(vis,&event,emAll);		/* get an event. */
-/* Let LibGIC evaluate it for the menu context */
-gicContextHandleEvent(hand, menucon, &event);
+  ggiEventRead(vis,&event,emAll);		/* get an event. */
+  /* Let LibGIC evaluate it for the menu context */
+  gicContextHandleEvent(hand, menucon, &event);
 
 Now the gicActionLazyAction callbacks are run, and you can check how much
 the individual gicActionLazyData elements are active.
@@ -264,4 +264,4 @@
 
 
 Conflicts
-~~~~~~~~~
\ No newline at end of file
+~~~~~~~~~

Update of /cvsroot/ggi/ggi-libs/libgiigic/doc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv4131

Modified Files:
	libgiigic-functions.txt 
Log Message:
do some docutil formatings - mark functions, add some manpage references in the 'See Also' section

Index: libgiigic-functions.txt
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/libgiigic-functions.txt,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- libgiigic-functions.txt	27 Oct 2004 23:38:40 -0000	1.6
+++ libgiigic-functions.txt	28 Oct 2004 05:15:24 -0000	1.7
@@ -476,7 +476,7 @@
 Description
 -----------
 
-gicFeatureAttachAction() and gicFeatureDetachAction() are used to bind an
+`gicFeatureAttachAction()` and `gicFeatureDetachAction()` are used to bind an
 action (i.e. a callback function) to a feature. This is usually handled
 by higher layers, which map whole sets of actions using a gic_actionlist.
 
@@ -484,7 +484,7 @@
 Return value
 ------------
 
-gicFeatureAttachAction() and gicFeatureDetachAction() return 0 on success
+`gicFeatureAttachAction()` and `gicFeatureDetachAction()` return 0 on success
 and an errorcode on failure.
 
 See Also
@@ -514,9 +514,9 @@
 Description
 -----------
 
-gicFeatureWrite() writes a description of the feature given to the given
-file. It can be read back with gicFeatureRead() which will allocate and
-return a feature if successful. Afterwards gicFeatureMapActions() should be
+`gicFeatureWrite()` writes a description of the feature given to the given
+file. It can be read back with `gicFeatureRead()` which will allocate and
+return a feature if successful. Afterwards `gicFeatureMapActions()` should be
 called to reestablish the mapping between actions and callbacks.
 
 Return value
@@ -526,7 +526,7 @@
 See Also
 --------
 
-gicFeatureMapActions
+:man:`gicFeatureMapActions(3)`
 
 
 Feature mappings
@@ -553,10 +553,10 @@
 Description
 -----------
 
-gicFeatureMapActions() is called to reestablish the connection between 
+`gicFeatureMapActions()` is called to reestablish the connection between 
 the actions and the action callbacks.
 
-In learning-mode, gicFeatureFindConflict() is useful to check, if there are
+In learning-mode, `gicFeatureFindConflict()` is useful to check, if there are
 conflicting features.
 
 Return value
@@ -591,11 +591,11 @@
 Description
 -----------
 
-To manually activate a feature, call gicFeatureActivate(). This will 
+To manually activate a feature, call `gicFeatureActivate()`. This will 
 activate the relevant callbacks.
 
-You can feed events to gicFeatureHandleEvent() to activate the relevant
-callbacks. However, usually one uses gicContextHandleEvent().
+You can feed events to `gicFeatureHandleEvent()` to activate the relevant
+callbacks. However, usually one uses `gicContextHandleEvent()`.
 
 Return value
 ------------
@@ -604,6 +604,7 @@
 See Also
 --------
 
+:man:`gicContextHandleEvent(3)`
 
 
 Controls
@@ -650,56 +651,58 @@
 Description
 -----------
 
-A gic_control is libgiigic's notion of a collection of things that control a
+A gic_control is LIBGIIGIC's notion of a collection of things that control a
 motion or similar.
 
 Usually applications do not need to handle this themselves.
 
-To allocate a new gic_control, call gicControlAllocate(). To free a
-context that is not needed anymore, call gicControlFree().
+To allocate a new gic_control, call `gicControlAllocate()`. To free a
+context that is not needed anymore, call `gicControlFree()`.
 
-gicControlAttachFeature() and gicControlDetachFeature() are used to
+`gicControlAttachFeature()` and `gicControlDetachFeature()` are used to
 attach and detach features from a control. Multiple features like
 up/down/left/right make up a control (like sliding).
 
-gicControlLookupFeature() and gicControlGetFeature() can be used to get
+`gicControlLookupFeature()` and `gicControlGetFeature()` can be used to get
 access to features attached to a control. The former accesses the features
-by name, the latter by number. You can use gicControlNumFeatures() to
+by name, the latter by number. You can use `gicControlNumFeatures()` to
 query for the number of controls.
 
-gicControlGetName() can be used to query for the name of a control.
+`gicControlGetName()` can be used to query for the name of a control.
 
-gicControlWrite() writes a description of the control given to the given
-file. It can be read back with gicContextRead() which will allocate and
-return a control if successful. Afterwards gicControlMapActions() should be
+`gicControlWrite()` writes a description of the control given to the given
+:p:`file`. It can be read back with `gicContextRead()` which will allocate and
+return a control if successful. Afterwards `gicControlMapActions()` should be
 called to reestablish the mapping between actions and callbacks.
 
-In learning-mode, gicControlFindConflict() is useful to check, if there are
+In learning-mode, `gicControlFindConflict()` is useful to check, if there are
 conflicting controls.
 
-You can feed events to gicControlHandleEvent() to activate the relevant
-callbacks. However, usually one uses gicContextHandleEvent().
+You can feed events to `gicControlHandleEvent()` to activate the relevant
+callbacks. However, usually one uses `gicContextHandleEvent()`.
 
 
 Return value
 ------------
 
-gicControlRead() and gicControlAllocate() return the read/allocated 
+`gicControlRead()` and `gicControlAllocate()` return the read/allocated 
 context on return or NULL on failure.
 
-gicControlAttachFeature(), gicControlDetachFeature(), gicControlWrite() and
-gicControlMapActions() return 0 on success and an error code on failure.
+`gicControlAttachFeature()`, `gicControlDetachFeature()`, `gicControlWrite()`
+and `gicControlMapActions()` return `0` on success and an error code on failure.
 
-gicControlLookupFeature() and gicControlGetFeature() return the requested 
+`gicControlLookupFeature()` and `gicControlGetFeature()` return the requested 
 feature or NULL on failure.
 
-gicControlNumFeatures() return the number of features attached to the 
+`gicControlNumFeatures()` return the number of features attached to the 
 control.
 
 
 See Also
 --------
 
+:man:`gicContextRead(3)`
+
 
 
 Contexts
@@ -751,62 +754,63 @@
 It can have multiple subobjects (called features) that can further
 break that down (e.g. into up/down/left/right).
 
-Most applications will not need to handle that themselves. gicHeadRead()
+Most applications will not need to handle that themselves. `gicHeadRead()`
 will provide all they need. For those that want to build up contexts
 themselves, the following functions are provided:
 
-To allocate a new gic_context, call gicContextAllocate(). To free a
-context that is not needed anymore, call gicContextFree().
+To allocate a new gic_context, call `gicContextAllocate()`. To free a
+context that is not needed anymore, call `gicContextFree()`.
 
-gicContextAttachControl() and gicContextDetachControl() are used to 
+`gicContextAttachControl()` and `gicContextDetachControl()` are used to 
 attach and detach controls from a context. A control refers to a 
 collection of features that describe a common motion. Most contexts 
 will have multiple such controls, like one for sliding and one for
 turning a player.
 
-gicContextLookupControl() and gicContextGetControl() can be used to get 
+`gicContextLookupControl()` and `gicContextGetControl()` can be used to get 
 access to controls attached to a context. The former accesses the controls 
-by name, the latter by number. You can use gicContextNumControls() to 
+by name, the latter by number. You can use `gicContextNumControls()` to 
 query for the number of controls.
 
-gicContextGetName() can be used to query for the name of a context.
+`gicContextGetName()` can be used to query for the name of a context.
 
-gicContextWrite() writes a description of the context given to the given
-file. It can be read back with gicContextRead() which will allocate and
-return context if successful. Afterwards gicContextMapActions() should be
+`gicContextWrite()` writes a description of the context given to the given
+file. It can be read back with `gicContextRead()` which will allocate and
+return context if successful. Afterwards `gicContextMapActions()` should be
 called to reestablish the mapping between actions and callbacks.
 
-In learning-mode, gicContextFindConflict() is useful to check, if there are
+In learning-mode, `gicContextFindConflict()` is useful to check, if there are
 conflicting controls.
 
 When the context is active, you feed it with events using
-gicContextHandleEvent() which will cause it to activate the relevant
+`gicContextHandleEvent()` which will cause it to activate the relevant
 callbacks.
 
 When an application is in a context, you should feed the events to 
-gicContextHandleEvent() to activate the relevant
+`gicContextHandleEvent()` to activate the relevant
 callbacks. 
 
 
 Return value
 ------------
 
-gicContextRead() and gicContextAllocate() return the read/allocated 
+`gicContextRead()` and `gicContextAllocate()` return the read/allocated 
 context on return or NULL on failure.
 
-gicContextAttachControl(), gicContextDetachControl(), gicContextWrite() and
-gicContextMapActions() return 0 on success and an error code on failure.
+`gicContextAttachControl()`, `gicContextDetachControl()`, `gicContextWrite()`
+and `gicContextMapActions()` return 0 on success and an error code on failure.
 
-gicContextLookupControl() and gicContextGetControl() return the requested 
+`gicContextLookupControl()` and `gicContextGetControl()` return the requested 
 control or NULL on failure.
 
-gicContextNumControls() return the number of controls attached to the 
+`gicContextNumControls()` return the number of controls attached to the 
 context.
 
 
 See Also
 --------
 
+:man:`gicHeadRead(3)`
 
 
 Heads
@@ -847,7 +851,7 @@
 Description
 -----------
 
-A gic_head is libgiigics notion of a collection of contexts. Each context
+A gic_head is LIBGIIGIC's notion of a collection of contexts. Each context
 describes the mappings between inputs and actions for a given situation 
 in a program.
 
@@ -855,46 +859,46 @@
 managed by libgiigic.
 
 Usually a program will not have to bother with most functions as it will
-read its config via gicHeadRead(). However when building apps that 
+read its config via `gicHeadRead()`. However when building apps that 
 can (re)build the configuration files, the other functions become useful.
 
-A gic_head is allocated using gicHeadAllocate(), which takes the gic handle 
+A gic_head is allocated using `gicHeadAllocate()`, which takes the gic handle 
 it will be associated with and a name for the Head. It returns the allocated 
 head or NULL on failure.
 
-gicHeadFree() frees an allocated gic_head.
+`gicHeadFree()` frees an allocated gic_head.
 
-gicHeadAttachContext() and gicHeadDetachContext() are used to attach and
+`gicHeadAttachContext()` and `gicHeadDetachContext()` are used to attach and
 detach contexts from a head. A context refers to a situation in a program
 that has an input mapping attached to it. Most programs will have multiple
 such contexts, like one for accessing the menus, one for the game mode,
 etc.
 
-gicHeadLookupContext() and gicHeadGetContext() can be used to get access to
+`gicHeadLookupContext()` and `gicHeadGetContext()` can be used to get access to
 contexts attached to a head. The former accesses the contexts by name, the
-latter by number. You can use gicHeadNumContexts() to query for the number
+latter by number. You can use `gicHeadNumContexts()` to query for the number
 of contexts.
 
-gicHeadWrite() can be used to write out a textual description of the head.
+`gicHeadWrite()` can be used to write out a textual description of the head.
 This is usually used to write out a config file after it changed.
 
-gicHeadRead() will read such a file, allocate a gic_head and fill it with
-the read data. After that, you should call gicHeadMapActions() to
+`gicHeadRead()` will read such a :p:`file`, allocate a gic_head and fill it with
+the read data. After that, you should call `gicHeadMapActions()` to
 reestablish the connection between the actions and the action callbacks.
 
 Return value
 ------------
 
-gicHeadRead() and gicHeadAllocate() return the read/allocated head on return
+`gicHeadRead()` and `gicHeadAllocate()` return the read/allocated head on return
 or NULL on failure.
 
-gicHeadAttachContext(), gicHeadDetachContext(), gicHeadWrite() and
-gicHeadMapActions() return 0 on success and an error code on failure.
+`gicHeadAttachContext()`, `gicHeadDetachContext()`, `gicHeadWrite()` and
+`gicHeadMapActions()` return 0 on success and an error code on failure.
 
-gicHeadLookupContext() and gicHeadGetContext() return the requested context
+`gicHeadLookupContext()` and `gicHeadGetContext()` return the requested context
 or NULL on failure.
 
-gicHeadNumContexts() return the number of contexts attached to the head.
+`gicHeadNumContexts()` return the number of contexts attached to the head.
 
 
 See Also

Update of /cvsroot/ggi/ggi-libs/libgiigic/doc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv25081

Modified Files:
	Makefile.am libgiigic-functions.txt libgiigic.txt 
Added Files:
	libgiigic-overview.txt 
Log Message:
Added more docs, added an overview article. Still needs work WRT the
config manager stuff. Maybe Andrew can shed some extra light?


--- NEW FILE: libgiigic-overview.txt ---
LibGIIGIC Overview
==================

Purpose
~~~~~~~

LibGIIGIC is intended to help the game developer with a flexible input
mapping system which enables the user to easily adjust the bindings between
game actions and the input device movements.

No Fear
~~~~~~~

Please do not get confused by the tons of API calls. Most are only useful 
if you are developing new configmanagers or applications that have very
special needs, like reconfiguring their controlset on the fly.

A "normal" game will usually only use a very small subset of the LibGIIGIC
API, depending if it wants to just use a given GIC configuration, or if it
also wants to implement a configuration manager.

Actually it is a good idea, to at least allow the user to run his own config
manager if he wants to.

Terminology
~~~~~~~~~~~

LibGIIGIC has its own terminology that describes how an application and the
actions that can be triggered within it relate. This can be confusing at
first, so please make sure you read this section carefully and refer to it,
if unsure.

From LibGIIGIC's point of view, an application is represented as a "Head".
This term stems from the fact, that an application might serve multiple
displays (heads) with different configurations. LibGGI will usually have
its own inputs for each head, then.

Within each head, applications will usually have different needs for input
mapping, depending on the current state of the application. In LibGIIGIC
this is called a "Context".

Each context (like "in game", "main menu", ...) will usually have several
aspects that can be controlled, for example movement, weapon choice, etc.
This is what LibGIIGIC calls a "Control".

Most Controls have several subunits. For example movement may contain
"forward", "backward", "left" and "right". LibGIIGIC calls these "Features".

Most of the time, one feature can be controlled by a single keystroke,
mouse-click, joystick movement, etc. However sometimes it makes sense to
have multiple bindings for the same feature.

Any such user input that is associated to a feature is called a
"Recognizer".


This hierarchy of types that builds the skeleton of LibGIIGIC.


It can be represented as a file. Look at programs/demos/configmanager.gic
for an example. Such a ".gic-file" contains all the configuration info 
for a given head.


Of course it is not enough to just recognize, that a feature has been
activated by some input. One usually wants to act on that.

LibGIIGIC allows to bind callback functions to features that get called
when a Recognizer triggers. These are called "Actions".

Simple Example
~~~~~~~~~~~~~~

Now let's have a look at a very simple sample program - demo.c

When working with LibGIIGIC, you first need to initialize the library.
Do this using gicInit(). When you don't need LibGIIGIC anymore, close it
down using gicExit(). Don't be afraid to use that in higher level libraries.
LibGIIGIC is aware of being initialized and exited multiple times, and will
handle it correctly, as long as the calls are nested properly.

These calls only initialize the lib. To interact with it, you need to
allocate a gic_handle_t using gicOpen(NULL). The parameter is reserved for
future expansion. When you are done with it, free the allocated handle using
gicClose(handle).

If you have an existing configuration file, you just read it:

        config=fopen("demo.gic","r");                                           
        head=gicHeadRead(handle,config);                                        
        fclose(config);                                                         

Simple - right?

You can of course stuff your other data there, too. gicHeadRead is aware
of where to stop, so you can store your data before and after the LibGIIGIC
data to your liking.

If you are interested in rehearsing the terminoloy chapter, you may want to
look at the demo.gic file yourself. It is human readable and you will find
the hierarchy of objects in there.

Now what you got back is an object "head" which is of type gic_head.

However, you will usually work with contexts, as the application will
normally enter different states associated with gic_contexts.

You can extract the contexts from the head like this:

menu=gicHeadLookupContext(handle,head,"Menu context");                  


Now we have one point at needs to be cleaned up: The file also stores
actions, which are basically callbacks. However how does one store function
pointers in a config file in a way that does not break when moving the
config file between platforms etc. ?

You don't. The next step is to reestablish the "action mapping" - a
connection between a symbolic name of the action, and the actual callback
function. This mapping is stored in a variable of type gic_actionlist.

A sample list would be:

gic_actionlist actionmapping[]= {                                               
        {NULL,"mynextaction",   my_action,      NULL},                          
        {NULL,"myprevaction",   my_action2,     (void *)0x12345678},            
        {NULL,NULL,NULL,NULL}                                                   
};                                                                              

The first element of each gic_actionlist-entry here is reserved for a
chaining pointer and always NULL.

The second element is the name of the action as it appears in the .gic-file.
The third is the callback function, and the fourth a void pointer to some
private data which will be given to the callback.

The fourth entry allows to reuse the same callback function for multiple
purposes, which makes a lot of sense, as many callback functions are usually
very similar.

You can now re-map the actions using this call:

gicHeadMapActions(handle,head,actionmapping);

This will cause LibGIIGIC to iterate through the head and its child objects
and find any actions attached. If the action names match a name in the
actionmapping list, the respective callbacks are set up.

From then on, LibGIIGIC is ready to receive events. You just receive a
gii_event from LibGII (oder LibGGI which uses LibGII for input), or build
one yourself, if you insist not to use LibGII.

You can then feed the event to LibGIIGIC using

gicContextHandleEvent(handle,menu, &event);

Note, that it does not make sense to send an event to a head, as the event
might have different meanings depending on context. So you just feed it to
the right context.

Now if an event matches the description in the .gic file, the requested
action callbacks will fire. We will discuss them in greater detail in the
next section.


When we are done with LibGIIGIC, we should close down all handles we
opened using gicClose(handle) and finally call gicExit().


Callback functions (actions)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If a recognizer triggers, it will activate the feature it is attached to,
which will in turn call the actions bound to it.

Action functions have the following prototype:

void my_action(gic_handle_t hand, gic_actionlist *action,
	gic_feature *feature, gic_state newstate,gic_flag flag,
	int recnum) 

When it gets called, it is given a lot of data that allows to derive 
why it was called.

First of all it gets the gic_handle_t that triggered the action. This is
useful, if you want to call LibGIIGIC functions within the callback.

Then you get the gic_actionlist of the action that caused the callback to be
actived. This datatype was already covered in the previous section.
It's most common uses are differentiating calls to a common callback that
serves multiple purposes. To achieve this, the most interesting entries are
action->name and action->privdata, which will commonly be used to find out
which action triggered and to point to some common data structure that will
be modified by the actions.

The gic_feature points to the feature that this action is bound to and can
as well be used to differentiate when binding a single action function to
multiple features.

When a feature gets activated, it can have an "extent to which it is
activated". This is used by features that don't only have on/off
characteristics, but rather a linear notion of "how active they are".
An example for this is e.g. a control for turning. Simple input devices
like keyboards can only say turn left/don't turn left, while mice or
joysticks can say how fast or far to turn.

gic_state carries this information. The macros GIC_STATE_MIN, GIC_STATE_MAX,
GIC_STATE_MIDDLE and GIC_NOACTION can be used to find out how strong the
respective measure of activation was.

gic_flag can carry additional information about the action. If flags are
set, that are within GIC_FLAG_MUSTKNOWMASK, you are expected to handle them.
Set flags outside that bitmask are optional and can be ignored for
application development.

Up to now, only one such flag is defined: GIC_FLAG_PULSE.
If set, it indicates, that the events triggering the action is of a "pulsed"
type, i.e. it is expected to be released immediately after it was received,
so you should handle it similar to the case of an event like the one you
received, immediately followed by one of the same kind with gic_state
containing GIC_STATE_MIN.

The integer recnum gives the number of the recognizer that caused this
event to trigger. This can be used when implementing "adding policies", like
if turning with joystick and mouse at the same time will add up, or will
just use the highest value, or whatever.


Using the Lazy action helpers
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Many simple programs will prefer not to use their own action callbacks, but
rather just use this predefined callback system.

For this to work, you have to bind all relevant actions you do not want to
handle yourself to gicActionLazyAction.

The privdata field must point to a gicActionLazyData variable.

When using the Lazy action helpers, you usually do something like this:

ggiEventRead(vis,&event,emAll);		/* get an event. */
/* Let LibGIC evaluate it for the menu context */
gicContextHandleEvent(hand, menucon, &event);

Now the gicActionLazyAction callbacks are run, and you can check how much
the individual gicActionLazyData elements are active.

For this, you do: gicActionLazyGetstate(&lazydata) which will return a
gic_state you can evaluate. (The gicActionLazyAction callback implement a
"max activation is returned" policy with respect to multiple active
recognizers).

This will also handle the case of pulsed inputs, which will be returned
and then deleted.

If you are unsure about the state of the variables (e.g. at startup or
after retraining the mappings), you can reset the variables using 
gicActionLazyReset.


Training
~~~~~~~~


Conflicts
~~~~~~~~~
Index: Makefile.am
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/Makefile.am,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- Makefile.am	14 Oct 2004 15:40:46 -0000	1.2
+++ Makefile.am	27 Oct 2004 23:38:40 -0000	1.3
@@ -1,3 +1,4 @@
 SUBDIRS = man
 
-EXTRA_DIST = libgiigic.txt libgiigic-functions.txt libgiigic-libraries.txt
+EXTRA_DIST = libgiigic.txt libgiigic-functions.txt libgiigic-libraries.txt \
+	libgiigic-overview.txt

Index: libgiigic-functions.txt
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/libgiigic-functions.txt,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- libgiigic-functions.txt	18 Oct 2004 23:54:07 -0000	1.5
+++ libgiigic-functions.txt	27 Oct 2004 23:38:40 -0000	1.6
@@ -476,12 +476,16 @@
 Description
 -----------
 
-TODO Write something useful here
+gicFeatureAttachAction() and gicFeatureDetachAction() are used to bind an
+action (i.e. a callback function) to a feature. This is usually handled
+by higher layers, which map whole sets of actions using a gic_actionlist.
 
 
 Return value
 ------------
 
+gicFeatureAttachAction() and gicFeatureDetachAction() return 0 on success
+and an errorcode on failure.
 
 See Also
 --------
@@ -510,8 +514,10 @@
 Description
 -----------
 
-TODO Write something useful here
-
+gicFeatureWrite() writes a description of the feature given to the given
+file. It can be read back with gicFeatureRead() which will allocate and
+return a feature if successful. Afterwards gicFeatureMapActions() should be
+called to reestablish the mapping between actions and callbacks.
 
 Return value
 ------------
@@ -520,6 +526,7 @@
 See Also
 --------
 
+gicFeatureMapActions
 
 
 Feature mappings
@@ -546,8 +553,11 @@
 Description
 -----------
 
-TODO Write something useful here
+gicFeatureMapActions() is called to reestablish the connection between 
+the actions and the action callbacks.
 
+In learning-mode, gicFeatureFindConflict() is useful to check, if there are
+conflicting features.
 
 Return value
 ------------
@@ -587,10 +597,6 @@
 You can feed events to gicFeatureHandleEvent() to activate the relevant
 callbacks. However, usually one uses gicContextHandleEvent().
 
-
-TODO Write something useful here
-
-
 Return value
 ------------
 
@@ -675,12 +681,20 @@
 callbacks. However, usually one uses gicContextHandleEvent().
 
 
+Return value
+------------
 
-TODO Write something useful here
+gicControlRead() and gicControlAllocate() return the read/allocated 
+context on return or NULL on failure.
 
+gicControlAttachFeature(), gicControlDetachFeature(), gicControlWrite() and
+gicControlMapActions() return 0 on success and an error code on failure.
 
-Return value
-------------
+gicControlLookupFeature() and gicControlGetFeature() return the requested 
+feature or NULL on failure.
+
+gicControlNumFeatures() return the number of features attached to the 
+control.
 
 
 See Also
@@ -774,12 +788,21 @@
 callbacks. 
 
 
-TODO Write more here
-
-
 Return value
 ------------
 
+gicContextRead() and gicContextAllocate() return the read/allocated 
+context on return or NULL on failure.
+
+gicContextAttachControl(), gicContextDetachControl(), gicContextWrite() and
+gicContextMapActions() return 0 on success and an error code on failure.
+
+gicContextLookupControl() and gicContextGetControl() return the requested 
+control or NULL on failure.
+
+gicContextNumControls() return the number of controls attached to the 
+context.
+
 
 See Also
 --------

Index: libgiigic.txt
===================================================================
RCS file: /cvsroot/ggi/ggi-libs/libgiigic/doc/libgiigic.txt,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- libgiigic.txt	16 Oct 2004 22:00:37 -0000	1.4
+++ libgiigic.txt	27 Oct 2004 23:38:40 -0000	1.5
@@ -2,6 +2,8 @@
 LibGIIGIC Documentation
 =======================
 
+.. include:: libgiigic-overview.txt
+
 .. include:: libgiigic-functions.txt
 
 .. include:: libgiigic-libraries.txt