manipulate/generate a drawable

by guruk » Wed, 29 Apr 2009 00:08:57 GMT

Sponsored Links
 hi, is it possible to generate a drawable dynamicaly.
for example i like to place a drawable on a button.
but the design (gfx) is generated dynamicly.
is that possible and how?



Other Threads

1. Where is the UI state information (used in super.onCreate(Bundle savedInstanceState)) stored ?

Where is the UI state information (used in super.onCreate(Bundle 
savedInstanceState)) stored and how can it be deleted from another app 
or command line on a rooted phone?

I need to delete the user data (username, password) of both the native Facebook app (com.facebook.katana) and the stock browser on Android ( on a rooted phone via command line (which I call from my own app) or elsewhere from my own app. This is what I'm calling: rm /data/data/* rm /data/data/* killall -9 rm /data/data/com.facebook.katana/cache/webviewCache/* rm /data/data/com.facebook.katana/databases/* killall -9 com.facebook.katana After I kill the facebook process, I check the running processesand there is no FB process running anymore. I then restart FB via long-press on home and choosing the FB app. Previous username/password still show on the login screen (= same screen as I left it before I killed the app). When I then press 'back' on the device, and then start the app again via home long-press / select FB, the login screen is empty. Where do the values for username/password come when I start FB again in the first place? I assume that the login activity still retrieves the savedInstanceState, but how could that be avoided - or else, where are those UI states actually stored, in order to delete them? Shouldn't the restarted app, after all it's processes are killed, already be in a new lifecycle? Same problem is with the stock browser: if i leave the browser and I'm on the login page of for example where the username/password is entered (but form not submitted yet), then killing the browser process, the values (username) entered into the form will still be there after restarting the app again after it's been killed. --

2. Protecting service from getting killed.

Hi All,
I have a service in my application, that keeps running in the device
to interact with our server.
I found that there are certain application available in Android Market
app, that can kill the services running in a given application.

Is there any way to protect our service getting killed by the 3rd
party applications? This can be certainly done if we run the
application as a system process. But is it possible while running
under dalvik?



3. UBIFS issues

4. Bluetooth name and address in 1.5

5. Tanya : desire tmob froyo

6. drawBitmap differences between 2.1 and 2.2

7. Getting error while trying to compile CameraHardware.cpp