Can not manage Google Chrome

[zarudama]

Hi. I use "bug.n" always.
I love this tool.
I was not able to manage Chrome from yesterday.

Windows Google Chrome Version

34.0.1847.116 m 

i::Manager_getWindowInfo()

ID: 0xd041a
class:  Chrome_WidgetWin_1
title:  New Issue · fuhsjr00/bug.n - Google Chrome
process:    chrome.exe
style:  0x17CF0000
metrics:    x: -4, y: 8, width: 1608, height: 1168
tags:   

Thank your for reply.

[fuhsjr00]

I just downloaded the latest Chrome, and I have no problems, but my config may not be completely standard.

I believe I have had issues with Chrome when the title bar is hidden. Make sure you can see the "X" button in the upper right of the window. If you can't, it may behave weird. I don't remember how to toggle this at the moment, but hopefully this is enough info to help you get started.

[zarudama]

X button and Titlebar is seen regretfully.

Although I am not able to manage chrome at the time of triggering
when it does it for a while why or I come to be able to manage it...

[fuhsjr00]

Ok, in order to track this down, we'll also need the version of bug.n that you're using and your config file if you have one. If you've made any source modifications, let us know.

Also, can you describe more how bug.n isn't managing Chrome? Is the window just not being tiled, or is it behaving oddly once it is?

[zarudama]

I usually use Ubuntu and use bug.n in a company. Therefore the detailed answer is Monday.
Even if Chrome pushed the Win+Cursor key, a focus was in condition not to come. It was in condition to be able to choose it only with Alt+Tab key or a mouse.

[drozzy]

I have the same problem. When I launch google chrome it is not "tiled" automatically. I am using Windows 8.
Using the stable version of bugn (version 830 I think) from here (downloaded April 13, 2014):
https://github.com/fuhsjr00/bug.n/blob/master/bug.n-stable.zip

It seems that it also might be because I already have one chrome window open.. and it's not picking up a new one?

PS: Great program by the way! Love it!!!

[dangavin]

I'm having the same problem. Bug.n rarely, if ever, detects the Chrome window on opening. After some time, or sometime after an interaction with Chrome (e.g. opening a new tab, downloading a file), bug.n will suddenly start managing Chrome. However, I haven't found any clear pattern to when or why this happens.

[ahri]

I have this issue, too; I have 3 Chrome windows open, and only one is being tiled. They also have the decorations switched on, though #+d can get rid of them.

I also can't move them to another view via #+3 etc.

I'm on master; b0a3181, using the default config/hotkeys -- I didn't change anything; downloaded and ran the exe :)

Chrome window that is working (tiling):

ID: 0x26ce0d8a
class:  Chrome_WidgetWin_1
title:  Tzbob/python-windows-tiler - Google Chrome
process:    chrome.exe
style:  0x16CF0000
metrics:    x: 0, y: 15, width: 1152, height: 1065
tags:   1

Versus one that isn't:

ID: 0x5f0ccc
class:  Chrome_WidgetWin_1
title:  Can not manage Google Chrome · Issue #1 · fuhsjr00/bug.n - Google Chrome
process:    chrome.exe
style:  0x17CF0000
metrics:    x: -8, y: 7, width: 1936, height: 1041
tags:   

The "tags" portion is empty.

I can resize and move the Chrome windows, and I note that they appear on every View.

PS. this app is awesome anyway, pun intended ;)

Edit: I'm on Win8.1, if that has any bearing, here's a window list, while I have a a bunch of Chrome processes running:

Active Window
0:  

Window List
0x2ab0f5a:  index.html (~\repos\mapdone-html5\app) - GVIM1
0x47f0af8:  root@optitron:~
0x4bd0f02:  Untitled - Notepad
0x15a90d06: Calculator
0x1c0dac:   bug.n-master
0x20a00114: Warning
0x170c02:   app.js (~\repos\angular-phonecat\app\js) - GVIM
0x4f0eda:   Cmder

As you can see it's not picking up any of my 5 Chrome windows.

[KyleSolo]

Removing the Chrome-specific code near the beginning of Manager_manage in Manager.ahk fixed this for me. It looks like that code is a workaround for something, maybe it isn't needed anymore? I didn't look into it too deeply.

[EdVanDance]

Had the same problem.
The solution by @KyleSolo works perfectly so far.
Thanks a lot @KyleSolo.

[darsain]

If this fixes the issue, could we get a standalone released?

Stumbled upon bug.n today and it looks great, except this little issue makes it unusable for me.

Tried removing the If (wndProcessName = "chrome.exe") conditional from src/Manager.ahk, but it had no effect, so I guess the src folder is already embedded in the executable? Anyway, don't know AHK, don't want to install it as I have no use for it apart of this, so please fix & standalone? :)

Or is this project abandoned?

[fuhsjr00]

Not abandoned, just idle. Time constraints.

All of the source is wrapped up in the executable, but you can verify that the change works by installing AutoHotKey and running Main.ahk.

I'll look into making a new executable, but it would be nice to get more confirmations that @KyleSolo's fix works.

[darsain]

@fuhsjr00 are you unable to replicate? It is quite simple. Just have more than 1 Chrome window. All but the 1st one are ignored by bug.n

[fuhsjr00]

Ok, I was able to reproduce the problem, and I have seen that eliminating that block of code makes things work. I'm very much in favor of dropping app-specific code, so I'll get this put together.

Thanks all.

[fuhsjr00]

Ok, I've pushed the suggested change to github and updated bug.n-dev.exe. Someone should let me know if this works for them.

[morinted]

Hi @fuhsjr00, that build works for me and fixes the issue! The only problem with Chrome, now, is that it insists on opening maximized, which bug.n doesn't like. Additionally, when it displays a pop-up (JavaScript Alert), it treats the pop-up as a new Window, where it shouldn't.

But I'd say this issue is fixed 👍

[joten]

The only problem with Chrome, now, is that it insists on opening maximized, which bug.n doesn't like.

This is set by rule 12: Config_rule_#12 := "Chrome_WidgetWin_1;.*;;1;0;0;0;1;0;Maximize". You can override it by adding the following line to your Config.ini:
Config_rule_#12=Chrome_WidgetWin_1;.*;;1;0;0;0;1;0;

-- Personally, I prefer Browser windows maximized; it reduces the windows title bar height.

Additionally, when it displays a pop-up (JavaScript Alert), it treats the pop-up as a new Window, where it shouldn't.

Again, rule 12. You can override it with the following line added to your Config.ini:
Config_rule=Chrome_WidgetWin_1;.*;0x80000000;0;0;0;1;1;0;

-- I myself do not like this 'pop-up problem'. I think it will be solved in the next major release with a revision of all rules. But in between there is still one minor release; therefor it will take a while until this is done.

[fuhsjr00]

It sounds like this issue is fixed.