05:33 <|> I think I'm having an idea but in a really early-ideas way

05:33 <|> Microsoft Teams is the bane of my existence in my other duties.

05:34 <|> I hate having someones' peasant-class monitor streamed to my screen to be upscaled

05:34 <|> I wish it were possible to say "Stream this as if it were a virtual monitor at this resolution"

05:34 <|> And then this had me thinking about games. Supersampling textures.

05:35 <|> Where you're saying "downscale textures twice the resolution of what is appropriate for my screen"

05:35 <|> for some reason this winds up creating crisper textures?

05:35 <|> if I'm understanding that right.

05:35 <|> And then I remembered how in MacOS you're never setting your screen to the native resolution. It's always half or a fractional multiplier

05:36 <|> So your monitor is really 2160p and you target 1080p and it's a clean 2x upscale to everything blah blah

05:37 <|> So wayland. It would be neat to say "I have this 1600x900 monitor, but I want to give a virtual resolution of 1920x1080 and downscale" and then i can stream this screen in shit like microsoft teams. :c

05:38 <|> And then other recipients would simply see a 1080p image. Even if I am not.

05:38 <|> I think that's why it's an early/dumb idea. There's gotta be a better idea than that. While I definitely want virtual resolutions married to physical screens, this particular use case is silly

05:39 <|> also that's the old kind of scaling. I understand simply upscaling an image isn't "hidpi" rendering

05:43 <|> conceptually, I wish framebuffers were divorced from outputs (if I'm phrasing that right). like default expected behavior in most compositors is that if a new display appears you'd set it up and extend the desktop to it. but I keep wondering if the proper default would be rendering a console for it, then allowing another user to login -and providing another way for the compositor to notify the exisitng user

05:43 <|> that another screen appeared and can be

05:43 <|> "taken over"

05:43 <|> something something multiseat

05:49 <|> I understand I have all my legit ideas in the wrong place (wayland is not a compositor), but the clipboard paste manager thing totally became part of windows 10 lolz

17:38 <frobnitz> I'm using X, not Wayland, but I have a libinput question. I have an old Lenovo ScrollPoint mouse (has a TrackPoint style scroll thingy) that recently started scrolling way too fast. For example, libinput debug-events says "event5 POINTER_SCROLL_CONTINUOUS +5.872s vert 15120.00/0.0* horiz 0.00/0.0 (continuous)". What can I do to fix this?

19:16 <wlb> wayland Merge request !191 opened by () wayland-shm: Keep shm pool data mappings valid. https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/191

19:17 <wlb> wayland/shm-resize-fixes: Build #450952 failed after 10 seconds https://gitlab.freedesktop.org/wayland/wayland/pipelines/450952

19:17 <wlb> wayland/shm-resize-fixes: Build #450952 failed after 10 seconds https://gitlab.freedesktop.org/wayland/wayland/pipelines/450952

19:22 <wlb> wayland/shm-resize-fixes: Build #450958 failed after 28 seconds https://gitlab.freedesktop.org/wayland/wayland/pipelines/450958

19:32 <wlb> wayland/shm-resize-fixes: Build #450961 failed after 3 minutes 35 seconds https://gitlab.freedesktop.org/wayland/wayland/pipelines/450961

19:37 <wlb> wayland/shm-resize-fixes: Build #450966 failed after 3 minutes 8 seconds https://gitlab.freedesktop.org/wayland/wayland/pipelines/450966

19:39 <zubzub> ohmy all pipeline statusses get printed here

19:40 <zubzub> did_I_do_that.gif

19:45 <wlb> wayland/shm-resize-fixes: Build #450968 failed after 3 minutes 2 seconds https://gitlab.freedesktop.org/wayland/wayland/pipelines/450968

19:46 <wlb> wayland/shm-resize-fixes: Build #450970 failed after 2 minutes 45 seconds https://gitlab.freedesktop.org/wayland/wayland/pipelines/450970