Add ability to define custom display->monitor mapping per vm

Fullscreen mode generally just assigns display 1 to monitor 1, display 2 to
monitor 2, etc. For custom setups, you can define a monitor mapping in the
settings keyfile per-vm. This requires a vm uuid (so only works in virt-viewer
or on versions of spice-server that send the uuid over the wire).  The format is
pretty basic:

    [6485b20f-e9da-614c-72b0-60a7857e7886]
    monitor-mapping=2;3

The group name ("6485b20f-e9da-614c-72b0-60a7857e7886") is the uuid id of the
vm. This group has a single key: monitor-mapping. This key is an array of
integers describing the order in which to assign the monitors to a guest
display. Any monitors that are not listed in this array will not be configured
at startup.  For instance:

    monitor-mapping=2;1

will attempt to configure 2 displays on the guest and assign the first display
to monitor 2 and the second display to monitor 1.

    monitor-mapping=2

will only configure a single display on the guest and place it on the second
monitor.  Any monitor numbers listed in the keyfile are greater than the number
of monitors that are physically present, they will be ignored.

1 files changed, 3 insertions, 0 deletions

diff --git a/src/virt-viewer-app.h b/src/virt-viewer-app.h
index f72f5b3..737b0af 100644
--- a/src/virt-viewer-app.h
+++ b/src/virt-viewer-app.h
@@ -100,6 +100,9 @@ gboolean virt_viewer_app_get_fullscreen(VirtViewerApp *app);
 gboolean virt_viewer_app_get_fullscreen_auto_conf(VirtViewerApp *app);
 const GOptionEntry* virt_viewer_app_get_options(void);
 void virt_viewer_app_clear_hotkeys(VirtViewerApp *app);
+gint virt_viewer_app_get_n_initial_displays(VirtViewerApp* self);
+gint virt_viewer_app_get_initial_monitor_for_display(VirtViewerApp* self, gint display);
+void virt_viewer_app_set_uuid_string(VirtViewerApp* self, const gchar* uuid_string);
 
 G_END_DECLS