Using A-Frame 1.2.0, the default view when visiting the URL on a mobile phone is a mono VR mode, with buttons to switch to AR and VR.
This mode also allows non-AR GUI elements like HTML buttons to be placed on the screen, they will overlay on top of the scene, with some CSS.
Is it possible to make the default view when visiting the URL just as it is currently, but with the AR camera? I.e. leave the AR and VR buttons, leave whatever is added to the page with HTML and CSS, but turn on the device camera?
Or, if that's not possible, how to switch to the AR mode immediately on load?
Related
I would like to embed grafana dashboard to an angular application. Tried dashboard share and panel share. It gives a URL to be added in an iframe. But it displays all the editable options too. I would like only panel area to be visible (only the area inside the green rectangle in the screenshot)
You can use the Kiosk mode.
Manually, you can enable it by clicking on the icon in the upper right corner (on hover: cycle view mode).
For using it when embedding a dashboard, you can enable it by adding kiosk to the URL parameters. Example: https://www.your-grafana-instance.com/d/dashboard-id/dashboard-name?orgId=1&kiosk
I have built an aframe application. I activate the VR mode on the first page. However, as soon as I e.g. switch to the next html page via a link, the VR mode closes again. How can I make it continue to exist automatically?
I am using an Oculus Quest 2.
When using aframe on mobile and going from page to page I want it to stay in VR mode after the user clicks the VR icon in aframe.
However at the moment whenever you go from one page to another it kicks the user out of vr and the address bar appears so you have to manually click the VR button everytime you want to enter fullscreen again.
Is there a solution to this?
You can check out my aframe application below:
https://www.360belfast.com/app/options.html
I've read desktop solutions online but not much for mobile.
It's not possible. On mobile, A-Frame relies on fullscreen mode that doesn't persist on navigation. It has to be triggered by user gesture on each individual site. It's a browser policy that cannot be worked around. In-VR navigation is only available with a supported headset on Firefox and Supermedium on desktop, and Oculus Browser and Samsung Internet on standalone headsets.
Is it possible to not show a context menu when the user performs a force touch. And instead show a custom interface controller modally.
Or is it even possible to programmatically detect a force touch.
There is no way to detect a force touch. You can only show a menu on the force touch.
From an Apple dev evangelist on https://devforums.apple.com/thread/254831?start=0&tstart=0
There is no API to directly respond to a Force Touch. Performing a
Force Touch within a WatchKit app will display the menu (if there is
one) for the visible WKInterfaceController.
Anyone know of a skinnable audio player (or something similar to Windows Vista audio control in task bar) that i can embed in my website?
A player that can be customized to
use a 'speaker' icon instead of a
'play' icon. When the speaker is
clicked, the volume can be adjusted
or turned off.
The option of being able to autoplay
and set the default volume level.
dunno if this is any use to you - http://mediaplayer.yahoo.com/