Impossible to write someting on a field

by Aur茅lien » Mon, 11 Oct 2010 05:31:44 GMT

Sponsored Links

I have build a sort of split view for one of my android applications.
I have made an activity which is a container of a listview and a
framelayout. I use the listview for a menu and in my framelayout, I
load views of different activities. I have read the source code of the
TabHost for building this system.

TabHost source code : ;a=blob;f=core/java/android/widget/

Activities that I load in my framelayout could contain a webview.

The system work pretty well but I have a big issue. When I click on a
field in a webview, the soft keyboard doesn't appear and typing on the
physical keyboard has no affect.

I have made many many researches and I found nothing :'( I really
appreciate if somebody could give me an idea for solving this issue.


Other Threads

1. What is Rasterizer?


i'm trying to understand Paint.setRastezer method

it seems there is only one concrete Rasterizer - LayerRasterizer class

so i created one and added two layers - addLayer(Paint, int, int)

after calling drawSomething it seems that "Something" is drawn twice
with offset specified by two ints passed to addLayer method.

what layer's Paint attributes are used during drawing each layer? i
tried adding some Shader to each layer and got process death - no java
exception, just {*filter*}ed my process...



2. RenamingDelegatingContext overwrites existing database file - bug?

I'm using a RenamingDelegatingContext (RDC) in an ActivityUnitTestCase
to have my application use a database files prefixed by "test." used
during testing.  My application expects a db called "database.sqlite",
so in the setUp() method I create & seed one called
"test.database.sqlite".  I then wrap the context in an RDC with the
prefix "test." and pass it to setActivityContext().

What I see occuring is that the RDC correctly maps calls from my app
for "database.sqlite" to "test.database.sqlite", however it recreates
the db file one first access (my app calls context.openOrCreateDatabase
("database.sqlite", Context.MODE_PRIVATE, null) ).  This destroys all
the seeded test data & causes my tests to fail.

If I just pass in my unwrapped context to the app it works fine (i.e.
doesn't wipe the db file), though obviously it then accesses the app
database, not the test database.  I've observed the state of the /data/
data/<package>/databases directory during test execution & the
"test.database.sqlite" gets created with identical user & access perms
to the original db - in fact I create it using
context.openOrCreateDatabase() then close() it before seeding.

Currently, the way I'm seeding the db is to overwrite it with the
contents of a template .sqlite file from the assets dir, since it
contains a large amount of static data that is prohibitive to insert
every time using SQL scripts (this is also how the app works).
However, I'm written a unit test that shows the RDC overwriting the db
even when seeding is accomplished by executing SQL against
"test.database.sqlite" in the setUp() call.  I've also tried creating
the test database as Context.MODE_WORLD_WRITEABLE with no success.

This seems like a bug to me - unless I'm not understanding how to use
RenamingDelegatingContext properly


3. Issue with simultaneous audio playback and recording

4. Error while booting 32 kernel with eclair RFS on beagle

5. How long does it take for an application to get indexed to the Marketplace?

6. Avoiding garbage collection for smooth 2d animations

7. How long does it take for an application to get indexed to the Marketplace?