Trackpad menu touch vs tap (allowing both)

[pizzaparty]

I've been trying to configure this for the last two weeks - and haven't had success.

Does anyone know how to set up the following:

tap
[1][2]
[3][4]

press
[X][Y]
[A][C]

I want two "sets" of buttons for a single track pad. When I tap/release I get 1/2/3/4. When I press I get X/Y/A/C.

I had some success on setting up action-layers and timings. However this seems to get confused, and starts inverting the action layer order. It's not consistent.

[shadowboy813]

Trackpad is pressure sensitive. Set one of them to touch (the tap) and the other to requires click (the press). Adjust the pressure threshold for the click to what works. Set the tap activator to be interruptible (or else it will potentially do both)

[pizzaparty]

I don't think you understand the issue fully. I don't want the trackpad to be one large/single button.

[ugafan]

Default set
Directional Pad - Requires Click Off
1 - release press
2 - release press
3 - release press
4 - release press

Click = Add Action Layer - Soft Press. Increase soft press threshold to avoid accidental clicks.

Layer
Directional Pad - Requires Click On
X - regular press
Y - regular press
A - regular press
C - regular press

Click = Cleared from Parent
Touch - Remove Action Layer - Release press

[pizzaparty]

Can you clarify the last bit? Is touch the default set (the soft press set)?

Going to try this later. Does this require beta branch?

[ugafan]

Everything above Layer is on the default set. Everything below Layer is on the action layer.

[pizzaparty]

Does this change significantly if I use touch menu instead of directional pad? I kind of need 5 buttons.

[pizzaparty]

Well it bugged and cleared the whole config. Very frustrating.

[pizzaparty]

Ok so this is *very* promising. It's the closest of anything so far.

The only things that need to be included are:

* I need 5 buttons, so I think it needs to be changed to a virtual menu. This probably breaks the "click required on/off" portion?
* I need to add additional commands to each button. I need to press/tap to move the cursor to a screen position and then press the button.

[pizzaparty]

Yeah it seems like the changes I've attempted to make by using a virtual menu have broken the working solution from the D-Pad.

[ugafan]

You can use a virtual menu, but you'll have to work around some technical problems and bugs. First of which is a touch release should only occur after you lift your finger off the trackpad. But this is not the case if you click into an action layer. The touch release from the default action set fires. You can avoid this by setting the default touch menu to continuous and have the button press release press. Downside is it will fire the release press any time you move to a different area of the pad.

When you click into the layer there can be a problem where the touch menu fires once, but doesn't fire with subsequent presses. You can work around this with release presses.

Layers have been buggy for years, in particular when using virtual menus. If you need 10 different inputs, it would probably be better safer to have all the commands in one menu on the default set.

You can do extra commands for each button, that won't be a problem. You can add a fire end delay to the move cursor position and a smaller fire start delay to the button you want pressed after the cursor is moved.

Nested menus are also an option. Just make sure you only have one action layer open at a time though.

[shadowboy813]

Originally posted by pizzaparty:

I don't think you understand the issue fully. I don't want the trackpad to be one large/single button.

I didn't say to make each trackpad one button?

What I was saying was what to do for EACH button, as in do what I replied for X/1, then for Y/2, then for A/3, then for C/4, etc. Not the entire trackpad. I fully understood the issue, you just didn't understand my reply.

Originally posted by pizzaparty:

Ok so this is *very* promising. It's the closest of anything so far.

The only things that need to be included are:

* I need 5 buttons, so I think it needs to be changed to a virtual menu. This probably breaks the "click required on/off" portion?
* I need to add additional commands to each button. I need to press/tap to move the cursor to a screen position and then press the button.

You can also use a radial menu (although I don't really like using them THAT much, so I haven't set one up on the deck, but I doubt it'll be much different than the steam controller)

[pizzaparty]

Can you elaborate on the original idea? What do you mean set on and then the other. Set action layers?

[pizzaparty]

Originally posted by ugafan:

You can use a virtual menu, but you'll have to work around some technical problems and bugs. First of which is a touch release should only occur after you lift your finger off the trackpad. But this is not the case if you click into an action layer. The touch release from the default action set fires. You can avoid this by setting the default touch menu to continuous and have the button press release press. Downside is it will fire the release press any time you move to a different area of the pad.

When you click into the layer there can be a problem where the touch menu fires once, but doesn't fire with subsequent presses. You can work around this with release presses.

Layers have been buggy for years, in particular when using virtual menus. If you need 10 different inputs, it would probably be better safer to have all the commands in one menu on the default set.

You can do extra commands for each button, that won't be a problem. You can add a fire end delay to the move cursor position and a smaller fire start delay to the button you want pressed after the cursor is moved.

Nested menus are also an option. Just make sure you only have one action layer open at a time though.

Does the radial menu have the same bugs as a virtual menu?