mi::DisplayInputRegion::confine(geom::Point& point) is responsible for confining the cursor position inside the display rectangles.
void ms::MediatingDisplayChanger::update_input_rectangles(mg::DisplayConfiguration const& config)
is that which configures DisplayInputRegion with the display rectangles.
phablet@frieza:~/lib$ mirout -- --desktop_file_hint=dialer-app
Connected to server: <default>
Card 0: Max 3 simultaneous outputs
Output 1: Card 0, LVDS, connected, 1200x1920+0+0, used, on, 135mm x 216mm (10.0"), normal
1200x1920 56.90*+
Output 2: Card 0, DisplayPort, disconnected
Output 3: Card 0, Virtual, disconnected
1920x1080 60.00*+
I am seeing the MediatingDisplayChanger consider the Virtual display as being included in the display rectangles, even though is is "disconnected".
mi::DisplayInpu tRegion: :confine( geom::Point& point) is responsible for confining the cursor position inside the display rectangles.
void ms::MediatingDi splayChanger: :update_ input_rectangle s(mg::DisplayCo nfiguration const& config)
is that which configures DisplayInputRegion with the display rectangles.
phablet@ frieza: ~/lib$ mirout -- --desktop_ file_hint= dialer- app
Connected to server: <default>
Card 0: Max 3 simultaneous outputs
Output 1: Card 0, LVDS, connected, 1200x1920+0+0, used, on, 135mm x 216mm (10.0"), normal
1200x1920 56.90*+
Output 2: Card 0, DisplayPort, disconnected
Output 3: Card 0, Virtual, disconnected
1920x1080 60.00*+
I am seeing the MediatingDispla yChanger consider the Virtual display as being included in the display rectangles, even though is is "disconnected".