Thread: is the importData(...) method of a transferHandler run on the EDT?

Hi,
just a quick question. When I implement a custom TransferHandler for a JTree / JList, can I expect that the importData method is called on the EDT and that I can simply Insert / Remove to / from the underlying model without having to push events on the EDT?
Or should I still wrap every action which changes the model up in a EDT.invokeLater(Runnable r) call?

I am asking because I am getting some visual glitches with and I want to know whether this is because of an error in my own code or because I am not using the EDT there explicitely.

Thanks in advance.

Or should I still wrap every action which changes the model up in a EDT.invokeLater(Runnable r) call?

No, that's not necessary. If an event running from a Swing app requires so much CPU time that the interface is impacted, then SwingWorker should be employed.

What kind of visual glitches are you experiencing?

With my JTree I get some blank lines and not correctly drawn selection boxes. I observed the same behavior when modifying the model from a different thread then the EDT in the past.
Furthermore, these glitches seem to come at random. I was monitoring every TreeModelEvent with a separate listener and writing them to an output.
When I noticed this glitch I restarted the application and repeated all steps from the previous run in the exact order. The same glitch did not appear at the same time, but sometimes earlier and sometimes later.
This is another reason why I was thinking that this might be because of events being fired out of sync.