If we overlooked
your question or we weren't clear with an answer, please let us know. We
are eager to help. Send your sales and order questions to
and your technical questions to
Do I need to change my code to use Detangler?
No. You don't have to change a single line of code to use Detangler. All you need is debugging on when you compile.
How does Detangler work?
Detangler watches all of the Swing calls that are made while you use your application. When you return to Detangler's wizard and click the Next button, Detangler uploads your report to DeNova's website, quickly analyzes the report, and then shows the results in Detangler's window.
What do I do after I get the report about my app?
If Detangler found Swing called in the wrong thread, then scroll down to the section of the report labeled Stack Trace. Look up the first line of code in your source and change it so Swing is called from the event queue (EDT).
Once you have modified your code to resolve the noted errors, then run Detangler again. Keep repeating this process until all of the Swing calls are invoked from the EDT.
When you write new code, then be sure to run Detangler again to verify that Swing is still being called properly.
Which Swing components are thread safe?
None.
It turns out the old rules were wrong. After years of confusion about which parts of Swing are thread safe, here's the definitive word from Sun:
Can Detangler find threading errors in a non-swing app?
No, Detangler only works with applications written in Java that use the Swing GUI.
Does Detangler work with non-java apps?
No, Detangler only works with applications written in Java that use the Swing GUI.
What is the current version of Detangler?
Detangler is updated on a regular basis. The current version number appears in the release notes.
What are the system requirements?
Copyright © 1997-2008 DeNova. All rights reserved worldwide.
Privacy policy
Legal notices