debugging open core using eclipse

by jerand » Wed, 04 Feb 2009 12:43:01 GMT

Sponsored Links
 I would like to know the steps involved in debugging open core using
eclipse IDE

Other Threads

1. multi resolution image button selectors broken?

It is not the right way. Do not use @drawable-ldpi/, just keep the
same XML file, it will work. The system will find startstopin and
startstopout in the right drawable-XXX/ directory.


2. EditText hint shows extra spaces when inputType="textpassword"


Just wondered, am I the only one to encounter this "strange" behavior.

When placing an EditText inside my activity and setting its
inputType="textPassword"  as follow:

<EditText android:text="" android:id="@+id/EditText01"
                android:hint="This is a hint" android:inputType="textPassword"

The hint is displayed with bigger/double spaces between the words.
If I remove the inputType attribute it all goes back to normal.

I couldn't find a known issue regarding this behavior.

BTW- If you wonder why this is important (it isn't that much) try
putting two EditText widgets one below the other and set the inputType
of one of them to "textpassword" it doesn't look good.

Any comments?


3. Problem in Accessing 2.9 MB Database from Apps

4. Clicking a link in Browser initates a new Intent

5. Samsung's Galaxy stuck in history

6. Android porting feasibility on Versatile Application Baseboard for

7. Motionevent problems - multitouch events give wrong coordinates