[BUG]: Komorebi doesn't manage NAPS2 windows properly
Summary
NAPS2 is an application for scanning documents. but whenever I open it, it opens in a state "unmanaged" by komorobi, ie, it doesnt tile, nor does it hide when switching between workspaces. I have attached a video to demonstrate the issue. when I minimize and restore window, it works - but as soon as NAPS2 opens a sub window for scanning progress dialogue - komorobi stops managing NAPS2 again.
https://github.com/user-attachments/assets/2e0da8e1-fd9b-44ac-a710-a60f291d99ab
Version Information
OS Name: Microsoft Windows 11 Home Single Language
komorebic 0.1.36 tag:v0.1.36 commit_hash:8ef1bcf2 build_time:2025-04-13 03:10:57 +00:00 build_env:rustc 1.86.0 (05f9846f8 2025-03-31),stable-x86_64-pc-windows-msvc
Komorebi Configuration
{
"$schema": "https://raw.githubusercontent.com/LGUG2Z/komorebi/v0.1.36/schema.json",
"app_specific_configuration_path": "$Env:USERPROFILE/applications.json",
"window_hiding_behaviour": "Cloak",
"cross_monitor_move_behaviour": "Insert",
"default_workspace_padding": 2,
"default_container_padding": 2,
"border": true,
"border_width": 2,
"border_style": "Square",
"border_offset": 0,
"stackbar": {
"height": 16,
"width": 250,
"label": "Title",
"tabs": {
"font_family": "JetBrainsMono Nerd Font",
"font_size": 16
}
},
"theme": {
"palette": "Base16",
"name": "Ashes",
"unfocused_border": "Base03",
"bar_accent": "Base0D"
},
"monitors": [
{
"workspaces": [
{
"name": "I",
"layout": "BSP"
},
{
"name": "II",
"layout": "BSP"
},
{
"name": "III",
"layout": "BSP"
},
{
"name": "IV",
"layout": "BSP"
},
{
"name": "V",
"layout": "BSP"
},
{
"name": "VI",
"layout": "BSP"
},
{
"name": "VII",
"layout": "BSP"
}
]
}
]
}
Hotkey Configuration
#Requires AutoHotkey v2.0.2 #SingleInstance Force
Komorebic(cmd) { RunWait(format("komorebic.exe {}", cmd), , "Hide") }
!q::Komorebic("close") !m::Komorebic("minimize")
; Focus windows !h::Komorebic("focus left") !j::Komorebic("focus down") !k::Komorebic("focus up") !l::Komorebic("focus right")
!+[::Komorebic("cycle-focus previous") !+]::Komorebic("cycle-focus next")
; Move windows !+h::Komorebic("move left") !+j::Komorebic("move down") !+k::Komorebic("move up") !+l::Komorebic("move right")
; Stack windows !Left::Komorebic("stack left") !Down::Komorebic("stack down") !Up::Komorebic("stack up") !Right::Komorebic("stack right") !;::Komorebic("unstack") ![::Komorebic("cycle-stack previous") !]::Komorebic("cycle-stack next")
; Resize !=::Komorebic("resize-axis horizontal increase") !-::Komorebic("resize-axis horizontal decrease") !+=::Komorebic("resize-axis vertical increase") !+_::Komorebic("resize-axis vertical decrease")
; Manipulate windows !t::Komorebic("toggle-float") !f::Komorebic("toggle-monocle")
; Window manager options !+r::Komorebic("retile") !p::Komorebic("toggle-pause")
; Layouts !x::Komorebic("flip-layout horizontal") !y::Komorebic("flip-layout vertical")
; Workspaces !1::Komorebic("focus-workspace 0") !2::Komorebic("focus-workspace 1") !3::Komorebic("focus-workspace 2") !4::Komorebic("focus-workspace 3") !5::Komorebic("focus-workspace 4") !6::Komorebic("focus-workspace 5") !7::Komorebic("focus-workspace 6") !8::Komorebic("focus-workspace 7")
; Move windows across workspaces !+1::Komorebic("move-to-workspace 0") !+2::Komorebic("move-to-workspace 1") !+3::Komorebic("move-to-workspace 2") !+4::Komorebic("move-to-workspace 3") !+5::Komorebic("move-to-workspace 4") !+6::Komorebic("move-to-workspace 5") !+7::Komorebic("move-to-workspace 6") !+8::Komorebic("move-to-workspace 7")
; disable windows keys #1:: #2:: #3:: #4:: #5:: #6:: #7:: #8:: #9:: { return }
Output of komorebic check
KOMOREBI_CONFIG_HOME detected: D:\OneDrive\Documents\Komorebi
Looking for configuration files in D:\OneDrive\Documents\Komorebi
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\prana.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
I suggest opening a bug report with NAPS2 and backlinking it here - when applications behave like this it's usually because they are not adhering to Win32 application development standards