Each has their own folder, which can contain dependent DLLs etc.Ī "Provider Libraries" project is provided, with helper classes etc to simplify the process of writing new Providers - their use is entirely optional.
Providers are MEF plugins that expose IProvider or one of it's derived interfaces. A Provider typically wraps one API, however this does not need to be the case. Support for new forms of I/O can be added to IOWrapper via plugins dubbed "Providers". Whilst Windows has standard APIs for I/O - for example DirectInput (Flight sticks, steering wheels etc), XInput (Xbox controllers) and RawInput (Keyboards, mice, joysticks), there are also other devices which require custom APIs (eg vJoy for faking DirectInput joysticks), so IOWrapper needs to be extensible. The consumer can make "subscriptions" to devices in order to receive input or send output. The purpose of the IOWrapper library is to present a list of devices to the consumer both input (The user typed a key, moved a joystick etc) and output (Faking user input). Technically, however, IOWrapper is a stand-alone project which is not inherently coupled to the UCR front-end.
IOWrapper is the "Back End" for Universal Control Remapper (UCR) 2, handling all the device interaction. End Users should download UCR instead Project Overview Unless you are a developer, this project is probably of no use to you.
0 kommentar(er)
