I try to change a displayable (list to a form) and than leave it on the screen for 5 seconds.
In order to implement it I call to Thread.sleep(5000), just after the setCurrent.
The problem isthat the delay does occur but without changing the disply.
If you call Thread.sleep() same thread as Display.setCurrent() then you are blocking the thread that has to set the current display. You have to spawn a new thread that sleeps for x seconds and then changes the screen back.
Multithreading is the answer.
If you look at the description of setCurrent in the API, it says that it returns, and then will change display when it will have time.
Using several threads helps solving that kind of problem ...
It is a bit more complicated. Several TimerTasks run in a single Timer thread, and..
Well, yes it's also multithreading, but it's usually much simpler for just sleeping several seconds. You also don't have to worry about any multithreading synchronization.