#UCR - Universal Control Remapper

#MAIN UCR DOWNLOAD LINK #Forum thread for news and discussion ##Historical releases

##About The aim of UCR is to allow end-users to easily leverage the power of AHK without having to learn to code.
At it's basest level, think of it as a way for an end-user to run a number of scripts written by various people, and manage when each script runs, what keys trigger it's functions, tweak each script's parameters, etc - solely by using a GUI application. The primary target audience is gamers, UCR is intended to be able to replicate the functionality that comes with programmable keyboards / mice / joysticks etc.

##Profiles UCR supports profiles. A number of plugins can be grouped together into a Profile.
Profiles will be able to be linked to a specific application - when that application gets the focus, the profile becomes active.

##Plugins At the core of the design of UCR is the idea of an AHK script as a "Plugin".
A plugin is simply a text file containing AHK script (Even though the main UCR "app" may be running as an EXE).
The plugin is an AHK class that derives from a base class that is part of the UCR source code.
Each instance of each plugin gets it's own GUI inside the UCR app when added by a user. You can add anything you like to that Gui.
Anything that you could normally put in an AHK class should work inside a plugin.

##Persistent GuiControls Plugins can call UCR methods to add a GuiControl to their Gui whose value will be remembered between runs of UCR.
It can be used to allow the end user to tweak the behavior of the plugin that it is part of.

##Inputs and Outputs Plugins may also contain special GuiControls that allow the end user to bind inputs and outputs.
Valid inputs are: Keyboard, Mouse, Joystick.
Valid outputs are: Keyboard, Mouse, vJoy Virtual Joystick

##Requirements If you are a typical end-user of UCR, you just need to download the installer package.

In order to run UCR un-compiled, you will need to replace your AutoHotkey EXE with one from AHK_H v1.
Alternately, rename Autohotkey.exe (An AHK_H v1 one) to UCR.exe and place it in the same folder as UCR.ahk, then double-click UCR.exe to run UCR un-compiled.

##Debugging A major design goal of UCR is to make it (and plugins) debuggable. Development is currently done using Scite4AutoHotkey, so if you wish to debug UCR or a plugin, that is the advised solution.
UCR's code avoids the use of SetTimer, OnMessage etc in the main thread wherever possible, so that "stepping in" in the debugger does not end up dropping you into some random timer pseudo-thread. In general, it works around these situations by offloading any code that might interfere with the debugging process to a worker thread.

##Documentation Documentation is forthcoming.