Broken Pointer conversion for flatland objects
when running a wayland app in flatland the pointer conversion(hand or controller and probably also something like azimuth) is incorrect, mainly if the pointer moves to far to the right or to far down, i think it gets clamped to some size (maybe the original window size), this might also be related to some apps like firefox and thunderbird just not receiving input at all.
also sorry for reporting so many issues, i do think stardust is great
11 Replies
no i want all these issues to be reported, they don't go away if someone doesn't report them!
and it's good that someone's clearly trying to use this :D
firefox and thunderbird use subsurfaces as their whole window, and i don't have those properly wired up for input right now
idk why they do, it makes no sense given nothing else uses subsurfaces that way, they're designed to delay composition so you can parallelize it and not take more time compositing before you send it to the compositor again except that since it's the only visible thing for firefox and thunderbird it's not compositing with anything
and yeah the way flatland works the type of input doesn't matter, it uses a hover and touch plane so the fault is probably on the server side wayland stuff
maybe window geometry not being accurate internally?
can you show me a video of when this happens (not firefox or thunderbird) so i can see the clamping bug?
ahh i think i know where that is
shoot i don't clamp it anywhere....
what app are you running in stardust there?
what discord client so i can recreate the bug
stock, but it happens with a ton of apps
does it happen only when the window gets super big?
or is square?
or... anything else to help me isolate the bug?
might be only chromium/electron based apps? alacritty seems fine
ahh ok so some apps but not all
v helpful
vlc is also broken (but maybe in a diff way), including the popup somehow
minecraft is broken too
maybe the server doesn't update the size correctly since resizing is pretty new in flatland?
no, the size is pumped straight into wayland
this feels like a problem with the xdg geometry vs render surface size
since wayland cannot keep its stuff consistent
it might be the whole issue with shadows again
where the thing INSISTS on drawing shadows when i don''t want them
gndsilkjujngkajlsdgndsa;lk
who knows
IT'S XWAYLAND! or xwayland-satellite, when i force an app to use native wayland it works!
oh yay it's NOT MY CODE
not my problem yeets self
jk i'll at least let the xwayland-satellite maintainer know