Note that Image is an abstract class. One of the direct known
subclasses is BufferedImage, and that is similar to
android.graphics.Bitmap.
Do you want to replace the AWT logic, or re-implement the missing
pieces of AWT the app actually uses?
//Ken
On Jan 6, 1:51 am, Derek wrote:
> Hi,
>
> I'm
}
>
> protected void onPrepareDialog(int id, Dialog dialog) {
> switch (id) {
> case ERROR_DIALOG_ID:
> AlertDialog alertDialog = (AlertDialog)dialog;
> alertDialog.setMessage(alertString);
> //alertDialog.show();
&
You mean the Pictures app?
If you want to launch the app to browse through the images and fiddle
with them, if you examine the log when you launch it manually, an
Activity is started with an Intent like:
new Intent(Intent.ACTION_VIEW, Uri.parse(
"content://media/internal/images/media"))
If yo
Yes, dialogs are reused; that's part of the idea behind having the
Activity manage the dialogs. Generally, onCreateDialog is called only
once for a given ID (you can use the debugger to verify this).
Override onPrepareDialog to modify the created/reused dialog just
before it appears.
--~--~---
You're close. The email address is contained in the DATA column. Using
CONTENT_EMAIL_URI automatically selects only emails (KIND=KIND_EMAIL),
and only returns the columns _ID, NAME, and DATA. (Internally, it does
a join of the "people" and "contact_methods" tables.) You might also
sort on ISPRIMAR
5 matches
Mail list logo
