be located outside of the current
monitor which is not handled by the current code. Also the monitor
itself might be located at coordinates different from (0, 0).
Signed-off-by: Dennis Wölfing
---
Changes in v2:
Warp the mouse to the center of the monitor.
ui/gtk.c | 26
On 19.07.21 13:31, Marc-André Lureau wrote:
Hi Dennis
On Tue, Jun 29, 2021 at 5:26 PM Dennis Wölfing wrote:
> To handle relative mouse input the event handler needs to move the mouse
> away from the screen edges. Failing to do so results in the mouse
> getting stuck at invisi
Ping 2
I'd like to get this bugfix into 6.1.
On 07.07.21 13:02, Dennis Wölfing wrote:
Ping
https://lore.kernel.org/qemu-devel/20210629132410.286813-1-denniswoelf...@gmx.de
On 29.06.21 15:24, Dennis Wölfing wrote:
To handle relative mouse input the event handler needs to move the mouse
away
Ping
https://lore.kernel.org/qemu-devel/20210629132410.286813-1-denniswoelf...@gmx.de
On 29.06.21 15:24, Dennis Wölfing wrote:
To handle relative mouse input the event handler needs to move the mouse
away from the screen edges. Failing to do so results in the mouse
getting stuck at invisible
be located outside of the current
monitor which is not handled by the current code. Also the monitor
itself might be located at coordinates different from (0, 0).
Signed-off-by: Dennis Wölfing
---
ui/gtk.c | 21 +
1 file changed, 9 insertions(+), 12 deletions(-)
diff --git
Ping
https://lore.kernel.org/qemu-devel/20210607115303.228659-1-denniswoelf...@gmx.de/
On 07.06.21 13:53, Dennis Wölfing wrote:
The highest VBE_DISPI_INDEX_ID version supported by QEMU is
VBE_DISPI_ID5. But currently QEMU only allows writing values up to
VBE_DISPI_ID4 to the VBE_DISPI_INDEX_ID
the register will
continue to report the lower version.
Indeed SeaBIOS is doing that during VGA initialization which causes
guests to always read VBE_DISPI_ID0 instead of the correct version.
Signed-off-by: Dennis Wölfing
---
hw/display/vga.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion
