RouteConverter and Mac OS X

[routeconverter]

Sorry for being "away" for quite some time.

I'm glad you're here again!

Could it have something to do with the window focus? Does this "Thread.sleep()" function maintain the focus within the main program/window, thereby stealing it from the popup? In this case the popup simply doesn't get the focus.

I understand the connection between the Thread.sleep() and the file dialog as the following:

• in Mac OS X the first thread of a process does the event processing
  
• for Java, it seems the Apple engineers managed to connect this directly to the AWT-EventQueue thread which is the single Java thread used to update the user interface for pure Java apps -XstartOnFirstThread is not necessary
  
• for the browser, I'm using a library (DJNativeSwingSWT) that allows to embed Eclipse SWT components into Javas Swing UI framework
  
• Eclipse SWT consists of native code and Java wrappers (where Java Swing is pure Java)
  
• this means the event processing becomes a problem since events from the operating system must reach the native code components i.e. the browser and the pure Java Swing (via the native Java VM)
  
• -XstartOnFirstThread and the Java class chrriis.dj.nativeswing.swtimpl.NativeInterface help to make sure that this hybrid SWT/Swing setup works
  
• if you now open the file dialog and after several layers of abstract at some point the Java VM calls the Mac OS to open a window that seems to collide with the Java thread I've throttled with Thread.sleep() which tries to call the native browser component
  
• I guess the reason for this collision is the single threaded approach of either Mac OS communicating with the apps its running or the Java VM executing AWT/Swing apps
  

Does this sound reasonable?

After writing the above, I've looked through the code (again) and searched for places where the access of the browser component could be parallized. Please have a look at EclipseSWTMapView#executeScript and #executeScriptWithResult and remove all the webBrowser.runInSequence( .. ) blocks, i.e.

webBrowser.runInSequence(new Runnable() {
public void run() {
webBrowser.executeJavascript(script);
}
});

becomes

webBrowser.executeJavascript(script);

Does this show any effect?

BTW: I stumbled upon this article (http://nadeausoftware.com/node/90).

I don't understand why you're citing this. What is special about that page?