VirtualBox

Changeset 60905 in vbox for trunk/include/VBox


Ignore:
Timestamp:
May 9, 2016 6:56:00 PM (9 years ago)
Author:
vboxsync
Message:

bugref:8087: Additions/x11: support non-root X server: do not reset the absolute input device to screen position co-ordinate mapping when we reset the screen mode after restoring a saved state. Among other potential problems this fixes problems with the cursor hot-spot position.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/include/VBox/vmm/pdmifs.h

    r59252 r60905  
    949949     * @param   pScreen             The data of screen being resized.
    950950     * @param   pvVRAM              Address of the guest VRAM.
     951     * @param   fResetInputMapping  Whether to reset the absolute pointing device to screen position co-ordinate
     952     *                              mapping.  Needed for real resizes, as the caller on the guest may not know how
     953     *                              to set the mapping.  Not wanted when we restore a saved state and are resetting
     954     *                              the mode.
    951955     * @thread  if render thread mode is on (fRenderThreadMode that was passed to pfnVBVAEnable is TRUE) - the render thread pfnVBVAEnable was called in,
    952956     *          otherwise - the emulation thread.
    953957     */
    954     DECLR3CALLBACKMEMBER(int, pfnVBVAResize,(PPDMIDISPLAYCONNECTOR pInterface, const PVBVAINFOVIEW pView, const PVBVAINFOSCREEN pScreen, void *pvVRAM));
     958    DECLR3CALLBACKMEMBER(int, pfnVBVAResize,(PPDMIDISPLAYCONNECTOR pInterface, const PVBVAINFOVIEW pView, const PVBVAINFOSCREEN pScreen, void *pvVRAM, bool fResetInputMapping));
    955959
    956960    /**
Note: See TracChangeset for help on using the changeset viewer.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette