vaivis has quit [Read error: Connection reset by peer]
vaivis has joined #river
waleee has joined #river
waleee has quit [Ping timeout: 240 seconds]
vaivis has quit [Read error: Connection reset by peer]
snakedye has joined #river
vaivis has joined #river
vaivis has quit [Read error: Connection reset by peer]
waleee has joined #river
snakedye has quit [Ping timeout: 246 seconds]
snakedye has joined #river
alebastr has quit [Quit: WeeChat 3.4]
alebastr has joined #river
<tiosgz`>
<tleydxdy[m]> "basically since the sticky..." <- i'm reading this week's log only now :D
<tiosgz`>
this reminded me i also sometimes have this issue
<tiosgz`>
basically every time i have one reference view with more tags and want to switch between two other views each with one of the tags
<tiosgz`>
the reference view keeps getting focused on its own
<tiosgz`>
i think the focus stack should only push focused views to the top, and leave the rest of the active tag where-ever it is
<tiosgz`>
does that sound reasonable? or is there a reason why the whole tag(s) is pushed to the top?
<tiosgz`>
(or do i completely misunderstand what's going on?)
<tleydxdy[m]>
I think the problem is that all the views are in one big stack
<tleydxdy[m]>
so when mutiple tags are selected their ordering might not be what one expects
<tiosgz`>
perhaps i forgot one thing: only one of the tags is active at a time
<tleydxdy[m]>
I suppose one solutions is to also make so you mean the reference view is always on top
<tleydxdy[m]>
even when you have zoomed other views on top in each of the tags?
<tleydxdy[m]>
s/I suppose one solutions is to also make//
<tleydxdy[m]>
lmao
<tleydxdy[m]>
forgot to memset my buffer
<tiosgz`>
example: view A == tags 0b10, B == 0b01, C == 0b11. currently focused is tag 0b10, view A
<tiosgz`>
i switch to tag 01, C is focused. i focus B
<tiosgz`>
back to 10, C is focused. i focus A
<tiosgz`>
etc
<tleydxdy[m]>
if you created the views in order, the stack would be CBA, so when you do the first focus the stack becomes BCA, and the BAC
<tleydxdy[m]>
i.e. because C is created last, it is automatically on top of everything else
<tiosgz`>
but C keeps getting focus over and over again every time i change tag, regardless of how many times i switch the focus away to another view
<tleydxdy[m]>
oh
<tleydxdy[m]>
interesting
<tiosgz`>
thus i think the stack is (start == top) ACB, then CBA, then BCA, then CAB, then back ACB and so on
<tleydxdy[m]>
lemme see if I can repro it
<tleydxdy[m]>
yeah, I've also noticed more unintentional focus switching from my dwm build for some reason
<tiosgz`>
hmm. i've now tried to write up the right sequence and realised it could be impossible without all three views being displayed at one point
<tiosgz`>
ACB, CAB, BCA, CBA, ACB. damn. it's the same as above. i'll try if i can work around it
<tleydxdy[m]>
damn my river lost the tag-mask again
<tiosgz`>
apparently it was no design issue, just a weird consequence of the tagging system
<tiosgz`>
if i first have tags 11 and focus A and B, it then works as expected
<tiosgz`>
thanks for rubberducking :)
<tleydxdy[m]>
np
<leon-p>
tiosgz`: It's not the order of the stack that's throwing you off, it's the focus history. When you move to a different tag set, but one view is kept active, then it is likely the most recently focused view and as such gets focused again
<tleydxdy[m]>
interesting
<tiosgz`>
leon-p: yeah, i used '[focus] stack' to mean focus history
<tleydxdy[m]>
why tho, I get that if the currently focused view is still visible then it should remain in focus
<tleydxdy[m]>
but if none are it should focus the one on top, rather than the most recently focues one
<tleydxdy[m]>
s/focues/focued/
<tiosgz`>
tleydxdy: because when switching between two tags with no intersection, the IMO expected behaviour is to keep focus 'per tag'
<tleydxdy[m]>
hmm
<tleydxdy[m]>
seem like we ought to take out the common views
<tleydxdy[m]>
since if they are not focused before, they probably should not get focus afterwards
<tleydxdy[m]>
i.e. only consider the newly visible views
<tleydxdy[m]>
anyone have any idea what could be resetting my spawn-tagmask?
<tleydxdy[m]>
lmao case closed
<tleydxdy[m]>
it was my monitor going to sleep
<tleydxdy[m]>
err, what do I do now
<tleydxdy[m]>
hmm, wouldn't this cause that output to loose position/views also?
lxsameer has quit [Ping timeout: 256 seconds]
notzmv has quit [Ping timeout: 248 seconds]
snakedye_ has joined #river
snakedye_real has joined #river
snakedye_ has quit [Quit: snakedye_]
snakedye_real has quit [Ping timeout: 240 seconds]
snakedye_ has joined #river
snakedye_ has left #river [#river]
vaivis has joined #river
vaivis has quit [Read error: Connection reset by peer]