在不进入 X-Window 的虚拟桌面的情况下从不同的虚拟桌面控制 X-Window？

Question

I'm using the XFCE4 desktop environment under Ubuntu 20.0.4 .

I have several virtual desktops set up, each of which containing one or more applications which are running.

Is there any way I can run an X-Windows-based command from one desktop and have it manipulate a window in a different desktop, without switching desktops?

For example, suppose I have an xterm shell window running in virtual desktop 0, and that I currently am focused in virtual desktop 0.

And suppose I have a text editor window open in virtual desktop 1.

Is there any way for me to remain focused in desktop 0 and to run a command within the xterm shell window which will send text to the text editor window in desktop 1?

I don't want to see desktops shifting back and forth between desktop 0 and desktop 1 while this text is being sent to the text editor. I want to remain focused in desktop 0 for the entire duration of the running of this command.

I know I can use xdotool to send text to another X window, but xdotool only seems to function when the destination window is in the same virtual desktop which currently has the focus. For example, I can do the following with xdotool , but it won't work unless the destination window (referred to by $windowid in the following example) is in my currently viewed virtual desktop:

xdotool type --window $windowid Sample text

What I want is to send text and mouse clicks to windows in desktops that differ from the desktop that I'm currently viewing, and have the windows in those other desktops receive and respond to the text and mouse clicks without any switch to the other desktops taking place.

If necessary, I'm willing to write a program in C, C++, or pretty much any other language in order to implement this functionality.

But I'm wondering: is what I'm trying to do even possible in an X Windows environment?

Thank you very much in advance for any thoughts and suggestions.

Answer 1

Virtual Desktops :

Most X servers have only a single screen. The window manager may virtualize this resource and offer multiple so-called 'virtual desktops', of which only one can be shown on the screen at a time. There is some variation among the features of virtual desktop implementations. There may be a fixed number of desktops, or new ones may be created dynamically. The size of the desktops may be fixed or variable.

Implementation note

There are at least two options for implementing virtual desktops. The first is to use multiple virtual roots and change the current desktop by manipulating the stacking order of the virtual roots.

The second option is to keep all managed windows as children of the root window and unmap the frames of those which are not on the current desktop.

In any case, you should study the Extended Window Manager Hints .
These properties might be of interest to you:

Root Window Properties :

• .NET_SUPPORTED - set by the Window Manager to indicate which hints it supports
• .NET_CLIENT_LIST - all X Windows managed by the Window Manager
• .NET_NUMBER_OF_DESKTOPS - indicate the number of virtual desktops
• .NET_CURRENT_DESKTOP - the index of the current desktop
• .NET_DESKTOP_NAMES - the names of all virtual desktops
• .NET_VIRTUAL_ROOTS - a list of IDs for windows that are acting as virtual root windows

Application Window Properties :

• .NET_WM_DESKTOP - determine the desktop the window is in (or wants to be)
• .NET_WM_STATE - list of hints describing the window state
• .NET_WM_ALLOWED_ACTIONS - list of atoms indicating user operations that the Window Manager supports for this window

---

Xlib :

• Sending Events to Other Applications ( XSendEvent )
• Obtaining Window Properties ( XGetWindowProperty )
• Properties and Atoms ( XInternAtom )
• Obtaining Window Information ( XQueryTree )