Hi.
I added a widget to view port from my character BP then I set its visibility to hidden while the sequencer was playing in Level BP then set it to visible again after sequencer then touch interfaces were disabled.
I reproduced this issue in third person template like below.
first I add a widget from character BP then in Level BP…
Hello ,
From taking a quick look at your post it would appear that your widget is capturing your touch input. If you set the entire widget to visible, this will make it so that all widgets capture input. For a quick test could you try setting the widget to self hit test invisible to see if your touch is still blocked? If the issue no longer occurs this will mean that you need to manage the visibility of your widgets so that only the widgets you would like to capture input do so. You can hover over each visibility setting for more information. I hope that this helps.
Make it a great day
1 Like
I tried all visibility options of the widget but no one solved this problem.
as I am dragging the touch interface it won’t get blocked if a widget gets hidden and visible but as soon as I leave it, it gets blocked
Does this issue only occur when using touch, or can this be reproduced using the click event?
click events all work fine.
buttons of other widgets work fine
buttons of that widget which its visibility was toggled also works fine
only touch interface is blocked
I have a couple of questions for you that will help narrow down what issue it is that you are experiencing.
Quick questions:
- I see that you have reproduced this in the third person template, could you provide a detailed list of steps to reproduce this issue on our end?
- Could you provide screen shots of all blueprints/widgets that may be involved with this issue?
1- open third person template(mobile project) and create a widget.
2- in character BP add that widget to view port
3- on begin play of Level BP toggle the visibility of the widget
then you will see that touch interfaces are blocked
Hello ,
After setting up the test above, I was able to find that I could not move the joysticks after the Widget was set to visible. Is this the indicator that you are using when testing your touch input? If so, this is working as intended. After setting the visibility to “Self Hit Test Invisible”, I was able to once again use the virtual joysticks. If this is not the test case that you are using, I will need you to provide a more detailed list of steps on how to reproduce the issue that you are seeing in a clean project. Along with the method you are using to test for success/failure.
Hey
how would you set Self Hit Test Invisible?
I click on the main panel(canvas panel) and then set it from there
When I ran my test, I set it dynamically (example provided below). The reason I needed to do this was because in your example you are changing the visibility at runtime. This means that the default setting will no longer be “Self Hit Test Invisible” for the canvas panel after you set it to “visible”.
Example:
Thank you so much. it worked