i wasn't here for 0.5
️
5
touch_controls and fix it accordingly.
5. Save the changes in the client when you are done. You can also discard your changes or revert to the default if you messed up.
Example for a new touch button:
{
"x": 500000,
"y": 500000,
"w": 100000,
"h": 100000,
"shape": "rect",
"visibilities": [
"ingame"
],
"behavior": {
"type": "bind",
"label": "Example",
"label-type": "plain",
"command": "echo Hello world!"
}
},
4
3
- would be interesting because then I'd have yet another reason to convince my company to buy me one for the apprentice - would be interesting because then I'd have yet another reason to convince my company to buy me one for the apprentice 
2 
1 2
looks like the account is gone after the second report 3
adb bugreport ./output.zip or use adb logcat to get the log while the app crashes.
adb bugreport ./output.zip or use adb logcat to get the log while the app crashes. 
adb you could try to get a crash dump, though I'm not sure how useful it is without a debug build of the apk
apTabNames which has a fixed size of NUMBER_OF_APPEARANCE_TABS, you also need to adjust that and the other enum literalsSDL_OpenAudioDevice returns the specs that were actually applied but we ignore most of themapTabNames which has a fixed size of NUMBER_OF_APPEARANCE_TABS, you also need to adjust that and the other enum literals 
1
