SYNC: how to hijack the hijacker

[Steven J Abner]

I am having problems again using xcb because of those things called 
window managers. I am still thinking of ways to even circumvent SYNC 
since I want an application to use xcb without having to load every os 
to figure out wm oddities workarounds. I am aware that gdk can somehow 
beat the system, but a glance at their code looks like they use SYNC, 
but how?.
Is there a way to get signals from the X Server instead of the window 
managers. A small test to even attempt SYNC usage, I found that one 
wont deliver even client messages for sync and one would. PS, I still 
dont understand SYNC but if cant use, why learn.
I've included 2 pngs. One using my application that proves smooth 
resizing can be done. The other showing the normal window as one 
expects to see. The application one uses the outlines much like window 
edges, or what gtk calls "paned grips"? And yes cursor changes to 
indicate directionals of pull/push. Application one generates 
configure/expose events
but configure goes direct to each object(text/label/text), not through 
the server.
I've considered using query pointer to weed out old configure signals 
with maybe a display lock, a ungrab/grab maybe?. Query pointer does 
great with old DND signals, so figure it could work here?
Currently the resizing of a window, I can sometimes move to 1/2 the 
window, wait 2-3 seconds before resize will occur (window and content).
In my window within a window, it works 100% of the time, resizing from 
any size or any of the gravities.
Steve

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot_window.png
Type: image/png
Size: 52806 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/xcb/attachments/20250201/a172e01f/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot_resize.png
Type: image/png
Size: 64310 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/xcb/attachments/20250201/a172e01f/attachment-0003.png>