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
I'm really excited about the latest release.
But is there any ways to dynamically disable back-arrow-icon at the top-left of the screen when setting vrModeEnabled = false? such as: backArrowIconVisible={false} ?
Because to handle this, it is super easy to do, and basically, in general, we don't like this icon in fullscreen.
And another issue is, in my application, we use vrModeEnabled (true and false) in 1 route, the value true/false is given in the params passed to this route from the previous one (you know what I mean, right?)
The flow could be described like this: Route 1 --> navigate--> Route 2 (which has VR components).
Firstly, Route 1 passed vrModeEnabled=false --> We watch VR mode like facebook did.
Next, Route 2 --> goBack--> Route 1.
Finally, Route 1 --> choose option vrModeEnabled=true, navigating and passing it to Route 2
And the app crashed.
So I have to degrade Viro back to 2.1.0 :(
The text was updated successfully, but these errors were encountered:
It is however possible to see the button being rendered as a view inside the XCode view inspector:
A possible solution could be using wrapping the whole VR scene in a Native Module that forcibly removes the view, just like the solution below: googlevr/gvr-ios-sdk#9 (comment)
Will probably give it a go for our project and report back when I have created a solution.
Hello Viro team,
I'm really excited about the latest release.
But is there any ways to dynamically disable back-arrow-icon at the top-left of the screen when setting vrModeEnabled = false? such as: backArrowIconVisible={false} ?
Because to handle this, it is super easy to do, and basically, in general, we don't like this icon in fullscreen.
And another issue is, in my application, we use vrModeEnabled (true and false) in 1 route, the value true/false is given in the params passed to this route from the previous one (you know what I mean, right?)
The flow could be described like this: Route 1 --> navigate--> Route 2 (which has VR components).
Firstly, Route 1 passed vrModeEnabled=false --> We watch VR mode like facebook did.
Next, Route 2 --> goBack--> Route 1.
Finally, Route 1 --> choose option vrModeEnabled=true, navigating and passing it to Route 2
And the app crashed.
So I have to degrade Viro back to 2.1.0 :(
The text was updated successfully, but these errors were encountered: