I use NW.JS a lot, and both on Windows and MacOS click trough transparent option works. What does that mean. It means if i have fullscreen window that has transparent region, that transparent region ignores mouse events. Example of usage would, lets say i want to make desktop companion app like Clippy and it’s full screen window, only Clippy can be clicked, in that case KWin would need to ignore transparent region of window. Of course you could move window via scripts, and it’s harder to manage resizing if let’s say Clippy has something to say. So i made workaround using node_module that uses libinput to calculate cursor position and move virtual cursor, so when virtual cursor is over transparent to make window ignore event (using x11, cause nw.js can run in x11). But issue is when you make x11 window click trough once, and you don’t know cursor position, you cant know should you turn event’s back on, cause you don’t know where the cursor is in Wayland. Well with libinput node_module i kind of made it, but cursor drifts away overtime from KWin’s cursor. So then i tried rebuilding Mutter to see how can get cursor position, but I’m not much of a programmer. I did rebuild it, but didn’t expose cursor. I’m looking to build one with wl-roots, but it doesnt have good VM support. I also looked into using EIS capture events, like input-leap does, but didn’t know how to utilize it. I wanted to use libinput to move cursor with virtual mouse, and block real inputs. All i need is click trough transparent, that’s why i hustle with getting cursor position. I made this bar also for Windows, can work on Linux too. But it’s full screen and I need transparent region to ignore mouse events in order for it to work. I’m building own shell to use. if KWin cant do it, i would need to make own compositor. So any advice?
