Re: pop up windows

--00000000000013152e062e5a9e01
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I think the difference was probably getting the grab reply. This flushes
the request queue at least to the point of the grab, then waits for the
grab reply to come back, indicating that the grab has started.

The grab_reply is a struct return and thus does not need to be freed. This
is by design.

Wish you success as you go on with X11!

On Mon, Feb 17, 2025 at 3:29=E2=80=AFAM Steven J Abner <[email protected]=
> wrote:

> On Mon, Feb 17 2025 at 01:47:19 AM +0000, Bart Massey <[email protected]>
> wrote:
> > I can verify that the version of your code here
> > https://gist.github.com/BartMassey/f4a904cbefc18045b32f39cfcf1b11f6
>
> Thank you! Love the ~0, bloody brilliant, I never even considered.
> Can say it works 100% like expected. I did a comparison to the original
> change like you first suggested and found the differences of
> underscores, and that sweet ~0 idea :).
> So I can only assume its gcc once again!
>
> Only one last parting question, I really don't know as being semi-new
> to X, on the grab reply, since it is a 'reply *' type, do I need to
> free grab_reply?
>
> I'll look into the virtual console idea another time.
> But thank you, thank Uli, and xcb for the assistance.
> The next demo I mention, you can toss. I'm sure now that it's gcc,
> given my history with it. I would bet the farm that Xlib and XCB work
> as expected.
>
> Steve
>
>
>

--00000000000013152e062e5a9e01
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I think the difference was probably getting the grab =
reply. This flushes the request queue at least to the point of the grab, th=
en waits for the grab reply to come back, indicating that the grab has star=
ted.</div><div><br></div><div>The grab_reply is a struct return and thus do=
es not need to be freed. This is by design.</div><div><br></div><div>Wish y=
ou success as you go on with X11!<br></div></div><br><div class=3D"gmail_qu=
ote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Fe=
b 17, 2025 at 3:29=E2=80=AFAM Steven J Abner &lt;<a href=3D"mailto:pheonix.=
[email protected]">[email protected]</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">On Mon, Feb 17 2025 at 01:47:19 AM +0000, =
Bart Massey &lt;<a href=3D"mailto:[email protected]" target=3D"_blank">bart@c=
s.pdx.edu</a>&gt; <br>
wrote:<br>
&gt; I can verify that the version of your code here <br>
&gt; <a href=3D"https://gist.github.com/BartMassey/f4a904cbefc18045b32f39cf=
cf1b11f6" rel=3D"noreferrer" target=3D"_blank">https://gist.github.com/Bart=
Massey/f4a904cbefc18045b32f39cfcf1b11f6</a><br>
<br>
Thank you! Love the ~0, bloody brilliant, I never even considered.<br>
Can say it works 100% like expected. I did a comparison to the original <br=
>
change like you first suggested and found the differences of <br>
underscores, and that sweet ~0 idea :).<br>
So I can only assume its gcc once again!<br>
<br>
Only one last parting question, I really don&#39;t know as being semi-new <=
br>
to X, on the grab reply, since it is a &#39;reply *&#39; type, do I need to=
 <br>
free grab_reply?<br>
<br>
I&#39;ll look into the virtual console idea another time.<br>
But thank you, thank Uli, and xcb for the assistance.<br>
The next demo I mention, you can toss. I&#39;m sure now that it&#39;s gcc, =
<br>
given my history with it. I would bet the farm that Xlib and XCB work <br>
as expected.<br>
<br>
Steve<br>
<br>
<br>
</blockquote></div>

--00000000000013152e062e5a9e01--