Skip to content

Creating presets

Alex edited this page Jan 4, 2019 · 5 revisions

input-overlay

Overlays consist of two parts:

  • The texture image
  • The config file

Since I poured quite a bit of work into simplifying the process of creating a config the only real task is to create a texture. So here are some specifications:

  • The texture needs a 1 pixel gap around the entire image.
  • Each element should be 3 pixel apart from another
  • All textures needed for the overlay have to be in this one image

Before you start you should make sure which types of elements you need, because some have additional specifications. Take a look at element descriptions over at io-cct to find out which those are.

Generally buttons work like this: They are either pressed or unpressed (duh). The pressed texture is always at the top in the texture atlas and below it with the same size with a 3 pixel gap is the pressed texture.

Other than that's it, when you've figured out which elements you want and which specifications they have you can now load the texture file in io-cct, and start arranging them.

input-history

input-history works a little different. The only presets it accepts are either key names or key icons. The key name file can be used to change, add or restrict key names. The syntax is as follows:

# This is a comment
# 2_[keycode]=keyname This is also a comment
# The line bellow renames the key with the key code '0x0034' to '.'
2_0x0034=.

the other type of preset it takes is key icons. This allows keys to be replaced by icons, which all have to be the same size and chained next to each other (once again 1 pixel border around entire image, 3 pixels in between) in one texture. Additionally it needs a list of keycodes, which tells the plugin what keycode corresponds to what key icon.

Clone this wiki locally