ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
emilio[m] has joined #wayland
pac85[m] has joined #wayland
ybogdano has quit [Ping timeout: 480 seconds]
silverdev2482 has quit []
silverdev2482 has joined #wayland
silverdev2482_ has joined #wayland
silverdev2482_ has quit [Remote host closed the connection]
co1umbarius has joined #wayland
silverdev2482 has quit [Ping timeout: 480 seconds]
soreau has quit [Read error: Connection reset by peer]
soreau has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
<LaserEyess>
better ask now then
mclasen has quit [Ping timeout: 480 seconds]
mclasen has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
fmuellner has quit [Read error: Connection reset by peer]
fmuellner has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
silverdev2482 has joined #wayland
silverdev2482 has quit []
silverdev2482 has joined #wayland
<zebrag>
yeah, right
silverdev2482 has quit [Remote host closed the connection]
silverdev2482 has joined #wayland
nyah has quit [Ping timeout: 480 seconds]
silverdev2482 has quit [Ping timeout: 480 seconds]
c6ristian has quit [Ping timeout: 480 seconds]
Shimmy[m] has joined #wayland
silverdev2482 has joined #wayland
<silverdev2482>
ello I have a problem. I want to play a game (Rain World) with my friends. Through a mod it has local multiplayer. However there is a catch, only one person can use a keyboard and the rest have to use controllers. So I want a way to use mutiple keyboards to play toghther. My idea is map a specific keyboard to a virtual controller then either make it so the system doesn't see the
<silverdev2482>
keyboard or the game doesn't see the keyboard. One minor problem: I don't have a clue on how to do this. I saw qjoypad but it hasn't been updates since 2010, doesn't support wayland, and probably will map all keyboards to a controller. I saw antimicrox but it maps controllers to keyboards so not what I want. I also would like to customise the keybinds since I use an alternate
<silverdev2482>
keyboard layout and use weird keys for movement. I would prefer to map keys to the dpad instead of joystick. I am on gentoo using sway. Anything I can do?
BilalElmoussaoui[m] has joined #wayland
nazarewk[m] has joined #wayland
Moprius has joined #wayland
Moprius has quit []
mclasen has quit [Ping timeout: 480 seconds]
doras has joined #wayland
silverdev2482_ has joined #wayland
silverdev2482_ has quit []
<zebrag>
silverdev2482: there is a #sway channel, but you must know that already
fmuellner has quit [Ping timeout: 480 seconds]
nielsdg has joined #wayland
DemiMarie has joined #wayland
DemiMarie is now known as Guest6853
zebrag has quit [Quit: Konversation terminated!]
Company has quit [Read error: Connection reset by peer]
drakulix[m] has joined #wayland
psydroid[m] has joined #wayland
inkbottle[m] has joined #wayland
Mershl[m] has joined #wayland
teh1[m] has joined #wayland
arichardson[m] has joined #wayland
hex[m]1 has joined #wayland
slattann has joined #wayland
tleydxdy has joined #wayland
jgrulich has joined #wayland
danvet has joined #wayland
tzimmermann has joined #wayland
feaneron has joined #wayland
JosExpsito[m] has joined #wayland
jmdaemon has joined #wayland
naveenk2 has joined #wayland
mvlad has joined #wayland
mvlad has quit [Quit: Leaving]
mvlad has joined #wayland
jgrulich has quit [Remote host closed the connection]
soreau has quit [Read error: Connection reset by peer]
MajorBiscuit has joined #wayland
soreau has joined #wayland
Major_Biscuit has quit [Ping timeout: 480 seconds]
<pq>
daniels, if you think porting screen-share to fullscreen shell is easy, go ahead. I wouldn't know and I wouldn't review that. ;-)
<daniels>
pq: 'to' f-s? :P
<pq>
I would review getting screen-share tested in CI, though.
<pq>
*from
<daniels>
yeah
<daniels>
I'm not volunteering for now tbh
<pq>
I think the use of fullscreen-shell is one of the smaller problems of screen-share.
<pq>
Maybe screen-share should just be, say, a pipewire source, rather than something that spawns another Weston with a pre-baked client Wayland connection, and shuffles pixels through CPU memory.
<pq>
but that's ignoring the input delivery
<daniels>
yeah ...
fahien has quit [Ping timeout: 480 seconds]
qyliss_ has left #wayland [#wayland]
qyliss_ has joined #wayland
qyliss_ has quit []
qyliss has joined #wayland
<emersion>
pq, let me know if you had an alternative idea for !51. i just went with one possible solution, but maybe there's a better one
<daniels>
emersion: do you mean wayland!255?
<daniels>
(nice number that)
<emersion>
ah, no, libdisplay-info
<daniels>
ah yeah ok, I'm not following that one :)
<pq>
emersion, nothing obviously better off-hand, no. Seems to do the job.
<daniels>
btw, on wayland!255 for the tests, I didn't really understand what the impetus was, but my inclination would be to just follow whatever the rest of the ecosystem does - if making meson test fail when tests are disabled is normal then great, but if it's going to surprise distros who have running tests as part of their default setup but might want to disable them, then that surprise is probably not good
<emersion>
distros can just not invoke the "test" task, if they don't want tests
<pq>
I wouldn't know how distro scripts work, do they need to add code instead of remove to skip executing tests.
<emersion>
for all distros i've seen, tests are separate from build, and executing tests is done by adding a line
<emersion>
but i'm not familiar with debian or fedora
<pq>
ok
<pq>
what about the meson subproject aspect? anything to consider these?
<qyliss>
in nixpkgs tests are usually part of the build, and we execute tests for some build systems by default (not sure about meson)
<pq>
*there
<emersion>
i don't know what other Meson projects are doing
<emersion>
in any case, if someone disables the tests, i don't mind if they need to do something more to disable the test task in their package builder
<pq>
like if someone if using libwayland as a subproject and wants to run some tests in the tree of projects but not libwayland's
digitalfavshetheyname[m] has left #wayland [#wayland]
<emersion>
the test target only runs tests for the parent project
<pq>
aha, ok then.
<emersion>
`meson test "mysubproject:"` can be used to run subproject tests, but it's opt-in