How do I reduce the initial distance threshold for Interaction Context manipulations?

Jim Bean 0

In the application I am developing, the interaction context callback that I have registered is not being called until the finger that already has contact has moved too many pixels. Basically, this causes a big jump. I'm not sure how to reduce this, or if its even supposed to be there normally. Its not accidental touch protection, because the finger can be in contact indefinitely and it will still happen; it only depends on the distance the finger moves, not the contact time.

Jeanine Zhang-MSFT 9,951 Reputation points Microsoft Vendor

2024-11-22T08:34:01.9033333+00:00

You could try to enable the INTERACTION_CONFIGURATION_FLAG_MANIPULATION_EXACT.

You could refer to the INTERACTION_CONFIGURATION_FLAGS enumeration
Jim Bean 0 Reputation points

2024-11-22T20:12:25.1033333+00:00

@Jeanine Zhang-MSFT

Unfortunately, it did not fix the issue. I think i'll have to bypass the IC and do direct POINTER_INFO processing.

This is what I used for the IC configuration:

constexpr static INTERACTION_CONTEXT_CONFIGURATION enableManipulation = {

INTERACTION_ID_MANIPULATION,

INTERACTION_CONFIGURATION_FLAG_MANIPULATION | INTERACTION_CONFIGURATION_FLAG_MANIPULATION_TRANSLATION_X | INTERACTION_CONFIGURATION_FLAG_MANIPULATION_TRANSLATION_Y | INTERACTION_CONFIGURATION_FLAG_MANIPULATION_RAILS_Y | INTERACTION_CONFIGURATION_FLAG_MANIPULATION_EXACT

};
Jeanine Zhang-MSFT 9,951 Reputation points Microsoft Vendor

2024-11-26T07:41:19.9633333+00:00

Whether your problem has been solved via direct POINTER_INFO processing?
Jim Bean 0 Reputation points

2024-11-27T06:56:19.6133333+00:00

@Jeanine Zhang-MSFT Yes, direct pointer processing gets around the issue, so the IC needs an option to lower the distance threshold for the standard use case or its a bug that needs fixing. Its a pretty serious issue considering this is the simplest use case for the Interaction Context, but its pretty easy to work around. In my case, I was developing fader controls for a virtual mixer, and the IC's behavior made it useless for that case. So, what I did was wrap the IC in an object that can optionally bypass the IC processor if the option is set.

Share via

How do I reduce the initial distance threshold for Interaction Context manipulations?

Your answer