On Tue, 2017-08-22 at 15:38 +0200, Roman Gilg wrote:
> Calling xwl_window_from_window means looping through the window ancestor
> chain whenever it is called on a child window or on an automatically
> redirected window.
>
> Since these properties and the potential ancestor's xwl_window are constan
On Tue, 22 Aug 2017 15:38:26 +0200
Roman Gilg wrote:
> Calling xwl_window_from_window means looping through the window ancestor
> chain whenever it is called on a child window or on an automatically
> redirected window.
>
> Since these properties and the potential ancestor's xwl_window are const
I've just sent another version with different naming and the additional
function for comparing the private field's xwl_window with its creator as
reply to your mail. Take a look how you like it. One other difference: I
realized that the xwl_window_find(..) function is unneeded, since when
putting t
On Sat, 12 Aug 2017 03:45:39 +0200
Roman Gilg wrote:
> On Thu, Aug 10, 2017 at 2:49 PM, Pekka Paalanen wrote:
> > Assuming the theory is sound, how about you kept the old names and
> > semantics of xwl_window_get() and xwl_window_from_window() but just
> > used the stored private in xwl_window_
On Thu, Aug 10, 2017 at 2:49 PM, Pekka Paalanen wrote:
>
> how does this work when windows are reparented? Does reparenting force
> them to go through the unrealize/realize steps again?
>
I assumed this because it is described this way for the XLib
function XReparentWindow:
https://linux.die.net/
On Sun, 6 Aug 2017 20:03:47 +0200
Roman Gilg wrote:
> Calling xwl_window_from_window means looping through the window ancestor
> chain whenever it is called on a child window or on an automatically
> redirected window.
>
> Since these properties and the potential ancestor's xwl_window are const