https://bugs.kde.org/show_bug.cgi?id=444510
--- Comment #14 from Paul Meier <public.paul.meier+...@gmail.com> --- (In reply to Vlad Zahorodnii from comment #13) > Do you know how looking glass handles the cursor? Does it hide the > compositor's cursor and render the cursor inside the window like many video > games do? I've found this in the docs: "we need to always operate in relative mouse input mode, and since factors like windows mouse acceleration, or cursor movement by a user application may occur in the guest, we need to pass this information back so the client can render the cursor in the correct location. " The cursor is captured and hidden by default as you've described, but I am not aware how exactly it works. There is an option to unhide the cursor, as well as to not capture the cursor, which does not change anything about the issue. If I unhide and capture the cursor, there will be the windows cursor and the host cursor, which will be shown as a small dot. The default fullscreen by looking glass is not exclusive, it is a borderless fullscreen. I habe not tried, if the issue shows up in windowed mode. Nonetheless, the issue appears in games as well, not just in this application, as I've written before. -- You are receiving this mail because: You are watching all bug changes.
