fuhsjr00 / bug.n

Tiling Window Manager for Windows
GNU General Public License v3.0
3.35k stars 214 forks source link

config rule of vs code is not set correctly #248

Closed tianxiayu007 closed 4 years ago

tianxiayu007 commented 4 years ago

my config are as follows:

; bug.n - tiling window management
; @version 9.0.2

Config_horizontalBarPos=center
Config_verticalBarPos=tray
Config_barWidth=20%
Config_singleRowBar=0
Config_fontName=simsun
Config_fontSize=9
Config_backColor_#1=101010;603000;Black;603000;Black;603000;000060;404040;080808
Config_backColor_#2=808080;;;;;;;202020;080808
Config_foreColor_#1=404040;101010;Black;101010;Black;101010;Black;404040;202020
Config_foreColor_#2=4040ff;;;;;;;0000ff;0000ff
Config_foreColor_#3=;;;;;;;010101;
Config_fontColor_#1=White;White;White;White;White;White;White;Black;808080
Config_fontColor_#2=Black;;;;;;;White;White
Config_fontColor_#3=;;;;;;;Black;
Config_readinBat=0
Config_readinDate=0
Config_readinTime=0
Config_readinVolume=0
Config_readinInterval=10000
Config_showTaskBar=1
Config_viewNames=1;2;3;4
Config_areaTraceTimeout=2000
Config_continuouslyTraceAreas=1
Config_ghostWndSubString= (Keine Rückmeldung)
Config_mouseFollowsFocus=0
Config_rule_#1=.*;.*;;1;0;0;0;1;0;
Config_rule_#2=.*;.*;Window_isChild;0;0;0;1;0;0;
Config_rule_#3=.*;.*;Window_isPopup;0;0;0;1;0;0;
Config_rule_#12=Chrome_WidgetWin_1;.*Code;;1;1;1;0;1;1;
Config_rule_#13=Chrome_WidgetWin_1;.*Chrome;;1;1;2;0;1;1;maximize
Config_autoSaveSession=off
Config_maintenanceInterval=1000
Config_hotkey=#c::
Config_hotkey=#q::Manager_closeWindow()
Config_hotkey=#^o::Manager_override(1;0;0;0;1;0;)
Config_hotkey=#i::
Config_hotkey=#^i::Manager_getWindowInfo()
Config_hotkey=#.::
Config_hotkey=#5::
Config_hotkey=#+5::
Config_hotkey=#^5::
Config_hotkey=#6::
Config_hotkey=#+6::
Config_hotkey=#^6::
Config_hotkey=#7::
Config_hotkey=#+7::
Config_hotkey=#^7::
Config_hotkey=#8::
Config_hotkey=#+8::
Config_hotkey=#^8::
Config_hotkey=#9::
Config_hotkey=#+9::
Config_hotkey=#^9::
Config_hotkey=#^e::Run, edit C:\Users\lbc\AppData\Roaming\bug.n\Config.ini
Config_hotkey=#+s::
Config_hotkey=#^r::Main_reload()
Config_hotkey=#+r::Reload
Config_hotkey=#+q::ExitApp
Config_hotkey=#Enter::Run, wt.exe
1.

from above we can see that, the rule for vs code window is Config_rule_#12=Chrome_WidgetWin_1;.*Code;;1;1;1;0;1;1; but not Config_rule_#12=Chrome_WidgetWin_1;.*Code;;1;1;1;0;1;1;maximize while rule for Chrome is set up correctly 1

2.

the second point is that, in tag 1, i only open 2 vs code window, but bug.n says it find 3. to show this, i change mode to monocle and take a screenshot but why this happen? i even don't know which window it is, it even has no title 2

3.

because points of 1,2, i can't switch vs code window use #up or #down in tile mode(i only can see one window at a time, the other one can't be switched, because it is maximize?), and also the layout is wrong(vs code is maximize, while notepad is above it, the layout not split into master and stack in tile mode) image

tianxiayu007 commented 4 years ago

i just find that, the window without title is:

ID: 0x1038c
class:  NarratorHelperWindow
title:  
process:    svchost.exe [9580]
style:  0x14C00000
metrics:    x: 1150, y: 0, width: 771, height: 521
tags:   1

Config_rule=NarratorHelperWindow;;;1;1;1;0;1;0;

this is very strange because it is a background process i add a rule to avoid this(may be added to default rule?😀): Config_rule=NarratorHelperWindow;.*;;0;

tianxiayu007 commented 4 years ago

my bad, i find point 1 is because vs code was opend with maximize, it retain the previous maximize state before i use bug.n, if i unmaximize it then the tile mode works fine

tianxiayu007 commented 4 years ago

from all above, we can learn that add one rule below may be useful on win10🤣,

Config_rule=NarratorHelperWindow;.*;;0;

in short, bug.n works fine currently, i will close this issue