Very nice, I've looked over the documentation several times without noticing there was a ipc interface.
I'l definitely check out that out. Do you think it would be worth it to add a IPC event for a denied focus request? I can have a go at making a pull request for it if you'd be interested, but it might be a bit of a corner case.. On Sun, May 25, 2014 at 6:38 PM, Michael Stapelberg <mich...@i3wm.org> wrote: > Hi Anders, > > Anders Aagaard <aagaa...@gmail.com> writes: >> Question 1: >> I regularly use multiple different screens (with different >> resolutions), I'd love to use for_window to lock the hangouts window >> to the lower right corner of my screen, but I can't really do this by >> px, as the resolutions will constantly change. Can I specify move >> position up 20px, left 20px, with the lower right corner as gravity >> somehow? > Nope. You'll need a custom script for that using the IPC interface, see > http://build.i3wm.org/docs/ipc.html > >> Question 2: >> Often when clicking on the extension (or a person in the chat) I'll >> have a window open with that content on another workspace. In those >> cases chrome will request that window gets focus, but since it's on >> another workspace I won't see that. Is there any option to either >> switch me to the workspace/move the window to the current workspace >> when a window requests focus? (.. and I do realize this option could >> be absolutely horrid if some random window has bad behavior and >> requests focus constantly.. :/ ) > We intentionally disallow these kinds of focus requests for exactly the > reason you cite in your last sentence. src/handlers.c:728 is the place > in the code if you want to patch it yourself and see what happens in > your setup. > > -- > Best regards, > Michael -- Weeks of coding can save you hours of planning. - http://www.codebox.no - http://code.google.com/p/aagaande/