LWUIT Issue

[giaviv]

Hey guys,

I have a MIDlet running on a Nokia 6212 NFC device. I'm using LWUIT for my GUI.

Lets say I have Form a and Form b.
In some situations when I call b.show() when a is already displayed, there is no visual change in the MIDlet - form a remains on the screen BUT the commands of form b are active - lets say that the right soft key command in form a displays an alert that contains the text "FORM A" when it is pressed in form a, and the left soft key command in form b displays an alert that contains the text "FORM B" when it is pressed in form b - when form a in showed and I call b.show(), there is no change on the screen - form a remains shown. But, if I press the left soft key - the "FORM B" alert is displayed. I have a few threads (not GUI related) running on the system and I have a feeling that this is a sync problem. Anybody has an idea?

Thanks!

[ektasrv]

Instead of just calling b.show(), first set the form b as current form then call its show().

thanks,
Ekta

[roopesh.kumar]

HI,

I had faced similar problem. I do not know why this happens.
But to avoid this I decided to attach the Command Listener only after the form is visible.
This avoids commands of Form-B getting activated in Form-A.

b.show();
while(!b.isVisible());
b.addCommandListener(cmdLtr);

You might like go through these links to know more about threads in LWUIT.
Link1 and Link2.

[giaviv]

Instead of just calling b.show(), first set the form b as current form then call its show().

thanks,
Ekta

Hey,

How do I set form b to be the current form? LWUIT's Display doesn't have a setCurrent like the MIDLet's Display class..

[giaviv]

Hey guys,

I still haven't been able to figure this out. There is some kind of a sync problem and I can't seem to prevent it nor to predict when it will happen.
Do you have any example of safe practice with regards to threading in LWUIT? I really don't know what to do as this issue is very weird..

Thanks!