Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Virtualbox -- Has anyone been able to control VB with bug.n? #161

Open
jwmurray opened this issue Feb 22, 2018 · 10 comments
Open

Virtualbox -- Has anyone been able to control VB with bug.n? #161

jwmurray opened this issue Feb 22, 2018 · 10 comments

Comments

@jwmurray
Copy link

When I start virtualbox and the subsequent VMs under VB, bug.n does not control them. has anyone else gotten this to work?

Thank you!

john

@joten
Copy link
Collaborator

joten commented Feb 24, 2018

Incidentally, I do use VirtualBox, too, and saw, that it is written with Qt5, which is not covered by rule no. 4. Config_rule=Qt5QWindowIcon;.*;;1;0;0;0;0;0; solved the problem for me, but you may want different rules for the pop-up windows (starting and exiting a vm), which otherwise will also be tiled.

@joten joten added the rule label Feb 24, 2018
@jwmurray
Copy link
Author

jwmurray commented Feb 24, 2018 via email

@lluke777
Copy link

It solves issue with qt applications, but there are some windows from Control Panel like Mouse, Color Management and Advanced System Settings/System Propeties that are out of control. What to do with that?
There is also old WinAmp application that is out of control.

@jwmurray
Copy link
Author

jwmurray commented Feb 26, 2018 via email

@joten
Copy link
Collaborator

joten commented Feb 26, 2018

@lluke777: Do you mean the Windows 10 Settings App with class = ApplicationFrameWindow and process = ApplicationFrameHost.exe?
You will need to add a corresponding rule, since those windows are not managed by bug.n by default. Config_rule=ApplicationFrameWindow;.*;;0;;;;;1; would go to far.

@jwmurray: Yes, by default bug.n keeps track of open windows (by window id) and restores the corresponding settings. You may use the following configuration variable to reset or keep those settings when restarting bug.n: Config_autoSaveSession=ask.

@joten joten added the question label Feb 26, 2018
@lluke777
Copy link

lluke777 commented Feb 27, 2018

There is opposit problem with Total Commander application. While copying small pop up windows appear and rearange positions of windows. How to prevent this happen?

@joten
Copy link
Collaborator

joten commented Feb 28, 2018

Try WinI to get the window information and copy the rule to your Config.ini with ;0;0;0;1;1;1; as the last part of the rule, just like the one for pop-up windows (Config_rule_#3=.*;.*;Window_isPopup;0;0;0;1;1;1;) and have a look at doc/Configuring_rules for more information on rules.

@shaunsmiley-rms
Copy link

I can confirm that adding
Config_rule=Qt5QWindowIcon;.*;;1;0;0;0;0;0;
to config.ini solves the problem for me too.

@lluke777
Copy link

I have added new rule for Windows Magnifier (using WIN + '+')
Config_rule=#19 := "MagUICl-ass;Magnifier;;1;1;2;0;0;0;"
and increased counter
Config_ruleCount := 19
unfortunatelly all new applications that are opened in bug.n are not tiling.

What I am doing wrong?

@joten
Copy link
Collaborator

joten commented Apr 13, 2018

Are all new applications still not tiled by bug.n without the addition of Config_rule=#19 := "MagUICl-ass;Magnifier;;1;1;2;0;0;0;" and Config_ruleCount := 19?

Please try to add the rule via the Config.ini file, not setting Config_ruleCount, but adding the following line:

Config_rule=MagUICl-ass;Magnifier;;1;1;2;0;0;0;

(Is there really a hyphen in the class name? Do you want to appear those windows on monitor 1, view 2? Sorry, I am currently not running Windows and cannot test it myself.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants