Is there any way to make a window handled by komorebi manually? about komorebi

[crosstyan]

@LGUG2Z Sorry for the late reply. I was busy dealing with other stuff today, and yes, the new manage-rule is wonderful

For some reason Internet Download Manager is still floating though. I think it's because its weird window class #32770 , which means dialog box. It's not a big issue because I prefer it floating anyway.

komorebi is quite perfect for my daily life now, thank you.

Issue closed!

[LGUG2Z]

To have a komorebic command that forces tiling of a window is a great idea, I will add this soon.

I'm curious to know which windows are not getting managed by default.

This is the hook that decides whether or not to try to handle a WinEvent, first by trying to create a WindowManagerEvent from known WinEvents and then by applying some heuristics to see if the window should be managed.

Ideally, all windows should be tiled by default unless there is a specific rule configured to float them.

Can you give me some examples of apps, their window classes and styles that are failing to tile automatically?

[crosstyan]

Can you give me some examples of apps, their window classes and styles that are failing to tile automatically?

• A chat app popular in China called TIM/QQ, whose window class is TXGuiFoundation (TX is the company created this app) and exe is TIM.exe
• Internet Download Manager. The window class is #32770 and exe is IDMan.exe

A command to add rule like float-rule will be a good idea indeed, I can add the window class or exe to that rule.

[LGUG2Z]

@crosstyan I have added komorebic manage and komorebic unmanage to forcibly manage and unmanage windows that don't automatically get tiled. Technically, you could also forcibly unmanage any window, but any window that is automatically registered for tiling at startup would just be tiled again on the next WinEvent.

[crosstyan]

@LGUG2Z That's really quick.

However when I try out the latest commit 8ffe6f7 I get error from komorebi

Aug 20 05:20:06.127 ERROR new{incoming=Mutex { data: Receiver { .. } }}: komorebi: panicked at 'could not determine the current virtual desktop number: ServiceNotCreated', komorebi\src\window_manager.rs:100:10 panic.file="komorebi\\src\\window_manager.rs" panic.line=100 panic.column=10

I think this error is concerning 74811fb because the error keeps appearing until rolling back to 209cd82 (and it's about virtual desktop)

[LGUG2Z]

This was some bad error handling on my part. 😅 Should hopefully be fixed in the latest commit on master, and the commit before that includes support for komorebi manage-rule exe TIM.exe etc.

[LGUG2Z]

@crosstyan Is the latest commit on master working out for you now?