[dsdp-ercp-dev] Running eSWT browser starves all other threads?

["Gerald McCobb" <mccobb@xxxxxxxxxxxxxx>]

Hello,

 

We used the example for starting the eSWT browser in a Midlet:

 

http://wiki.forum.nokia.com/index.php/CS000974_-_Using_eSWT_Browser_in_Java_ME

 

Because the browser URL may be set from an external event, for example, we have an event processing queue for processing browser commands.  This queue runs in its own thread.  From the event queue a Browser Midlet handleEvent method is called, which processes the event more or less as follows:

 

  display.asyncExec(new Runnable() {
   public void run() {

 

    short type = getEventType(evt) ;
    
    switch (type) {

    case START:

       String url = "">       browser.setUrl(url);

    break;

     }

   }});

 

After the event queue runs and the browser.setUrl is called the web page appears and works as expected.  However, all other threads started for the event queue and logging are either cancelled or starved.  No more thread processing takes place.  What are we doing wrong, or is this the expected behavior?

 

The above code works fine on Windows Mobile.  Thanks.

 

 

Regards,

 

Jerry McCobb
Openstream

BEGIN:VCARD
VERSION:2.1
N:McCobb;Jerry
FN:Jerry McCobb
ORG:Openstream
TEL;WORK;VOICE:(732) 507-7030 ext 109
TEL;WORK;FAX:(732) 507-7035
EMAIL;PREF;INTERNET:mccobb@xxxxxxxxxxxxxx
REV:20080922T194624Z
END:VCARD