Argolance wrote:As soon as clicked on desktop ('root window') to display MENUS, Pinboard doesn't work properly anymore: desktop shortcuts, drives icons, files/directories listed inside Rox windows don't react to mouse events.
Argolance,
I have attached a modified version of /usr/local/apps/ROX-Filer/AppRun which may get you going.
Back-up your original, then gunzip and copy this one to /usr/local/apps/ROX-Filer/AppRun, and restart the X server.
Please note that this has been briefly tested OK in Racy-5.2.2, so it is likely to work in Wary-5.2.2, but I can make no guarantees.
This may be more of a work-around than a true fix. Or it may be all that is needed. Either way, it should point you in the right direction.
The problem results from a change to GDK. Until sometime around 2009, GDK made an X11 window for each GDK window. That is not necessarily the case anymore. Now GDK makes what it calls "client-side windows". So now, an application that was designed to interact with an X11 window corresponding to one of its GDK windows may be disappointed to find that no such X11 window exists.
I think something like that is happening with ROX-Filer.
One way around that problem is to set an environmental variable, GDK_NATIVE_WINDOWS, true. Then GDK will create a native X11 window for each GDK window, making the application happy again.
This is all that my modified /usr/local/apps/ROX-Filer/AppRun does.
There is a potential downside to this: An application that uses "client-side windows" may have a speed advantage, and create windows slower if GDK_NATIVE_WINDOWS is set true for it.
I have not yet determined if setting GDK_NATIVE_WINDOWS=true will affect only ROX-Filer, or will affect every GTK/GDK application it opens.
The reason that I set it in /usr/local/apps/ROX-Filer/AppRun instead of /root/.xinitrc or earlier, is to, hopefully, limit its effect to ROX-Filer. But it is certainly possible that, once set, all GTK/GDK applications will be affected. I
have noticed that when I use ROX-Filer to run urxvt, GDK_NATIVE_WINDOWS does not appear in the environment. So maybe I got lucky.
Admittedly, I have more success predicting the weather than the mysteries of GDK and GTK behavior.
I need to test some with GTK/GDK apps, but I thought that I would send this off to you so that you can try it out, rather than waiting for me to get around to doing more tests.
Let me know if this seems to slow anything down. Of course, unless an application has been optimized for "client-side windows", it should not run any slower than it did in early 2009.