# Webconf touchscreen UI config

**URL:** <https://discourse.zynthian.org/t/webconf-touchscreen-ui-config/5400>\
**Category:** Using Zynthian\
**Created:** [February 14, 2021, 9:37am UTC](https://discourse.zynthian.org/t/webconf-touchscreen-ui-config/5400 "2021-02-14T09:37:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pat](https://discourse.zynthian.org/letter_avatar_proxy/v4/letter/p/8491ac/32.png) [@pat](https://discourse.zynthian.org/u/pat)\
**Post date:** [February 14, 2021, 9:37am UTC](https://discourse.zynthian.org/t/webconf-touchscreen-ui-config/5400/1 "2021-02-14T09:37:07Z")

</div>

Hi, I’m a little bit confused about interface settings in webconf, and didn’t find relevant info in the wiki. There are: “Enable Touch Widgets” and “Enable Onscreen Buttons” checkboxes and from what I experience (for now I have only a touchscreen, no encoders yet) : I don’t see what the “Enable Onscreen Buttons” option does, while the “Enable Touch Widgets” option… enables the onscreen buttons at the bottom of the screen.

BTW, it often happens accidentally with a touchscreen to accidentally trigger a button press command (like “back”, etc.) when rotating a touchscreen control. I think it would make total sense UI wise that when the onscreen buttons are shown, the 4 corner controls can no longer be used for emulating button press operations, as virtual buttons are already available onscreen. It would avoid triggering unwanted commands.

---

<div class="post-metadata">

**Author:** ![gr0k](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/gr0k/32/5821_2.png) [@gr0k](https://discourse.zynthian.org/u/gr0k)\
**Post date:** [February 14, 2021, 11:11am UTC](https://discourse.zynthian.org/t/webconf-touchscreen-ui-config/5400/2 "2021-02-14T11:11:33Z")

</div>

I also faced this confusion! Both with the Enable Touch Widgets / Onscreen Buttons options, and with seemingly random events firing whilst adjusting controls.

One tip I wish I knew before I got some hardware for my Zynth was the [keypad/keymapping integration](https://wiki.zynthian.org/index.php/Zynthian_UI_Users_Guide#CUIA:_Callable_UI_Actions). In [this thread](https://discourse.zynthian.org/t/touch-interface-increment-and-decrement-buttons/5394/3) @jofemodo recommends a keypad like [this](https://sea.banggood.com/MLD-268-Wireless-Numeric-Keypad-2_4G-18-Keys-Mini-Digital-Number-Pad-Portable-Silent-Financial-Accounting-Keyboard-p-1675409.html?cur_warehouse=CN&ID=6287845&rmmds=buy) but any keyboard will work. The mappings are customisable in webconf.

It won’t fix the button toggle bug, but it might make using the Zynthian more enjoyable.