-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MRTK3: Scrolling Views do not work with user input. #10736
Comments
A bit of an update, after some tweaking of the controls I returned to testing and found it was possible to scroll in the view (quite a relief that it is even possible), however this still leaves it practically unusable. Ideally though, if a Selectable is Grabbed and the use attempts to drag, then this input should be fed through to the parent scrolling area (if there is one), so that scrolling is possible wherever you drag in a Scrollable area. |
I have a video from Simon if anyone on the MRTK team needs to see it. Just let me know over Teams if so. |
@SimonDarksideJ, Scrolling is not yet implemented for this preview release. I've been working on it for the past few weeks, stay tuned! There's a reason this is still in preview 😉 |
Tracking this work in #10795 ! |
Closing as duplicated from the PR. I'll be posting additional updates over on the PR page. |
@srinjoym can you look into Finn's PR and see what it'll take to bring this into GA |
Tested out Finn's draft PR today. The implementation adds a There are a couple of issues right now:
|
MRTK 2 had both poke scrolling and bubble up ray scrolling. The implementation wasn't ideal either as the inner buttons still got clicked when trying to scroll |
Based on the investigation above, I'd say we need about 2 weeks to either fix this implementation or prototype new scroll interactions. I'm moving this task back to planned |
## Overview This adds an experimental method of scrolling through a Unity `ScrollRect` using XRI interactors. The sample scene demonstrates how to scroll through a canvas `SrollRect` using both the poke and hand ray interactors. ![An animated image demonstrating scrolling with Unity XRI interactors](https://github.com/microsoft/MixedRealityToolkit-Unity/assets/36461279/ce1c487a-502e-477a-96e0-bda910bfc20f) To accomplish this, the new experimental component `InteractableEventRouter` was added. The `InteractableEventRouter` component routes child XRI events to other child and parent game objects that contain the `IXRInteractableEventRouteTarget` component. The following image shows a sample usage of this component. In this usage, the `InteractableEventRouter` is configured to bubble up select and hover events from child games objects. ![Shows a sample usage of this component. In this usage, the `InteractableEventRouter` is configured to bubble up select and hover events from child games objects](https://github.com/microsoft/MixedRealityToolkit-Unity/assets/36461279/7119b208-b79c-44bc-851d-9f2374a95e1c) ## Fixes - #10736 ## Known Limitations The `InteractbleEventRouter` currently can't handle `IXRInteractableEventRouteTargets` being dynamically added. So, this may limit some use cases, such as wanting to trickle down events to children added dynamically. ## Verification - Unit Tests in progress
An experimental feature has been added for this. |
This issue has been migrated a new MRTK repository, and the status of this issue will now be tracked at the following location:
Describe the bug
A clear and concise description of what the bug is.
Tested all of the available MS examples on using a Scrolling View with the MRTK3, yet none actually function with user input.
Valiated:
All the input seems to be captured by the content and none of the scroll behaviour makes it's way up to the scrollrect. Even using a Scrollbar does nothing.
To reproduce
Steps to reproduce the behavior:
Expected behavior
ScrollRects should be interactable with using input via near hands or far pointers, to scroll the view.
Your setup (please complete the following information)
Target platform (please complete the following information)
The text was updated successfully, but these errors were encountered: