Comment 6 for bug 1651307

Ummmm, I was actually thinking about doing it at skin level:
making any knob.xml a stacked layout and stacking two buttons on top. This way, I'd to position the buttons individually for every knob size with <Pos> or margin.

You're seeing a bigger picture I guess...
I had a look at wknobcomposed.cpp and wwidgetgroup.cpp
If I get it right (?), your 1st suggestion is basically like mine but on another level (WKnobComposed::addWidget?) so that one would have
<KnobComposed>
   <Background>...
   <Indicator>...
   <Children>
     <LeftButton>(incl. object name, conneceted control, ...
     <RightButton> --"--
   </Children>
And "hard" means your worried about the positioning per knob type with qss?

In your 2nd suggestion "sensitive regions" refers to relative positioning and sizing of buttons as well as an interface to individually connect controls in knob.xml, both on C++ level?
To maintain some flexibility, couldn't size and position (top/bottom) be variable, too, then?

In case I got it right, I like the second idea much more!
But I'd need 'a few' hints how to accomplish this.

Regarding the touch bugs: I'm still C++ newbie, so a lot can happen on the go... ;)