Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As far as I can tell, that "pixelated" behavior is an optimization made for scrolling (in Froyo and above). If the rendering is simplified, it makes things like the fling scroll animation require less processing.</p> <p>If you need full browser functionality, I'm not sure you can help it much.</p> <p>Since you've said you're making a game, however, I might have a workaround. I'm hoping your game doesn't need scroll (one full screen), so the scrolling optimization isn't necessary.</p> <p>I've done a simple test with a WebView. On tap, as you mentioned, the rendering gets simplified, and things look a little off. Then once something is clicked (the WebView knows no more scrolling is taking place), things go back to normal.</p> <p>I modified my Layout by replacing a WebView, with a FrameLayout. The FrameLayout contains the WebView and an invisible Button (on top). This Button grabs all the touch events. Then, I selectively choose what types of events the WebView should need, and pass them to the WebView. If a touch down and touch up happen close together, with no movement in betweeen, there's no reason for scrolling, so I haven't seen any of that "pixelated" behavior.</p> <p>Because it was simplest for this example, I've chosen to detect the "MotionEvent.ACTION_UP" event, and when it's complete, I send a down first, so that it simulates a real click. You could certainly trigger on ACTION_DOWN, but you'll get more than one of those if the user swipes or something, and I wanted to keep the logic here simple. You can customize as you see fit, and probably with enough work, even enable scrolling in some cases. I hope the code below is enough to relay what I think works.</p> <pre><code>WebView wv = new WebView(this); View dummyView = new Button(this); dummyView.setBackgroundColor(0x00000000); dummyView.setOnTouchListener(new OnTouchListener() { @Override public boolean onTouch(View v, MotionEvent event) { if (event.getAction() == MotionEvent.ACTION_UP) { MotionEvent down = MotionEvent.obtain(100, 100, MotionEvent.ACTION_DOWN, event.getX(), event.getY(), 0); wv.onTouchEvent(down); wv.onTouchEvent(event); } return false; } }); FrameLayout fl = new FrameLayout(this); fl.addView(wv); fl.addView(dummyView); topLayout.addView(fl); </code></pre> <p>EDIT: If you don't want to edit PhoneGap source, you might be able to do something like the following to change the PhoneGap layout... It's untested, but seems like it should work:</p> <pre><code>@Override public void onCreate(Bundle arg0) { super.onCreate(arg0); super.loadUrl("file:///android_asset/www/index.html"); // Get the "root" view from PhoneGap LinearLayout droidGapRoot = super.root; // Create a new "root" that we can use. final LinearLayout newRoot = new LinearLayout(this); for (int i = 0; i &lt; droidGapRoot.getChildCount(); i++) { // Move all views from phoneGap's LinearLayout to ours. View moveMe = droidGapRoot.getChildAt(i); droidGapRoot.removeView(moveMe); newRoot.addView(moveMe); } // Create an invisible button to overlay all other views, and pass // clicks through. View dummyView = new Button(this); dummyView.setBackgroundColor(0x00000000); dummyView.setOnTouchListener(new OnTouchListener() { @Override public boolean onTouch(View v, MotionEvent event) { // Only pass "UP" events to the specific view we care about, but // be sure to simulate a valid "DOWN" press first, so that the // click makes sense. if (event.getAction() == MotionEvent.ACTION_UP) { MotionEvent down = MotionEvent.obtain(100, 100, MotionEvent.ACTION_DOWN, event.getX(), event.getY(), 0); newRoot.onTouchEvent(down); newRoot.onTouchEvent(event); } return false; } }); // Layer the views properly FrameLayout frameLayout = new FrameLayout(this); frameLayout.addView(newRoot); frameLayout.addView(dummyView); // Add our new customized layout back to the PhoneGap "root" view. droidGapRoot.addView(frameLayout); } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POImages get pixelated when the screen is touched
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMatt
    1. USMatt
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for your post, however as I said I'm using Phonegap and my app is 99% built with Javascript, I just have one Java Class called App.java, you can see it here http://phonegap.com/start#android Do you still think that your solution could work if I can somehow integrate you code?
      singulars
      1. PO
      1. USadrien54
    2. COI hope the additional example above will help.
      singulars
      1. PO
      1. USMatt
    3. COI tried it, after import the missing classes I get the app running, however the screen is black and I have no warning or info that could help me. Thx for your help anyway.
      singulars
      1. PO
      1. USadrien54
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload