MonoGame: Disable mouse input on Android - android

I'm developing a monogame game app for several plattforms including Android, iOS and Windows Universal. Therefore I want to support touch as well as mouse input.
Problem is that on Android the initial mouse position is at (0,0) and is triggering a hover effect inside of the app which is not supposed to happen. Is there a way to disable Mouse input for android? On iOS I just set the mouse position out of the Viewport to (-1,-1). Which is hacky but it works. Unfortunately on Android Mouse.SetPostion() is not working for some reason.
Any other idea how to make the mouse disappear in MonoGame for Android?

Related

MRTK Button press not triggering correctly on Android despite doing so in the Unity Editor

I am developing an MRTK app for Hololens and mobile platforms and I am using the default MRTK buttons with scripts assigned to them.
In-Editor (when using the hand interaction simulation tool) the buttons work as intended (instanciating a 3d model on press, either with finger touching or left mouse click while the button is centered).
When testing the buttons on my mobile phone on Android, tapping the buttons triggers the sound of being pressed, but nothing happens. I use the DefaultHololens2InputSystemProfile in the MRTK.
Things I checked:
Button Events triggering correct in the Editor
Things I don't know how to check:
EventConsole/Some kind of output on Android to check if the Assets or the Buttons are the problem
Any ideas of what I can try?
You got to use the Onclick() event instead of the ButtonPressed, -Released etc. events you usually use for clicking in AR. You should find it right below the ButtonReleased event.

Android Accesibility system-wide zoom controlled via Keyboard?

I am developing an accessibility based application which lets users use the application using a bluetooth keyboard, hands-free. What I need now is for the users to be able to zoom in and out, in the application(and possibly the whole android system) using certain key-combo(say Ctrl+Alt+?).
The zoom should work something like the Magnification Gesture feature of the android accessibility settings.The magnification on that works on triple-tap to activate(which I want to activate by a certain key-combo) and pan around using two finger swipe( Which probably would be the direction keys from keyboard).
The only thing I have found even remotely related to doing something like this is the Android Accesibility Service. But I dont think it let's me get keyboard key-combo and then zoom-in the screen.
Is there any way we can do this in Android? Do I need to go AOSP and make my own Android OS version probably? Please help!

Can I enable mouse/desktop-like text selection behavior in an Android app?

I'm using ARC Welder to turn my Android app into a Chrome OS app. Most of it works perfectly, except that text selection with a mouse behaves like it would on a touch device, requiring long-clicking or double-clicking on words, and then dragging the ends. Is there a way around this?
As CommonsWare points out, this is the Android behavior.
Feel free to file a bug even for a feature request.
We are open to allowing the behavior to be changed, but it also seems like something that should be left up to the end user (how do they expect to interact with an Android app on a Chromebook?)

Trigger.io and KendoUI Mobile - Layout / view doesn show up until touch

I am trying to work with trigger.io and Kendoui Mobile.
the point is, when launching the mobile app on emulator all works like expected - but when it runs on android mobile the Layout / View doesnt show up until you touch the screen or turn the mobile to landscape or viceversa.
with a tabstrip of kendoui one time showed up you can swtich between views with no problems.
but if you redirect to another view with different layout you have to touch again the screen to show the content (it just shows just the background of body until touch).
the telerik guys at the moment dont know from where it comes from as they tested it with phonegap and no problems.
Maybe the trigger.io guys can find out why it happens?
Best regards
marc
It looks like this is an issue with hardware acceleration on Android 4.0, probably an unfortunate interaction between whatever hardware accelerated transitions Kendo UI use and that particular version of Android.
Phonegap seem to have hardware acceleration disabled by default, which is why they would not be affected.
As a fix we are going to add an option to disable hardware acceleration on that particular Android version, which we'll have live by the end of the week.

Android Hide mouse pointer programmatically in my own app

I know there is a similar question here: Moving mouse pointer on Android screen programatically but it doesn't seem to answer my needs (particularly because the answer was "not possible"!)
My client has an Android phone which is connected via some sort of bluetooth dongle to a wireless keyboard/trackpad. This is all working fine and I have written some software to react to keypresses. The problem is that the client is NOT interested in seeing a mouse cursor on the screen (this particular keyboard will have all except a few buttons covered up and will function as a remote control, the trackpad is inaccessible so the pointer sits in the middle of the screen uselessly).
So - is there any way for my app to get rid of the visible mouse pointer (either just for itself or for all cases, I don't care - this app is the only thing they want running on the phone). If I can't hide it can I move it to a corner, or can I change it to look like a plain white box instead of an arrow, or something else?
Any ideas would be greatly appreciated
Thanks
So - is there any way for my app to get rid of the visible mouse pointer (either just for itself or for all cases, I don't care - this app is the only thing they want running on the phone). If I can't hide it can I move it to a corner, or can I change it to look like a plain white box instead of an arrow, or something else?
All of this may be possible with custom firmware. None of this is possible via the Android SDK.
You may be better served simply by replacing the "wireless keyboard/trackpad" with one that does not have a trackpad.

Categories

Resources