disable automatic calling of paint

[honest_success]

I have one application based on canvas. Application works fine on n96 and emulator but there is some issue in 6300. When user will go to command and then come back some how pain() invokes automatically. Is there any way to cancell all that automatic invokation of paint() ?

[raj_J2ME]

I have one application based on canvas. Application works fine on n96 and emulator but there is some issue in 6300. When user will go to command and then come back some how pain() invokes automatically. Is there any way to cancell all that automatic invokation of paint() ?

Hey,
That means you would be looking some flickering ...correct.

Make sure to stop the thread,
make the previous thread as null and hence the paint/repaint.This problem will be resolved.

[honest_success]

Hey,
That means you would be looking some flickering ...correct.

Make sure to stop the thread,
make the previous thread as null and hence the paint/repaint.This problem will be resolved.

Do you mean that at the end of paint()(Which will be invoked manually) i will have to do access the current thread by Thread.currentThread() but how can we stop it ?


-Kartik Trived

[grahamhughes]

You can't stop paint() being called by the platform. That's what paint() is for. If the platform didn't call it, the screen would be blank.

Why does it cause a problem?

[senthil_k]

Hi,
You are using highlevel command right. Instead of that use you own command implementation ie. in LSK and RSK you draw your command and control using key press. in that way you can control your paint call.
This means if you are using canvas alone you have some control on paint but switching between highlevel UI and canvas will definitely call paint when setting setcurrent.

[raj_J2ME]

Hi,
What I was saying is that from the current displayable say DISP1,while you are going back by clicking the command say DISP2,is there any thread running in the DISP1.
If yes then you can just make the thread as null,