Package com.intellij.compiler.impl

Class TranslatingCompilerFilesMonitor

java.lang.Object

com.intellij.compiler.impl.TranslatingCompilerFilesMonitor

All Implemented Interfaces:

AsyncFileListener

public class TranslatingCompilerFilesMonitor
extends java.lang.Object
implements AsyncFileListener

Nested Class Summary

Nested classes/interfaces inherited from interface com.intellij.openapi.vfs.AsyncFileListener

AsyncFileListener.ChangeApplier

Constructor Summary

Constructors

Constructor and Description
TranslatingCompilerFilesMonitor()

Method Summary

Modifier and Type	Method and Description
static TranslatingCompilerFilesMonitor	getInstance()
AsyncFileListener.ChangeApplier	prepareChange(java.util.List<? extends VFileEvent> events) Called (possibly on a background thread) when a batch of VFS events is ready to be fired.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

TranslatingCompilerFilesMonitor

public TranslatingCompilerFilesMonitor()

Method Detail

getInstance

public static TranslatingCompilerFilesMonitor getInstance()

prepareChange

public AsyncFileListener.ChangeApplier prepareChange(java.util.List<? extends VFileEvent> events)

Description copied from interface: AsyncFileListener

Called (possibly on a background thread) when a batch of VFS events is ready to be fired. This method should not have side effects and should guarantee its cancellability by calling ProgressManager.checkCanceled() often enough.

Note that this listener can only observe the state of the system before VFS events, and so it can't work with anything that would be after them, e.g. there will be no file in VFileCreateEvent, FileIndexFacade won't know anything about the updated state after VFS change, and so on.

Note that the events posted passed might differ from the ones passed into BulkFileListener. In particular, there may occasionally be several events about the same file (e.g deletion and then creation, or creation and then deletion of the file's parent). Hence the order of events is significant. Implementations should be prepared to such situations.

Specified by:

prepareChange in interface AsyncFileListener

Returns:

a ChangeApplier object to be called inside write action before/after the passed events are finally applied to VFS