gio.app_info_monitor.AppInfoMonitor is a very simple object used for monitoring the app
info database for changes (newly installed or removed applications).
In the usual case, applications should try to make note of the change
(doing things like invalidating caches) but not act on it. In
particular, applications should avoid making calls to gio.app_info.AppInfo APIs
in response to the change signal, deferring these until the time that
the updated data is actually required. The exception to this case is when
application information is actually being displayed on the screen
(for example, during a search or when the list of all applications is shown).
The reason for this is that changes to the list of installed applications
often come in groups (like during system updates) and rescanning the list
on every change is pointless and expensive.
gio.app_info_monitor.AppInfoMonitor monitors application information for changes.
gio.app_info_monitor.AppInfoMonitor is a very simple object used for monitoring the app info database for changes (newly installed or removed applications).
Call gio.app_info_monitor.AppInfoMonitor.get to get a gio.app_info_monitor.AppInfoMonitor and connect to the gio.app_info_monitor.AppInfoMonitor.changed signal. The signal will be emitted once when the app info database changes, and will not be emitted again until after the next call to gio.app_info.AppInfo.getAll or another g_app_info_*() function. This is because monitoring the app info database for changes is expensive.
The following functions will re-arm the gio.app_info_monitor.AppInfoMonitor.changed signal so it can be emitted again:
The latter functions are available if using [gio.desktop_app_info.DesktopAppInfo] from gio-unix-2.0.pc (GIR namespace GioUnix-2.0).
In the usual case, applications should try to make note of the change (doing things like invalidating caches) but not act on it. In particular, applications should avoid making calls to gio.app_info.AppInfo APIs in response to the change signal, deferring these until the time that the updated data is actually required. The exception to this case is when application information is actually being displayed on the screen (for example, during a search or when the list of all applications is shown). The reason for this is that changes to the list of installed applications often come in groups (like during system updates) and rescanning the list on every change is pointless and expensive.