XFWM4 Window Problems, Part Deux

[Milosz Derezynski]

Well nevermind, like Jasper said it's not about flaming, just nevermind it
(i don't want to pull myself out of having stirred up an affair though, i
don't expect you to forget everything that i've said, and i still hold
particular opinions about XFWM4 until i've, one day, perhaps, read all of
it's code, just because of paranoid cautiousness), but yeah like Olivier and
Jasper said let's get back on a topic then.

On 11/15/06, Milosz Derezynski <internalerror at gmail.com> wrote:
>
> On 11/15/06, Mike Massonnet <mmassonnet at gmail.com> wrote:
>
> > just reappeared in the taskbar.  If you add gtk_widget_show (GTK_WIDGET
> > (window)) it works... but I know you will refuse this line of code...
>
> Yeah, i could add this line of code, but anyone dare to explain me why i
> need to add this _only_ for XFWM4?
>
> Seriously your project _does_ claim high standards compliance and holds
> this up as one of it's major points/benefits/whatever the right for this is
> (sorry non native english speaker here) and please don't come with this "I
> just work on it in my free time" statement.
>
> So, given the both above statements, anyone care to explain me because of
> which spec (or perhaps brokenness, after all ?) of XFWM4  i need to add
> gtk_widget_show() explicity just for XFWM4
>
> Just btw, if you look at the code of gtk_window_present() in the gtk+
> source tree, it does already call _show() so what is the point here anyway ?
>
>
> I'm riding so much on a minor issue because you boast all the time with
> standards complicance, yet now you suggest me to use a workaround; and if
> it's not a workaround then i'd seriously like to know by which spec this
> behaviour  is defined, and different from all other WMs (and also implying
> that all other WMs are broken or at least not fully compliant).
>
> Anyone? (again)
>
> M.Derezynski
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.xfce.org/pipermail/xfce4-dev/attachments/20061115/b3e6bfa9/attachment.html>