Package org.gnome.gio

Interface FileMonitor.ChangedCallback

All Superinterfaces:

FunctionPointer

Enclosing class:

FileMonitor

Functional Interface:

This is a functional interface and can therefore be used as the assignment target for a lambda expression or method reference.

@FunctionalInterface
public static interface FileMonitor.ChangedCallback
extends FunctionPointer

Functional interface declaration of the ChangedCallback callback.

See Also:

• run(org.gnome.gio.File, org.gnome.gio.File, org.gnome.gio.FileMonitorEvent)

Method Summary

Modifier and Type	Method	Description
void	run(@Nullable File file, @Nullable File otherFile, FileMonitorEvent eventType)	Emitted when file has been changed.
default MemorySegment	toCallback(Arena arena)	Creates a native function pointer to the upcall(java.lang.foreign.MemorySegment, java.lang.foreign.MemorySegment, java.lang.foreign.MemorySegment, int) method.
default void	upcall(MemorySegment sourceFileMonitor, MemorySegment file, MemorySegment otherFile, int eventType)	The upcall method is called from native code.

Method Details

run

void run(@Nullable File file,
 @Nullable File otherFile,
 FileMonitorEvent eventType)

Emitted when file has been changed.

If using FileMonitorFlags.WATCH_MOVES on a directory monitor, and the information is available (and if supported by the backend), eventType may be FileMonitorEvent.RENAMED, FileMonitorEvent.MOVED_IN or FileMonitorEvent.MOVED_OUT.

In all cases file will be a child of the monitored directory. For renames, file will be the old name and otherFile is the new name. For "moved in" events, file is the name of the file that appeared and otherFile is the old name that it was moved from (in another directory). For "moved out" events, file is the name of the file that used to be in this directory and otherFile is the name of the file at its new location.

It makes sense to treat FileMonitorEvent.MOVED_IN as equivalent to FileMonitorEvent.CREATED and FileMonitorEvent.MOVED_OUT as equivalent to FileMonitorEvent.DELETED, with extra information. FileMonitorEvent.RENAMED is equivalent to a delete/create pair. This is exactly how the events will be reported in the case that the FileMonitorFlags.WATCH_MOVES flag is not in use.

If using the deprecated flag FileMonitorFlags.SEND_MOVED flag and eventType is FileMonitorEvent.MOVED, file will be set to a GFile containing the old path, and otherFile will be set to a GFile containing the new path.

In all the other cases, otherFile will be set to NULL.

upcall

default void upcall(MemorySegment sourceFileMonitor,
 MemorySegment file,
 MemorySegment otherFile,
 int eventType)

The upcall method is called from native code. The parameters are marshaled and run(org.gnome.gio.File, org.gnome.gio.File, org.gnome.gio.FileMonitorEvent) is executed.

toCallback

default MemorySegment toCallback(Arena arena)

Creates a native function pointer to the upcall(java.lang.foreign.MemorySegment, java.lang.foreign.MemorySegment, java.lang.foreign.MemorySegment, int) method.

Specified by:

toCallback in interface FunctionPointer

Parameters:

arena - the arena in which the function pointer is allocated

Returns:

the native function pointer