I'm working on a program which used the functions as title.
There's a problem that the tunctions above do not have their metrics on API website.
To avoid misunderstanding, here is an example about "metric" I metioned before.
Ex. size = pixel, pressure = kilogram(kg)
I have no idea about the metric at all.
View 1 Replies
Debugging on my G1 phone, I am trying to use android.view.MotionEvent.getPressure() and MotionEvent.getSize().
For MotionEvent.getSize(), I always get 0 (the documentation says it returns a value ranging from 0 to 1;
For MotionEvent.getPressure(), it seems to me this actually reflects the real finger touch size, as opposed to "pressure"; for me, I get values range from 0 - 0.63.
Am I missing anything or is it a known bug of the SDK?
This may be in the wrong forum, but I can't figure out where else to post it.
The maps app (the one from google your phone comes with by default) only shows routes in feet and miles. Is there no way to get it in meters? I can't find any settings for this!
I was expecting the getEdgeFlags() method of MotionEvent to tell me when a MotionEvent had reached the edge of something, but the value returned from getEdgeFlags() is *always* zero. Is this the expected behavior? The documentation says that the flags indicate when a touch has reached the edge of the display. I've tried this on a real device and in the emulator, and the location coordinates never quite reach the edge of the display, and getEdgeFlags() always returns 0. By "never quite reach" I mean that if dragging a finger off the left edge of the display, the smallest X I got was 2. Reaching the edge of the view doesn't seem to change the value returned either.
I suppose I could set the flags myself using setEdgeFlags() using calculations with known dimensions of the object whose edges I care about. Is that how it's supposed to be used? Is this broken for now?
I have a display that is 854x480 pixels. Why is it that the MotionEvent.getX and getY methods return floats? As far as I can tell, the pixels on the display are discrete integers, there is no such thing as a half a pixel on the display.
View 1 Replies View RelatedI am implementing OnTouchListener and am receiving MotionEvent objects. Some ACTION_MOVE events reports absolute X/Y coordinates, while some reports relative coordinates.
How can I ask a MotionEvent what kind of coordinates it currently represents?
I am having trouble getting my activity to generate a MotionEvent.ACTION_UP. Probably a beginner's error.
In LogCat, I'm only seeing the ACTION_MOVE event (which is an int value of 3). I also see the X/Y coordinates. No ACTION_DOWN and no ACTION_UP.
I looked everywhere for a solution. I found one question on a forum that seems to be the same as my issue, but no solution is proposed: http://groups.google.com/group/android-developers/browse_thread/thread/9a9c23e40f02c134/bf12b89561f204ad?lnk=gst&q=ACTION_UP#bf12b89561f204ad
Here's my code:
CODE:..........................
I'm writing a simple tile based game using a canvas and a 5X5 grid of tiles. To determine if a tile is clicked I look at the MotionEvent supplied by onTouch. I get the coordinates when MotionEvent.event is ACTION_UP and translate to tiles. This works great on the emulator but when I touch on a device the actual coordinates of the touch register higher than I'd expect as a end user.
I'm wondering what strategies people have used to get a closer to "expected" result. Do you use a simple Y offset? Do you average the coordinates over the life of the touch? Do you use other methods?
I need to have a left, right and click event in my App.
I am trying it like below:
CODE:...........................
I couldn't find a definite reference for the size of a MotionEvents history, when there are multiple pointers. The reference says that if you use a getHistorical* function, you might pass it a history position which is somewhere between [0..getHistorySize()-1]. But in a lot of examples handling multitouch if there are multiple pointers they only use history positions between [0..getHistorySize()/ getPointers()-1] (so they divide the history's size with the number of pointers). Which one is the correct way?
View 8 Replies View RelatedIt seems like making any call to event.getHistoricalEventTime(int pos) when there is historical touch position data available makes my application crash. I've searched online and it seems like no one ever uses this method.
View 4 Replies View RelatedMy app forwards MotionEvents, reported by GestureDetector.OnGestureListener, to a worker thread. Right now i am doing it by calling MotionEvent.obtain, pass the obtained copy to the worker thread, handle it and recycle it at the worker thread. Is it required to obtain and recycle a MotionEvent if it is passed to another thread? Or could it safely be skiped? If i am making things overly complicated, could you please explain me at which conditions MotionEvent.obtain is usually called?
View 2 Replies View RelatedI am developing one application in which there is an imageview...in which i want to move left or right using mouse touch...for that i found "android.view.MotionEvent" but in MotionEvent there are few events among that ACTION_CANCEL 2. ACTION_DOWN 3. ACTION_UP ......etc.
Hence there is no such event for "LEFT" and "RIGHT" action....so is there any other way to implement the "LEFT" and "RIGHT" move ?
I'm trying to get coordinates of the mouse, but there seems to be no easy ways. Can't make the MotionEvent object because the constructor is private. Can anyone please tell me how to get the coordinates of the touch/ pointer/mouse? I only want the touch coordinates of ImageView, but wouldn't mind the touch coordinates anywhere on the screen.
View 2 Replies View RelatedPurpose of the app:
A simple app that draws a circle for every touch recognised on the screen and follows the touch events. On a 'high pressure reading' getPressure (int pointerIndex) the colour of the circle will change and the radius will increase. Additionally the touch ID with getPointerId (int pointerIndex), x- and y-coordinates and pressure are shown next to the finger touch.
Following a code snipplet of the important part (please forgive me it is not the nicest code ;) I know)
CODE:.............
The problem:
A HTC Desire running Android 2.1 is the test platform. The app works fine and tracks two finger without a problem. But it seems that the two touch points interfere with each other when they get t0o close -- it looks like they circles 'snap'to a shared x and y axle. Sometimes they even swap the input coordinates of the other touch event. Another problem is that even though getPressure (int pointerIndex) refers to an PointerID both touch event have the same pressure reading.
As this is all a bit abstract, find a video here: http://www.youtube.com/watch?v=bFxjFexrclU
My question:
Is my code just simply wrong? Does Android 2.1 not handle the touch events well enough get things mixed up?Is this a hardware problem and has nothing to do with 1) and 2)?
I have been racking my brain to try to figure out what is going wrong here. I wanted to experiment with multi-touch, so I decided to add the controls for LunarLander to the touchscreen.
Instead of adding buttons, I defined regions on the screen that when touched, would act like the buttons on the keyboard (for example, the gas fires as long as you press the screen in the area defined for the gas button, and stops firing when you release.)
To do this, I added the onTouchEvent override to the LunarView class as follows:
CODE:.....................
I'd really like to know what the state of that fix is as 2.1 is rolled out onto first generation (MSM7200-based) devices. As it stands, I don't see much of a problem with touch eating up CPU on the Droid and N1 but those are much faster phones so I don't think it would be quite as pronounced on them. My current 1.6 devices (G1 and Tattoo) cut my framerates in half during any touch (with the sleep hack, even). I optimized my new games so that they would run well-enough (25-40fps) on that hardware but they have very touch-centric interfaces so won't work well with that bug. I talked to a few people who run 2.0/2.1 mods on their G1s and they said the problem isn't any better. They still see the big slowdown. I tested on my 1.6 emulator vs a 2.1 emulator and there is a huge improvement. The 1.6 emulator slows down just like my G1 does and the 2.1 emulator shows only a tiny bit of slowdown, which is what I was hoping for. That's encouraging, but I have yet to see a real 2.1 MSM7200 update in the field so I don't know what to think yet.
View 10 Replies View RelatedI'm running into some issues with input events and garbage collection, or more precisely object allocation. I am creating a game and have pretty much got my head around the OpenGL environment. I've digested all the relevant material I could find regarding performance, memory allocation etc (and watched the excellent presentation by Chris Pruett - http://code.google.com/events/io/2009/sessions/WritingRealTimeGamesAn...). I've pretty much eliminated any object allocations after initial setup from my game (which is still in its infancy), but I'm still getting a bunch of GC calls, like this:...........................
View 6 Replies View RelatedI have added this line in my androidManifest.xml <uses-permission android:name="android.permission.INJECT_EVENT"/>
I am trying to execute following code:
CODE:........
Both above lines are throwing exception W/System.err(762): java.lang.SecurityException: Injecting to another application requires INJECT_EVENT permission.
Do we need anything else too to get it working ?
I have a relative layout built from XML.I am capturing the onTouchEvent.When I touch the screen anywhere except over the TableLayout or ImageButton
the MotionEvent.ACTION_DOWN and MotionEvent.ACTION_MOVE
events work fine.
how to make the onTouchEvent() work on the TableLayout and ImageButton views?
The purpose of the exercise was to have a drag method working over the relative layout,no
Maybe manipulating the layout_margin values? I was contemplating a transparent canvas overlay but haven't figured that out yet.
Code snippets below
XML
<RelativeLayout
xmlns:android="http://schemas.android.com/apk/res/android"[code]......
My Android app is experiencing this crash randomly during operation, and I think it is due to a pending MotionEvent that is dispatched to a null object, but not sure.
Here is the crash output:
CODE:.................
My Android app manually creates a custom WebView and adds it to the ViewGroup in the Activity.onCreate() method like this:
CODE:....
The reason for doing it this way was to be able to get to the constructor for the WebView in order to pass getApplicationContext() instead of this to the constructor, which was a workaround for a memory leak in 2.1.
The issue, I think, is that this Activity is restarted frequently. This causes the normal chain of onStop(), onDestroy(), onCreate(), etc... to happen often.
So my question is, could the crashes be due to a MotionEvent being dispatched to an instance of MyWebView that was attached to an old Activity that has been garbage collected? Such as if the user clicked something in a webview right before this actvity was recycled?
Another thing to note is I'm seeing these messages following a call to onDestroy() /webviewglue( 436): nativeDestroy view: 0xd738d0
This started happening in Android OS 2.2. I've submitted a bug to Google, but not sure it is their issue.
today i meet the problem.i need technic can control the android machine from server.then i want send data from server to android with no request from android.
View 2 Replies View RelatedI'm trying to open a dialog window, but every time I try to open it it throws this exception:
CODE:.................
I'm creating it by calling showDialog with the display's id. The onCreateDialog handler logs fine and I can step through it without an issue, but I've attached it since it seems like I'm missing something:
CODE:............
Is there something missing from this? Some questions have talked about having this problem when creating a dialog from onCreate, which happen because the activity isn't created yet, but this is coming from a call from a menu object, and the appContext variable seems like it is correctly populated in the debugger.
I'm writing an application which connects to a back office site. The backoffice site contains a whole slew of JavaScript functions, at least 100 times the average site. Unfortunately it does not load them, and causes much of the functionality to not work properly. So I am running a test. I put a page out on my server which loads the FireBugLite javascript text. Its a lot of javascript and perfect to test and see if the Android WebView will load it. The WebView loads nothing, but the browser loads the Firebug Icon. What on earth would make the difference, why can it run in the browser and not in my WebView? Any suggestions.
More background information, in order to get the stinking backoffice application available on a Droid (or any other platform except windows) I needed to trick the bakcoffice application to believe what's accessing the website is Internet Explorer. I do this by modifying the WebView User Agent.Also for this application I've slimmed my landing page, so I could give you the source to offer me aid. package ksc.myKMB;
import android.app.Activity;
import android.app.AlertDialog;
import android.app.Dialog;
import android.app.ProgressDialog;
import android.content.DialogInterface;
import android.graphics.Bitmap;
import android.os.Bundle;
import android.view.Menu;
import android.view.MenuInflater;
import android.view.MenuItem;
import android.view.Window;
import android.webkit.WebChromeClient;
import android.webkit.WebView;
import android.webkit.WebSettings;
import android.webkit.WebViewClient;
import android.widget.Toast;
public class myKMB extends Activity {
I already have JavaScript on the web browser on, the problem is the web view is acting to different from the web browser.
I want to implement my own Tokenizer base on the file
"MultiAutoCompleteTextView.java",
but I encounter an error "com.android.internal.R cannot be resolved" when I try to
import "MultiAutoCompleteTextView.java" to my project.
code:.................
I haven't research any solutions to resolve this problem.How to correct "com.android.internal.R.attr.autoCompleteTextViewStyle" my own attr?
1- Does Android Browser (Éclair code base) support the "plug-in" or not?
2- Why "Google Gears" support is removed from the clair code base?
I searched the forum and came to know that earlier version of the Android does not support it at all? Here is the link for that, but this query asked in Dec'2008.
At first,I have a database created by using Ruby on rails.I just already implement insert function(HTTPPost) in my Android Application and it's work.But I don't know how to retrieve specific record from my databases and insert it back to specific record in Android (Like edit function in RoR)This is my insert code :
private void insertComment() {DefaultHttpClient client = new DefaultHttpClient();HttpPost post = new HttpPost("http://10.10.3.87:3000/comments");
// Configure the form parameters
List<NameValuePair> nvps = new ArrayList<NameValuePair>();
nvps.add(new BasicNameValuePair("comment[content]", t_comment.getText().toString();
nvps.add(new BasicNameValuePair("comment[id_account]", "1"));
nvps.add(new BasicNameValuePair("comment[id_place]", Integer.toString(position)I really try many ways out but it doesn't work and it takes very long time to fight with this piece of code. Actually, I really don't know how to specify RowID to HTTPPost.
I am doing some android development, and now I need to send some android application generated data onto a remote server (a database)?How can I do that? can I use direct JDBC connection and sql?
View 1 Replies View RelatedSo i am making a android app, and i want it to be so if i call lets say 911 it sends my GPS coordinents to a certain IP, i know everything but how i make it so if i call 911 it sends the info and how i can make it send the info to the IP via 3g,
View 3 Replies View RelatedI released updates of my apps yesterday and they are being hidden from android 1.5 and 1.6 phones.
This is due to a Market bug which hides apps with bluetooth permissions from android 1.5 and 1.6.
Come on Google fix the market. We spend countless hours making are apps work on ALL android versions and now you do this...
This issue has been raised since June, but has only affected me since i made an update to the market yesterday.