diff --git a/libx52_integration.html b/libx52_integration.html index 2af28f2..007a38e 100644 --- a/libx52_integration.html +++ b/libx52_integration.html @@ -97,7 +97,7 @@ $(function() {
Most libx52 functions to update the joystick state do not directly write to the connected joystick, but only update internal data structures within the device context. In order to actually update the joystick, the application must call libx52_update. This function writes the updates to the joystick and resets any internal state.
Example
@@ -105,11 +105,11 @@ Joystick UpdatesMost libx52 functions return a standard libx52_error_code integer value that indicates the status of the operation. As long as the operation succeeded, the function will return LIBX52_SUCCESS. Other values returned indicate a failure of some sort.
libx52_strerror can convert the return code into a descriptive string that may be displayed to users.
-libx52_strerror automatically handles internationalization. As long as your application sets up the locale correctly, and the error strings have been translated to that locale, the returned strings will correspond to the translated values for your locale.
diff --git a/pages.html b/pages.html index e0e3c0a..dd45ff1 100644 --- a/pages.html +++ b/pages.html @@ -74,10 +74,11 @@ $(function() {
+ libx52
+ 0.2.3
+
+ Saitek X52/X52Pro drivers for Linux/Unix
+ |
+
The logging
commands allow the user to fine tune the logging configuration of x52d
as well as adjust the log levels for either all the modules, or for each of the modules individually.
While the -v
and -q
command line options allow you to either increase the logging verbosity or suppress it entirely, they are required to be specified at program startup. On the other hand, having the logging
commands allows the user to fine tune the logging while the daemon is running.
x52d
is split into several modules as far as logging is concerned. The list of modules is below:
Config
Clock
Command
Device
IO
LED
Mouse
The following is a list of supported logging levels. Each level logs the ones above it as well as the current level
+none
- Disable logging entirelyfatal
- Log fatal messageserror
- Log error messageswarning
- Log warning messagesinfo
- Log informational messagesdebug
- Log debug messagestrace
- Log trace messages - useful for tracing program flow.default
- Not a level, but used when configuring module log levels, makes the module log level fallback to the global log level.The logging show
command takes in an optional module name, as listed in the Modules section above. It returns the module name, if specified, and the log level for that module. If the module is configured to fallback to the global level, then it will return the global level.
Arguments
+logging
show
Returns
+DATA
module-name
(if specified)The logging set
command takes in the optional module name and the log level and sets the log level for that module, if specified, or the global level otherwise.
Arguments
+logging
set
Returns
+OK
logging
set
module-name
(if specified)x52ctl - Command line controller to X52 daemon
-x52ctl [-i] [-s socket-path] [command]
x52ctl is a program that can be used to communicate with the X52 daemon. It can be used either as a one-shot program that can be run from another program or script, or it can be run interactively.
Commands are sent to the running daemon, and responses are written to standard output.
If not running interactively, then you must specify a command, or the program will exit with a failure exit code. If running interactively, the program will request input and send that to the daemon, until the user either enters the string "quit", or terminates input by using Ctrl+D.
--i
Run in interactive mode. Any additional non-option arguments are ignored.The list of supported commands are shown below: