Depends on if you use custom images for the UI elements. If so, you
will need to make different versions for each screen configuration
(LDPI, MDPI, HDPI and the xtra large one if you truly avid in this).
If your UI is comprised of only the standard UI components that the
Android SDK presents you,
h. OK. But without creating a new thread the changes made to the
button are not visible (END View pops up).
Can you give me a suggestion the original problem please?
Thank you
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
Hard to say what you really want from the snippets of information and code
you provided.
Generally speaking you normally only call setContent() to setup your screen
from your activity's onCreate() method, not when some state changes that
needs reflection on the UI.
When you have state changes you
You want a delay between changing the button's text and showing the
new content-view?
If that's the case,
private void markUser(int index) {
btnArray[index].setText(mark);
btnArray[index].setClickable(false);
postDelayed(new Runnable()
Yeahh.. I found out..
runOnUiThread() is the solution
Thread t = new Thread() {
public void run() {
f.runOnUiThread(new Runnable() {
@Override
This code is just wrong: you are starting a new thread just to run
code back on the UI thread. All your code amounts to doing nothing but
run the content of the run() method. Even worse, if holdGame(3000)
triggers a thread sleep, you are blocking the UI thread.
On Thu, May 14, 2009 at 2:59 AM,
6 matches
Mail list logo
