Eclipse warning

by Chihau Chau » Sun, 12 Apr 2009 05:14:51 GMT

Sponsored Links
 hi everybody,

Since previous releases of android SDK (I think since version 0.9), I
have a warning when I run a aplication from Eclipse.

"Warning once: This application, or a library it uses, is using
NSQuickDrawView, which has been deprecated. Apps should cease use of
QuickDraw and move to Quartz."

How I can solve this? I am running Eclipse 3.4 (Ganymede) in Mac OS X 10.5.6.


Chihau Chau


Eclipse warning

by Mark Murphy » Sun, 12 Apr 2009 08:54:00 GMT


Ignore it. AFAIK, it is an error raised by the qemu emulator system, not
by anything in Android proper.

Mark Murphy (a Commons Guy)  | 

Android App Developer Training: 


Sponsored Links

Other Threads

1. Associate app to open email attachments

Hi all,

I've written an app that can handle the VIEW action for a given
mimeType, say "application/foo". By adding the following to
AndroidManifest.xml the Browser automatically uses my app to open
downloads of that type:

     <action android:name="android.intent.action.VIEW"/>
     <category android:name="android.intent.category.DEFAULT"/>
     <data android:mimeType="application/foo"/>

The GMail app also tries to use my app to Preview attachments of that
type, but it's passing a URI with scheme "gmail-ls://" rather than a
"file://" URI. I guess I need to use a ContentProvider to get the
attachment data, I haven't looked into that yet.

But the real mystery is the Email app... there just doesn't seem any
way to make it open the attachments.

Any pointers? Opening attachments is a very common requirement of
course, and I would expect the Android platform to encourage
developers to write apps to handle more mime types. Instead I couldn't
find any answers:


2. sensors.h file descripter help

I am in the process of writing the sensor glue for the os4000-t
digital compass/accel device. This reports nmea style string via TTL.

I have modeled my file after sensors_qemu.c example.

I have it working partially. The first process which tries to use
SensorManager is able to receive orientation updates. Any processes
launched afterward are not.

I believe I have traced it to the "open_data_source" and "data_open"

It seems that the "data_open" function is not receiving the FD that
"open_data_source" retrieves. From my logs, it seems that
"open_data_source" is actually called from the first process (system
screen orientation) when the second process (android app) tries to
open sensor up for polling. data_open is invoked under the pid of the
second process but it does not receive the right FD.

I assumed that:
int (*data_open)(struct sensors_data_device_t *dev, int fd);

the fd there would be from:
int (*open_data_source)(struct sensors_control_device_t *dev);

but it is not happening.

As I mentioned, the first app, whether it be the system screen
orientation manager (when enabled) or a standalone app which utilizies
SensorManager, everything works great. If I try to relaunch the app
(since it would be under different PID) it isn't able to obtain valid
FD to talk to the device.

If you have any experience with writing the sensors.c glue for any
devices, would greatly appreciate any hints or tips.

3. Small Change to Camera app (get source code)

4. Motorola Android Phone Coming to Verizon?

5. HVGA T-Mobile G1/G2 vs. iPhone

6. Architecture dilema

7. Upgrading from SDK 1.1 to 1.5 - map API key not valid?