Yes, It was exactly the problem, the different WM didn't update the configuration without resizing.
Am 19.05.2015 um 10:50 schrieb Ulrich Sibiller:
On Tue, May 19, 2015 at 10:09 AM, Oleksandr Shneyder <o.shneyder@phoca-gmbh.de> wrote:
Imagine that you have agent window in the middle of two screens. Window size is 1024x768. You current displays configuration in that case is: left-512x768, right-512x768. Imagine, that you moved your window 100 px left. Now your displays configuration is: left-612x768, right-412x768. But from the view of x2goagent nothing is changed, agent has no idea about the display geometry on the client side. This is why client updating xinerama.conf and resizing a window to apply new settings. I hope it's understandable.
Yes, it is understandable. But this only relevant for xinerama information. And that information is coming from the config file (which is correctly updated in this case by x2goclient). So I still do not see why x2goagent needs to be triggered in any way. If a software needs to know the xinerama setup it issues a XineramaQueryScreens() request. This is intercepted by the libNX_xinerama.so and answered with the information from the config file. The x2goagent does not even see this request and thus does noot need to be updated. The only problem that your code solves might be the window manager in the session that caches xinerama information.
Do you have a use case that does not work without the resize?
Uli
--
Oleksandr Shneyder | Email: o.shneyder@phoca-gmbh.de phoca GmbH | Tel. : 0911 - 14870374 0 Ludwig-Feuerbach-str. 18 | Fax. : 0911 - 14870374 9 D-90489 Nürnberg | Mobil: 0163 - 49 64 461
Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder