You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.
My app has a DrawerLayout which has a FrameLayout for the main content, and a ListView for the side navigation drawer. The main content has a FlipViewController. After flipping the items in FlipViewController, when I try to swipe the navigation drawer, it appears under the FlipViewController.
I think this behaviour is due to this line "surfaceView.setZOrderOnTop(true);". I have tried the solution suggested for a similar problem here but it didn't work as expected. Do you have any suggestion?
Thanks for the fantastic lib and help.
The text was updated successfully, but these errors were encountered:
Hey there, I didn't manage to find a solution to this. All the "solutions" (more like hacks) do not work consistently across devices. So in the end I had to change my app layout to not using navigation drawer. It's a bummer really.
@pkid169 , there is no other way to fix this issue ?. Even I'm facing the same issue. I cannot change the navigation drawer. Tried the suggestions given in the link shared by you. But none of them worked for me.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
My app has a DrawerLayout which has a FrameLayout for the main content, and a ListView for the side navigation drawer. The main content has a FlipViewController. After flipping the items in FlipViewController, when I try to swipe the navigation drawer, it appears under the FlipViewController.
I think this behaviour is due to this line "surfaceView.setZOrderOnTop(true);". I have tried the solution suggested for a similar problem here but it didn't work as expected. Do you have any suggestion?
Thanks for the fantastic lib and help.
The text was updated successfully, but these errors were encountered: