Usage: First Touch Mapping
If there is anything that you still dont understand, the application does not do what is explained on this tutorial or you would like another tutorial for another topic just contact me.
In this tutorial I'm going to explain a very simple mapping to touch. As always if something does not happen like it is explained here maybe there is a problem so feel free to contact me.
I will place a button that will touch a single screen point and a stick that will touch a virtual screen gamepad.
On a real case scenario you want to have a game or whatever application you want to touch map on the background to see its touch controls as a position reference.
I recommend that you enable show touches on screen on developer options because it will make very clear what screen positions are touched. Sometimes screen needs calibration and touches happen NOT where you think they are.It is also useful to understand better what each of the operation modesdo.
Remember from the previous tutorial that we got our gamepad recognized by the mapper? It showed in the setup area with a joystick icon on the right.
So now you move the right stick and it should appear both in thesetup area and as a screen widget.
Its name is Stick 1. On the left you see a little bar that is the same color as the device (IN: ADC JOYSTICK) and the same color as the widget. This makes it easier to identify if you have more than one gamepad connected.
On the right of Stick 1 you will be able to select different operation modes those are the things you can make the stick do. For now the default mode Touch pad is good enough'. Under Stick 1 you can see different options related to the current operation mode.
You can move the virtual touch pad around by dragging on it. You can change size by pinch or zoom gestures or by moving the Zoom slider.
If you tap on the widget or you move the stick the setup area scrolls to the moved component. This makes easier finding your configuration.
Now I placed it on the right and I made it bigger. You would put it on top of the virtual gamepad of the touch only game you want to map.
Now I press the A button of the gamepad. And the A widget shows. A touch button is very simple so it needs no extra parameters. There are a lot of different operation modes to simulate many different interactions.
I drag theA widget to the left side.
Now I considered finished my simple mapping so I click on the tick that is on the header of the setup area. A dialog shows asking for the name of the profile. The default name is the one of the application on the background. I recommend that you do not change that name. At the end of the day you should need only one mapping per game and you can enable the autoprofile function to let the mapper load the mappings for you, Remember that mappings can be shared if people collaborate you may not even need to write your own mappings. Nevertheless is very easy!
I click accept and the mapping will be applied. When I move the stick or click the A button touches will be done on the screen. Again, I recommend that you enable show screen touches on the developer options on Android configuration.
If you have more questions ask and I'll make more tutorials.