Starting to implement the client side of this I realize it might be good to know the workspace of the window in question. That's easy enough to add. Also technically we could skip the "changed" field, as the "focused" field in the container will tell you the same information. I also wouldn't mind knowing the window class. Any technical reason that's not already in the Con class?
On Tue, May 27, 2014 at 7:43 PM, Anders Aagaard <aagaa...@gmail.com> wrote: > Sent a patch to http://cr.i3wm.org/patch/559 now. I unfortunately > can't get the tests running. Trying to start up a x session with > Xdummy seems to make the nvidia driver explode... I've done some > manual testing and I really don't see how this could screw up anything > else (.. famous last words I know). > > It's been a good 5 years since I've written any C or perl, so any > comments are welcome :) > > I can do testing in a VM if needed, but I won't have time for that > tonight. If I make some slightly larger pull requests I will set that > up though. > > On Mon, May 26, 2014 at 8:56 AM, Michael Stapelberg <mich...@i3wm.org> wrote: >> Hi Anders, >> >> Anders Aagaard <aagaa...@gmail.com> writes: >>> 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.. >> That sounds reasonable. That way, a third-party script can make the >> decision (based on arbitrarily complex rules) on what to focus. Submit >> patches at http://cr.i3wm.org/ :). >> >> -- >> Best regards, >> Michael > > > > -- > Weeks of coding can save you hours of planning. > - http://www.codebox.no > - http://code.google.com/p/aagaande/ -- Weeks of coding can save you hours of planning. - http://www.codebox.no - http://code.google.com/p/aagaande/
