#Problem with floating layout

1 messages · Page 1 of 1 (latest)

gleaming bane
#

Hello so i have 2 monitors one have floating layout and other have v-stack and when floating layout is empty and i move app from v-stack to floating then v-stack layout will broke and when i switch workspaces on monitor with that floating point then i can see apps on my second monitor are moving too because they are somehow pinned to the monitor where i have floating layout. To fix that i need to move all apps from that second monitor to that floating layout and then move that to workspace with no floating layout and then from that layout i can only move them back to the second monitor. I have no idea if i explained that corretly and sorry for my english its not my first language. i forgot to add that iam moving my apps to floating layout using mouse cause with binds my app disappears

olive tide
#

First it is important to know what version of komorebi are you using? Try running komorebic version on the terminal...

#

Second: How are you moving the app from the monitor with VStack to the monitor with floating layout? Keybind? What command? With mouse?

#

Third: I might be wrong but I don't think those initial-workspace-rules work without a "matching-strategy": "Equals" or something like that...

gleaming bane
#

yea i added on the end that iam using mouse

#

because with keyboard my apps disappear

olive tide
#

Also it might be useful to know more info about your monitors, try running: komorebic monitor-info

gleaming bane
olive tide
#

Oh I see that you are using an older version. Version 0.1.29 has already been released can you try updating and see if the issue persists?

gleaming bane
#

i realised that i have 1.28 not 1.29 version too

#

yeee

#

still same problem

olive tide
#

Did you stop komorebi before updating?

gleaming bane
#

iam moving my window to floating layout monitor and if i want that window back to that v-stack then it cant attach

coral chasmBOT
#

GG @gleaming bane, you just advanced to level 1!

gleaming bane
#

i forgot stopping but after that stop and start is not enough?

olive tide
#

And it succeeded in updating with it running?

#

I would probably stop it and force update it again...

#

Also try using keybinds with the new version! I'm using them and it works fine...

#

I do however noticed some weird behavior when using the mouse...

gleaming bane
#

it is weird with versioning because with komorebic --version it shows 1.28 but with scoop update komorebi whkd it shows 1.29 latest version

olive tide
#

Run where.exe komorebic on the terminal

#

You might have both versions installed

#

And it is defaulting to 0.1.28

#

If where.exe shows more than one, then try scoop uninstall komorebi; scoop install komorebi

gleaming bane
#

all still the same on 1.29

olive tide
#

There is this issue I've just created and I'm looking into fix it. However on 0.1.29 you should be able to move windows between monitors using a keybind to a command like komorebic cycle-move-to-monitor next or komorebic move-to-monitor 0 where 0 is the index of the monitor you want to move to... These commands work well with moving windows to/from floating workspaces...

GitHub

Summary Currently when using the mouse to move windows, komorebi only checks to start a move operation if the origin workspace is tiling and it checks for the focused container so if we move floati...

gleaming bane
#

and iam having issues with window focusing on floating layer like i cant click on window cause my mouse is moved each time to the middle of the screen, but i could not found the source of the issue

#

and like it happens to me rarely

olive tide
coral chasmBOT
#

GG @olive tide, you just advanced to level 5!

olive tide
gleaming bane
olive tide
gleaming bane
#

so thank you for help ❤️