00:40 <snakedye> the new layout protocol seems to assume that you have the same layout generator with the same namespace on both your outputs.

08:14 <novakane[m]> shouldn't `rivertile -main-location top` or I missed something?

08:47 <novakane[m]> oops works*

11:40 <snakedye> Is there anything that could explain this? https://gofile.io/d/uHqZKV

11:44 <snakedye> The layout generator seemingly pushes the correct dimensions but there's no changes on screen. It does works fine on my first output but the views I push on the other get lost in the void.

12:09 <ifreund> can you reproduce it with rivertile?

12:10 <ifreund> oh, I guess they left

12:11 <leon-p> ifreund: it's time for you to get a second output, apparently :P

12:12 <ifreund> well yes, but I can probably try this with WLR_WL_OUTPUTS=2

12:16 <ifreund> I can't reproduce it with rivertile, but I'm also not entirely sure what the expected behavior of snakedye's layout client in that video is

12:54 <snakedye> ifreund when I launch the client, it should reproduce the monocle layout river had before the layout protocol. If I send a command with `./riverctl set-layout-value kile string command "set-tag focused:v:hD"`, it should basically change the full layout for a dwindle layout.

12:57 <snakedye> the empty space is due to me removing some windows. if the client is running and is properly sending layout requests. the entire available space should be occupied by windows (minus gaps).

13:08 <snakedye> small nack, river shouldn't send events related to a layout demand after a commit is sent

13:09 <leon-p> snakedye: there is no avoiding that

13:09 <leon-p> river sends the layout demand and immediately afterwards the view advertising events

13:09 <leon-p> they are already in the queue when your client commits

13:10 <leon-p> but it's fine, your client can just ignore those events

13:13 <snakedye> okay, makes sense

13:16 <snakedye> ifreund I also can't reproduce this with rivertile

13:34 <ifreund> that makes me doubt the bug is on river's side then

19:23 <novakane[m]> I still don't understand how to change the main location now

19:23 <novakane[m]> riverctl mod-layout-value rivertile string main_location top

19:24 <novakane[m]> I thought it was this

19:27 <ifreund> that should work...

19:27 <ifreund> novakane[m]: oh wait, set-layout-value not mod-layout-value

19:27 <ifreund> https://github.com/ifreund/river/blob/0c8e718d95a6a621b9cba0caa9158915e567b076/example/init#L105

19:28 <ifreund> though come to think of it, maybe I shouldn't have added both. rivertile could just interpert the new value as a delta for main count/factor

19:30 <novakane[m]> oh thanks

19:30 <novakane[m]> I thought set-* was just for the first time

19:32 <ifreund> documentation improvements welcome :D

19:33 <novakane[m]> yeah... :D

19:34 <novakane[m]> but what's the point of mod-* then

19:40 <novakane[m]> also is that normal that rivertile -view-padding 10

19:41 <novakane[m]> return err: namespace 'rivertile' already in use.

20:03 <leon-p> only if you have another rivertile running.

20:06 <novakane[m]> so the options can only be set at rivertile launch?

20:09 <leon-p> padding can only be set launch, the others via riverctl

20:10 <novakane[m]> alright I got it, thanks for clearing that up, I wasn't sure