How to prevent touch screen from trying to scroll inner containers or embedded views instead of parent container

Ignition
1

I'm trying to troubleshoot a nuisance bug specific to touch screens / perspective mobile app.

I have a layout where I have a tab container and views embedded within it. Each of those views is a coordinate container as they are P&ID layouts. The client did not want breakpoint containers and smaller designs but rather a pan/pinch/zoom style so the screens are identical on mobile vs PC.

What happens is sometimes when things are slightly zoomed in, I touch to pan on the W01 portion of the screen, it tries to move the embedded view within the tab container, which has no where to move and thus does not actually move. However if I touch higher on the tab portion then I can pan the whole screen.

My question is are there any settings I can try to try and fix it so that it cannot pan the inner containers? Would toggling the useDefaultViewWidth/Height affect this, would the style overflow options help? I've tried various combinations so I'm at a loss if I'm just missing something. When they first load the screen it works fine but if they touch on any blank space within the W01 view and then try to pan it seems to happen.

Layout:

image
image210×215 4.62 KB

Note: I know I should probably convert the root back to a flex container. This was the latest round of just trying a few troubleshooting things.

2

I don't know how to solve your issue, but I assume you're using a pan/zoom container provided by one of the 3rd party modules?

3

You might could try adding pointerEvents:None to the containers style that you don't want to pan. This will ignore touch actions and click actions. If you want those containers to still have click actions, you should be able to add touchEvents:None instead. (untested)

4

Thanks, I'll give those a try. Would that still allow embedded objects inside those containers to be clickable though? They still need to be able to tap on a valve to launch a faceplate.

5

touchEvents:None should, but again, I haven't tested it. You'll have to try it and see.

6

Went to implement dkhayes suggestion and then noticed that one page had the scrolling issue while another did not. Tracking down one of the levels of embedded containers did not have the use default height/width enabled. Turning that on resolved my problems.