dimbor-ru

> However, what should we do about this in nx-libs? Maybe mentioning those links in the readme would be a good start. It would be nice. It is for this...

You have destroyed almost all my dreams. Then in my free time I'll try to at least limit the transmitted shadow area. Because usually one application with one own window...

Wow! -R jointly -S really worked. But they work strange too. Shadow client open two windows. First is full black and don't operate (root window for rootless?). Second named 'Unnamed'...

@sunweaver: I am flattered by the assessment of my modest old work. Of course, our further interaction will occur in the form of my pool requests. On the other hand,...

I'm not an employee of Ethersoft, I only advise them sometimes. Therefore, I can't speak on their behalf.

However, I was prompted with a promising project: [usbip-win](https://github.com/cezanne/usbip-win) But I'm not so friendly with MSVS for experimenting with it. While he is waiting for brave guys.

Yes, I assumed that changing the CHANNEL_MASK to 0x0F would violate the nx-protocol in some way. However, when tested, it worked. Naturally, all possible modes were not tested. Please note...

Exactly. It is this problem that is being described. Native wm controls are left for contrast only.

Here's another way to reproduce the problem: In the x terminal rootless session try to operate youreself window by [xclimsg](https://github.com/phillbush/xclimsg.git).

Firstly, the fix is still only my fantasy ;) For example, the maximization case. Simulation done if command `xclimsg -m -w _NET_WM_STATE 1 _NET_WM_STATE_MAXIMIZED_VERT _NET_WM_STATE_MAXIMIZED_HORZ` starting on client of real...