[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Native dialogs and deadlocks

Subject: Re: Native dialogs and deadlocks
From: Brendon McLean <email@hidden>
Date: Thu, 19 Apr 2007 00:47:39 +0200
Delivered-to: email@hidden
Delivered-to: email@hidden

The Foxtrot code is very interesting, but looking at its source shows that it depends on an event dispatch algorithm that was obtained from the 1.3 JRE. Looking at the 1.5 JRE shows some changes to that algorithm, in that it adds a new dispatching option. This may or may not effect running in 1.5+ JREs, and testing would need to be very vigourous to ensure that all possible cases work correctly.

Foxtrot subclasses ConditionalEventPump with SunJDK14ConditionalEventPump for 1.4+ JVMs. I have used Foxtrot to create semi-modal (or window-modal) dialogs. If you need something tested, use the Foxtrot code. _______________________________________________ Do not post admin requests to the list. They will be ignored. Java-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/java-dev/email@hidden

This email sent to email@hidden

References:
	>Re: Native dialogs and deadlocks (From: Doug Zwick <email@hidden>)

Prev by Date: Re: Native dialogs and deadlocks
Next by Date: Re: Help!: Kernel Panics under heavy socket connections, Java 1.5 causing them?
Previous by thread: Re: Native dialogs and deadlocks
Next by thread: Java App will launch on Powerbook but not IntelMini
Index(es):
- Date
- Thread

Home