00:11 <snakedye> I remember writing some kind of lockscreen and because my cursor was hovering foot it disappeared each time I ran the client and I was unable to click the close button

01:48 <Guest39> Hello! Anyone here using kile?

01:48 <Guest39> I'm having real trouble trying to use the layouts...

09:47 <snakedye> Yes

11:15 <ifreund> leon-p: There have been some waylock issues reported and I have no desire to debug rust code, so I'm going to rewrite it in Zig and might as well make an actually secure protocol first :D

11:16 <ifreund> good point about keyboard focus, should probably just state that it's compositor policy.

11:17 <ifreund> what would likely make sense to implement would be giving the first surface created keyboard focus and changing it if other surfaces are clicked on

11:21 <emersion> leon-p: yes, swaylock hides the cursor

15:14 <ifreund> https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/131

15:15 <ifreund> leon-p: added a bit about keyboard/pointer focus being up to the compositor there :)

15:35 <novakane> dumb question but what does "!100" means on gitlab, just like "#100" on github?

15:45 <ifreund> yep

15:53 <novakane> ok thanks, wasn't sure

15:54 <novakane> personally I just an empty tag as screenlock, a tiling wm is already a great lockscreen for most people :P

15:57 <ifreund> xD

16:00 <tiosgz_> novakane: and switch off all bars to get only the wallpaper :)

16:05 <novakane> tiosgz_: well I don't have any bars so I'm good :D

16:10 <novakane> cool article about the new Allocator in zig 0.9 https://pithlessly.github.io/allocgate.html

16:10 <novakane> ifreund: does the new allocator changes something when you use the c_allocator, like river?

16:12 <ifreund> novakane: yes, the type of std.heap.c_allocator has changed

16:12 <ifreund> depending on your code this might not actually break much though

16:15 <novakane> so it gonna improve a bit performance too?

16:28 <leon-p> ifreund: nice!

16:29 <leon-p> off-topic, but since it came up: I wonder if you can do the reverse of c_allocator: some sort of shim so that malloc and calloc in linked C code can use a user specified allocator.

16:32 <leon-p> ifreund: I looked over the protocol again and I can't find any obvious problems, I think it will both for smaller compositors and the Big Desktops™.

16:32 <leon-p> I'll take another look tomorrow

16:40 <ifreund> leon-p: I've seen that reverse C allocator thing done already, but I can't remember where

16:40 <ifreund> maybe r/zig?

16:41 <ifreund> thanks for taking a look at the protocol!

16:42 <ifreund> I'm also kind of thinking of it as warm up for the river window management protocol I want to do xD

16:53 <novakane> gonna be weird when river window mangement protocol ask for a password everytime you want to focus an other window :P

17:05 <leon-p> for rivers windowmanagement protocol it probably makes sense to look at how X handles window managers for inspiration, even if it'll just server as a _bad_ example.

17:08 <ifreund> I don't expect that the interface I want will look anything like that, I think I just need to get in the right headspace and write a lot of xml and zig to get something working then iterate from there

19:01 <Anderson-D> Is it possible to make some windows non-floating by default? I've seen config to make them float, but how to do the opposite?

19:04 <Anderson-D> Use cases are spotify (XWayland) and minecraft client (XWayland)

19:06 <Anderson-D> And another question: do layout generators manage floating windows as well? Looking for a way to set positions for some floating windows once they appear

19:07 <leon-p> nope, layout generators don't do anything with floating windows