launch_uris_as_manager
Description:
This function performs the equivalent of launch_uris, but is intended primarily for operating system components that launch applications.
Ordinary applications should use launch_uris.
If the application is launched via GSpawn, then spawn_flags, user_setup and user_setup_data are used for
the call to spawn_async. Additionally, pid_callback (with
pid_callback_data) will be called to inform about the PID of the created process. See
spawn_async_with_pipes for information on certain parameter
conditions that can enable an optimized posix_spawn codepath to be used.
If application launching occurs via some other mechanism (eg: D-Bus activation) then spawn_flags, user_setup,
user_setup_data, pid_callback and pid_callback_data are ignored.
Parameters:
| this | |
| uris |
List of URIs |
| launch_context | |
| spawn_flags |
SpawnFlags, used for each process |
| user_setup |
a SpawnChildSetupFunc, used once for each process. |
| pid_callback |
Callback for child processes |
| pid_callback_data |
User data for |
| user_setup_data |
User data for |
Returns:
|
true on successful launch, false otherwise. |