ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
yrlf has quit [Quit: Ping timeout (120 seconds)]
yrlf has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
Brainium has quit [Quit: Konversation terminated!]
Moprius has quit [Quit: bye]
agd5f has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
garnacho has quit [Ping timeout: 480 seconds]
glennk has joined #wayland
slattann has joined #wayland
gnarchie has quit [Remote host closed the connection]
<orowith2os[m]>
question: how bad of an idea would it be to set a super specific acceleration curve for libinput
<orowith2os[m]>
like, I'm talking a step of 0.1, and probably close to 50 or 100 points
<orowith2os[m]>
if not even more specific
<vyivel>
should be fine
<vyivel>
(i think)
<orowith2os[m]>
vyivel: time to screw around and find out!
<orowith2os[m]>
(I would use more, uh, descriptive language, but trying to be family friendly. I used enough of my sailor mouth at work today)
<vyivel>
are you trying to make an actually curvy curve
<orowith2os[m]>
perhaps
<orowith2os[m]>
oh god. imagine a sine wave for the curve.
<vyivel>
peak ux
<orowith2os[m]>
I need an app to generate and visualize acceleration curves for this....
<orowith2os[m]>
good first time for Python I guess.
akimoto has joined #wayland
<orowith2os[m]>
I'll play around with GTK and see if I can make something that plots it out
<orowith2os[m]>
erhm, later.
<orowith2os[m]>
something something gnuplot
akimoto has quit [Remote host closed the connection]
<orowith2os[m]>
I think my biggest concern right now is making sure I set the libinput config on x11 correctly...
<orowith2os[m]>
also curious to know if npoints_min could be changed to 1, and it just level it out (a flat acceleration profile) if it ever hits that condition
<vyivel>
the code in filter-custom.c assumes there are at least 2 points, the special case isn't worth it
<orowith2os[m]>
with a low step and high amount of points, you could hit the limits
sally has joined #wayland
<whot>
orowith2os[m]: beyond "nicer visualisation" I doubt you'd notice a difference with >64 points
<orowith2os[m]>
yeah
<whot>
this very much sounds like the ikea effect :)
<orowith2os[m]>
feel free to close as not planned, we can always wait and see if someone ever hits those limits and would give a real world case to justify raising the limit
<orowith2os[m]>
I also hope my Mutter patches caught your eye? ;)
<orowith2os[m]>
you might want to scrutinize the X11 implementation over there
<whot>
orowith2os[m]: they did, I had the tab open all day! and probably will for another few days :)
<orowith2os[m]>
hehe
<orowith2os[m]>
I think there's a good chance we could eek it into 48, considering there isn't any UI changes involved
<orowith2os[m]>
or backport it to other versions
<whot>
what's the deadline for that?
<orowith2os[m]>
I think, uh, Soon
<whot>
like days or a week?
<orowith2os[m]>
beginning of March, looks like
<whot>
curse the short february
<orowith2os[m]>
March 19th
<whot>
thats the release date or the deadline?
<orowith2os[m]>
release date for the final stable release
<whot>
ah, so a tad sooner then
<orowith2os[m]>
yeahhhh
<orowith2os[m]>
it's not a worry for me. distributions or users will patch it in if they want to
<orowith2os[m]>
so long as gnome doesn't NACK the idea of backporting the patches to 47 or earlier
<orowith2os[m]>
I also hope seeing the process of me figuring out how to write glib-flavored C and slowly get to a more fully working implementation was fun
<orowith2os[m]>
whew boy, 60 more files to build in webkitgtk (well, 120, since it's doing two different ABIs) until I can test the X11 stuff...
<mdb977>
Hi, I'm on BeagleBoneBlack with Weston 13.0.3. I have a problem with my physical USB keyboard. If I connect the keyboard before starting weston-editor, everything will work fine. If I connect the keyboard after starting weston-editor, it does not work until I restart the editor. What's the best way to debug this? The log does not show anything obvious to me.
<bl4ckb0ne>
iirc that user made 2 LLM issues on wlroots and a bunch of spam comments on other MRs
gnarchie has joined #wayland
<karolherbst>
I think the person in question uses LLM for translation purposes, but might overdo it a little... might be best for you to have a chat with them to check what's up there
<bl4ckb0ne>
yup, it doesnt look like a regular spambot
<karolherbst>
but in the end if you want to forbid LLMs for technical contributions that might be reasonable if it's only wasting maintainers time, but it's a tough call to make if the person in question doesn't understand english
<karolherbst>
or not well enough
<daniels>
I'm handling it
<kchibisov>
The point is that they are used in a way to confuse people in the current state of things.
<bl4ckb0ne>
thanks
<daniels>
I saw that on the weekend but forgot it
<karolherbst>
thanks
<daniels>
I think that person is genuinely enthusiastic, but as karolherbst is getting at, is quite possibly using LLMs to better express themselves in a non-native language
<bl4ckb0ne>
i have the same feel
<kennylevinsen>
this isn't my experience of how LLM's handle translation requests, so it seems more like they told it to try to make a review or create constructive commentary for them
<daniels>
oh yeah, for sure they've also asked the LLM to make a compelling point for them
<karolherbst>
well maybe "translation" is the wrong term here, they might just try to overcome language barriers
<karolherbst>
anyway, I did check out that account a while ago and at least from a quick look it seems plausible that they might not be able to communicate properly in English.
<kennylevinsen>
but then again, who can? :)
<karolherbst>
not the point I was trying to make
<kennylevinsen>
nah, but as someone using technical assistance to navigate other (non-english) languages, I don't think it's an excuse. You will know that you have just generated an essay on a subject where your only actual opinion is "can I haz plz".
<kennylevinsen>
but it's fine to reach out and give them a heads up instead of insta-banning, as they might not fully have realized just how annoying and spammy such comments are
ity has quit [Remote host closed the connection]
ity has joined #wayland
gnarchie has quit [Remote host closed the connection]
gnarchie has joined #wayland
Brainium has joined #wayland
mdb977 has quit [Remote host closed the connection]
coldfeet has quit [Remote host closed the connection]
leon-anavi has quit [Quit: Leaving]
tzimmermann has quit [Quit: Leaving]
pavlushka has joined #wayland
pavlushka has quit [Ping timeout: 480 seconds]
rasterman has quit [Quit: Gettin' stinky!]
nerdopolis has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
fmuellner has joined #wayland
<orowith2os[m]>
Uhm..... could libinput expose LIBINPUT_ACCEL_NPOINTS_{MIN, MAX} publicly?
<orowith2os[m]>
MAX, at least
<Guest9726>
What is the context for this?
<orowith2os[m]>
I filed https://gitlab.freedesktop.org/libinput/libinput/-/issues/1094 but it was closed by whot for being a niche use case that nobody's hit yet (no complaints there), but I also want to keep in mind if that does change, having mutter Just Work to support the larger NPOINTS_MAX value
Brainium_ has joined #wayland
<orowith2os[m]>
whot: your choice here. I'll just change my mutter patches to hardcode 64 for now
sima has quit [Ping timeout: 480 seconds]
Brainium has quit [Ping timeout: 480 seconds]
Brainium_ has quit [Ping timeout: 480 seconds]
gnarchie has quit []
akimoto has joined #wayland
mvlad has quit [Remote host closed the connection]
akimoto has quit [Remote host closed the connection]
Drakulix has quit [Remote host closed the connection]