According to;
https://developers.google.com/vr/discover/daydream
The Daydream controller features:
A touch pad that allows users to interact with virtual objects or easily scroll through a media collection.
An app button that you have complete control over for your experience.
A home button ....................
Volume controls ..................
.
In the three.js DaydreamController.js
// app button not available, reserved for use by the browser
Can anyone explain the discrepancy.
I would like another button to re-centre the gamepad only.
(to comply with "UX-D6: App recenters appropriately with respect to the experience ; https://developers.google.com/vr/distribute/daydream/design-requirements)
Related
I am developing an app very similar to Uber in Nativescript + Vuejs.
There is a moment in the flow of the application, where a driver, having accepted a trip, runs the device's default satnav application (eg Google Map, Waze, etc.) to perform GPS navigation. The point is that while the driver is navigating -with the maps application in the foreground- there is a use case where he can receive an offer to take another trip (as the current trip is soon to end), which he has to confirm or reject/dismiss. Is there a way to do one of the following scenarios:
Show a dialog that appears above the map application showing trip details and two CTA buttons? Like a dark overlay maybe?
Return my application to foreground to show the dialog (leaving the maps application in the background). Important detail is that the map application is opened programmatically by my application.
Please remember that I am using nativescript and not Java/Obj-C.
Thank you!
I am not really understanding what's the difference between using a notification to build a ui where you can perform an action (click on button or display a card) and using the GridViewPager to do that.
I am creating an app where you can perform actions with a button (following the spec of google, on action/button per page). I am using the GridViewPager to do so. But looking at the samples that google provides and looking at the different wear apps that I could find, it looks like a lot of the applications have the same design : buttons with a blue background circle, provided by the Notification class.
In which case should I use the GridViewPager or the notifications?
Im writing an application for workers in our factory and one of requirements is that they should be able to take images using camera integrated in PDA with WM6.5.
The main difficulty is, that thay MUST NEVER EVER be able to enter windows, Start button, desktop etc. They are allowed ONLY to see my fullscreen application.
I succesfully deactivated BlueTooth + red, green and volume buttons (if you are interested, im pasting links here)
http://forum.xda-developers.com/showthread.php?t=546737
http://msdn.microsoft.com/en-us/library/bb431750.aspx
http://social.msdn.microsoft.com/forums/en-US/vssmartdevicesvbcs/thread/a4f9f41d-47a8-4080-8613-2c2ddcf4c012/
And now I have to implement the camera function. But as CameraCaptureDialog opens a new dialog and shows start button, task bar and allows user to open list of applications, I must not use it.
I must create my own dialog that will show the Live Preview in a panel or in an imageBox and photo will be taken using a button.
I searched the whole internet and found only DirectShow.NETCF (but people do not recommend it) and CameraCaptureDialog.
Can I somehow redirect the CameraCaptureDialog to my dialog? Or can I access camera directly via .NET framework? Or can I modify the CameraCaptureDialog not to show Start button, menu etc?
Looks like you have a bit of a challenge. I agree that Directshow is a questionable solution, but it may be your only option. I did get http://alexmogurenko.com/blog/directshownetcf/ to work, but only on low resolutions.
A better option might be to find a device that does not show the menu bar/start button. AFAIK, the HTC HD2 has a very clean Cameracapturedialog..
Good luck.
Does Palm/HP WebOS 3.o / Enyo framework support image maps??
I have an HtmlContent control that contains "image maps" -- an image with links embedded in hot spots using the HTML "usemap" attribute. However my those links don't seem to be active, and I cannot click on them. (The same page when opened in a regular browser allows me to click, but when that HTML content is in an HtmlContent control, the links seem to have disappeared).
Any ideas?
Also i did check that the click events are not being fired -- the click handler for the HtmlContent control does not fire. This does not happen when the entire image has an href -- in that case things work fine. But if the image has a map associated with it, then the links are not active, and clicking on the link regions does not seem to fire click events.
It's not Enyo that needs to support imagemaps, but the lower level WebKit system. Right now, webOS should handle rectangular image maps, but polygon maps weren't being handled correctly.
I have recently started on a project developing a window mobile/ce buisiness application. I have a ui design that uses a wizard to capture input data. To get the wizard started we open a windows form and maximize it. The form has one panel on it that is set to the size of the form. We pass a reference to the panel into the wizard controller as a container for the wizard user controls (each wizard step is a user control and the user control's size is set to that of the panel and thus the windows form. When viewed in a windows mobile emulator this works great the user control takes up the entire screen and the controls on the wizard step control are all visible on the screen with no vertical or horizontal scroll bars visible. When we load this onto one of the potential handheld devices the windows form doesn't fit exactly onto the screen as I would expect. There are both horizontal and vertical scroll bars and the controls aren't all visible. Does anyone have any hints and tips on getting around this problem? Is it possible to maximize a windows form in such a way that it exactly fills the screen on any mobile or ce device?
You need to check the screen resolution of your emulator and of your handheld device.
I suspect you are working on different screen resolutions.
If it's the case, then set the screen res for your emulator to match the screen res of your device. If for some reason this is not possible, just create your form to match the screen res of the device and try to fit all your UI in that limited space.
If you need to support many screen resolutions, you have 2 approaches:
1. Develop for the lowest res. This might look a bit ugly for higher res devices
2. Use anchors and control docking when defining your form layout.