Login

This Months Donations

$427.23
of $500.00 goal
Server, CDN, Network, Licensing
Development Budget
Developers Beer Fund
Recent:
IsaacElenbaas
$2.00
SFAH
$2.00
sOLACE
$5.00
Rob Nice
$5.00
ghost
$2.00
Number of donations
96
Highest donation
$50.00
Average donation
$4.94

Input Mapper 2.0 (Alpha)

IM 2 is currently under development.

This article is obsolete as of latest alpha, properties and signatures required by the plugin interface are now created inside the inherited class.

There are many interfaces and API's available to plugin development for IM 2.0, but the basics just to meet the minimum requirements for IM for the plugin to even load will be covered in this article.

Log in to comment

Regardless of what kind of input or output plugin you are developing, it will likely need at least one input or output channel.

Log in to comment

Most plugins will need a way for users to be able to manupilate settings. This will show how to use IMs built in functionality to dynamically create plugin settings.

Log in to comment

Mapping plugins are the easiest to make, they only require a specific signature and an overrided method and that is it.

Log in to comment
Log in to comment

Plugin packages have the benefit of being completely user hands off wen it comes to installation, they simply double click the file.

Log in to comment

Some output plugins will have a fixed list of output devices such as keyboard or moue plugins since the system only recignized one of those devices at a time anyway, but virtual controllers may wish to have the ability to allow the user to add or remove as many virtual controllers as needed.

Log in to comment

Subcategories

Even though IM 2 is in its alpha stages, it is already open to plugin development. This section details how to go about writing a plugin for IM 2.0.