search

jbuchermn / newm

Wayland compositor
MIT License
958 stars 31 forks source link

mouse extremely buggy on desktop + default config causing graphical glitches #177

Open FantasyPvP opened 1 year ago

FantasyPvP commented 1 year ago

i know that the window manager was designed for touchpads over actual mice but using a mouse with this wm is almost impossible for me, is there anything i can set in the configs that will make it work normally (like its impossible to use any of the gestures properly with the mouse)

EDIT: ok, i think i've managed to figure out how to use it to a basic level using the keyboard shortcuts, but i believe that the mouse is not working as intended. when holding down my windows key and moving the mouse, the window im hovering over flies uncontrollably around the screen and the cursor dissappears, is this a bug?

also i have another issue: the default config file makes the window manager bug out completely, the new frames dont seem to be replacing the previous ones, perhaps because i'm not using a wallpaper? (ill try installing a background and see if that fixes it because it looks like the new frames arent fully overwriting the old ones) i have a feeling this should be an easy fix if it is what i think it is

FantasyPvP commented 1 year ago

ok, after setting the wallpaper, the graphical issues have disappeared as i thought they would, it seems like the compositor just overlays the previous frame with the new one even if some areas of the screen havent generated a new frame yet. if you intend on fixing this, i guess you could just render a blank black background every frame.

CRAG666 commented 1 year ago

Most of the problems he mentions are not, you should read the full documentation or go to my user and read the configuration I use. On the other hand, I also use the mouse and indeed there are no mouse gestures, the way to use newm is with the touchpad or with keyboard shortcuts

FantasyPvP commented 1 year ago

im pretty sure the issue was because i was trying to use it in a VM and the desktop was using the raw input or something like that because it was fine when i tried it on my laptop and then natively on my desktop, the reason i think it's to do with raw inputs is because i had a similar kind of mouse buggyness when i tried to play a game (minecraft) across a vnc server and it worked fine after turning off raw mouse input

idk but what i do know is it seemed broken for me in a vm