ifreund changed the topic of #river to: river - a dynamic tiling wayland compositor || https://github.com/riverwm/river || channel logs: https://libera.irclog.whitequark.org/river/
lxsameer has quit [Ping timeout: 256 seconds]
elshize has joined #river
waleee has quit [Ping timeout: 240 seconds]
vaivis has joined #river
vaivis has quit [Read error: Connection reset by peer]
snakedye has quit [Ping timeout: 248 seconds]
Guest86 has joined #river
<Guest86> Hi trying to build this on AARCH64 and am getting "unable to override alignment of packed struct fiends" errors in the zig compilation.  Has anyone else run into this?
<Guest86> zig version 0.10.0-dev
<Guest86> *fields not fiends
vaivis has joined #river
vaivis has quit [Quit: WeeChat 3.5]
Guest86 has quit [Quit: Client closed]
pkap has joined #river
pkap has quit [Quit: Client closed]
lxsameer has joined #river
<novakane> because you need zig 0.9
<tiosgz`> can a layout generator know which view is focused? and can it decide to hide some views?
<novakane> it can't, not with the layout protocol, the focused view is known with the river status protocol though
<novakane> but I'm not sure how you could hide it
<novakane> the only way to hide view is to send it to an unfocused tag, that would probably be hacky to implement in a layout generator
<tiosgz`> then i can at least stay somewhat realistic :P
<tiosgz`> thanks :)
snakedye has joined #river
<leon-p> tiosgz`: all a layout generator can do is propose sets coordinates and dimensions, exactly as many as river demands. It only sets the layout and has no influence on window management, hence the name.
lxsameer has quit [Ping timeout: 250 seconds]
lxsameer has joined #river
<tiosgz`> i swear i was already going to read it sometime earlier
<tiosgz`> perhaps we disagree on how far a layout goes, but whatever. i see how it's better most of the time to keep it limited
snakedye_real has joined #river
snakedye_real has quit [Quit: snakedye_real]
lxsameer has quit [Ping timeout: 246 seconds]
snakedye_real has joined #river
snakedye_real has quit [Quit: snakedye_real]
snakedye_real has joined #river
waleee has joined #river
elshize has quit [Quit: WeeChat 3.4]
snakedye_real has quit [Ping timeout: 256 seconds]
elshize has joined #river
elshize has quit [Ping timeout: 240 seconds]
elshize has joined #river
elshize has quit [Ping timeout: 246 seconds]
elshize has joined #river
lxsameer has joined #river
groknull has joined #river
groknull has quit [Remote host closed the connection]
<tiosgz`> leon-p: > layout generators can use this to display useful information to the user, like for example how many views are currently *hidden in an overflow area*
<tiosgz`> this is what i meant IIUC. i suppose it ended only in that blog post though?
<leon-p> tiosgz`: don't interpret too much into it. What I had in mind was basically just what my layout generator, stacktile, does: There is an overflow area, where windows are stacked, hence the name
<tiosgz`> ah, gotcha
<tleydxdy[m]> err, cannot figure out how to make the cursor warp correctly
<tleydxdy[m]> so moving my mouse would cause the handleMotion function to be called right? and in the event there is event.device which is a *wlr.InputDevice. this would be a pointer to my mouse? if so then when I do self.wlr_cursor.warp(null, lx, ly)) which also cause the handleMotion function to be called, what would the event.device be?
<tleydxdy[m]> if it doesn't call handleMotion, then why would the cursor become unhide?
snakedye_real has joined #river
elshize has quit [Ping timeout: 246 seconds]
elshize has joined #river
elshize has quit [Ping timeout: 246 seconds]
elshize has joined #river
lxsameer has quit [Ping timeout: 246 seconds]