02:27 <gryffus_> drm_info|grep Mode gives me "Mode: 1920x1080@60.00 phsync nvsync"

02:28 <gryffus_> But I doubt think the adapter supports only 1 resolution

02:28 <danieldg> gryffus_: grep for hsync instead to get a list, or search it

02:29 <danieldg> they aren't prefixed with Mode

02:29 <gryffus_> danieldg: yeah, only 1920x1080

02:29 <gryffus_> "1920x1080@60.00 preferred driver phsync nvsync" and "1920x1080@48.00 driver phsync nvsync"

02:29 <danieldg> look in the Connector section

02:30 <gryffus_> https://susepaste.org/62c936730b59

02:30 <danieldg> This service is now obsolete

02:30 <gryffus_> https://paste.opensuse.org/62c936730b59

02:30 <gryffus_> sorry wrong link :x

02:31 <danieldg> ah, eDP might actually only support one resolution

02:32 <gryffus_> I am using even 640 x 480 on both X11 and Windows

03:30 <bwidawsk> gryffus_: so there's no reason why you can't render the surfaces at lower resolutions, but either the compositor, or the display is going to scale it to 19x10

03:30 <bwidawsk> I know nothing about how KDE handles this stuff, but fractional scaling should allow this

06:31 <cmeissl[m]> Is it required to send frame events for wl_touch.up? Seems that some compositor send it and some not.

06:31 <cmeissl[m]> I would expect wl_touch.cancel and wl_touch.up to take immediate effect and not require a separate frame event.

07:14 <kennylevinsen> cmeissl[m]: It does not seem specified well enough, and I do not see an immediate reason why down *wouldn't* use the frame event

07:14 <kennylevinsen> ah, up

07:16 <kennylevinsen> Not sure tbh - up and cancel say "no further events will be sent for this touch point", but whether that implies that no frame event is sent is unclear

07:17 <kennylevinsen> up for a clarifying patch? :)

07:26 <cmeissl[m]> kennylevinsen: thx. yeah, I will open an issue. seems that this has been changed in weston: https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/980

07:28 <daniels> 'no further events will be sent for this touch point' was written before 'frame' was introduced

07:29 <daniels> cancel explicitly states 'No frame event is required after the cancel event', but up doesn't

07:29 <daniels> so I'd say that cancel+frame is unexpected but harmless, whereas up+frame is mandatory

07:32 <cmeissl[m]> interesting , thx daniels this seems to match the implementation in wlroot which internally tracks needs_touch_frame and sets it for up, but not for cancel. afaict weston would send frame in both cases.

07:33 <cmeissl[m]> will re-test, but iirc gnome did not send frame after up

07:35 <kennylevinsen> Ah yes, ifreund updated the cancel event a month ago to specify that no frame event is needed