Bug 894036

Description of problem:
Currently used monitor-config message uses continuous range of monitors, which forces the user to use a continuous display configuration.

Copying from BZ#881072

...Reopening of closed display has been fixed, one different issue has surfaced:
  -- for some reason the client always tries to establish connection on first n available displays, where n is number of windows open. Which results in: 
     -- user being unable to open displays out of order (e.g. instead of having displays 1, 3 and 4; he gets 1, 2, 3)
        -- this might be considered as OK, but remote viewer actually states it's waiting for the selected display and ends up with the wrong one. 
        -- the bigger issue related to this behaviour is: 
           -- user has no control of which display actually gets closed, when he closes a window.
              -- when user closes a window, then after a short period of time, the configuration alters in this way: It closes the highest open display, and maintains the first n displays open. Example for a use case, where this is wrong: 
user opened displays 1, 2, 3. Works mostly on displays 1,3, decides to close 2. After a short timeout, display 3 gets closed, 2 reopened, and work from 3 gets rearranged between 1 and 2. The expected way is obviously keeping 1, 3 open, closing 2.
...

Version-Release number of selected component (if applicable):
spice-vdagent-0.12.0-4.el6
spice-gtk-0.14-7.el6

How reproducible:
Always 




Additional info: