I have attached a modified version of /usr/local/apps/ROX-Filer/AppRun which may get you going.

This works great and doesn't seem to slow anything down (let me further watch!)

Quote:

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.

Is it to say that Lucid and Quirky have got GDK version older than Wary and Racy?
Very strange indeed!

There is a problem with ffmpeg :
ffmpeg -i 'http://api.jamendo.com/get2/stream/track/redirect/?streamencoding=mp31&id=859750'
gives : No such file or directory
Is it because http protocol is not included in compilation ( --disable-network) ?

The empty opt directory is not an artifact or a bug. Some third party applications choose to install to this directory rather than /local and in my case I see that qt4 is installed in the opt directory.

Monsie

I know this already but in wary, it's empty by default, so should we keep empty folders ?

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.

I found some time to look into this further.

Apparently it works the way I hoped that it would. By setting GDK_NATIVE_WINDOWS in /usr/local/apps/ROX-Filer/AppRun instead of earlier, it is affecting only ROX-Filer, not applications started by ROX-Filer. So other GTK/GDK applications will continue to use "client-side windows", and should not suffer any loss of speed when creating windows.

The effect of GDK_NATIVE_WINDOWS can be seen with help from xwininfo.

With the unmodified ROX-Filer and libgdk-x11-2.0.so.0.2400.8, running

Code:

xwininfo -children

and clicking on the pinboard (desktop), will result in something like this:

There is only one child despite all of those buttons. So this application is still using "client-side windows", even though it was launched from ROX-Filer, which is using native X windows.

Apparently, ROX-Filer does not export GDK_NATIVE_WINDOWS to the applications that it starts. So even if that variable is exported to the environment before X is started, it will not pass it along.

But if you launch an application with the JWM menu, or from a terminal that was launched with the JWM menu, GDK_NATIVE_WINDOWS will be exported to the application.

For instance, if instead of setting GDK_NATIVE WINDOWS=true in /usr/local/apps/ROX-Filer/AppRun it was exported to the environment before starting X, it would affect all GTK/GDK applications launched with the JWM menu, and the xwininfo report for "Puppy Setup" would look like this:

Now it shows a native X window for each button, plus that mystery one-pixel window. In the case of "Puppy Setup" I don't think that this would cause any problems, but this example shows that exporting GDK_NATIVE_WINDOWS=true before starting X could affect any GTK/GDK application, which could cause performance issues with some applications. It is safer to just set it for ROX-Filer, as done by the modified /usr/local/apps/ROX-Filer/AppRun.

Bottom line: It looks like the modified /usr/local/apps/ROX-Filer/AppRun should not affect anything other than ROX-Filer itself.

Barry,
In the new "testing" version of lucid pup 5.2.8, I addressed issues that keep frustrating new users of pupdial. I submit them for consideration to be included in woof/wary/racy.

When instructed to omit the login ID and password for wireless modem connections, new users encounter the error message from wvdial complaining about the absence of those items. The remedy is to select "Stupid mode", which is not something novices could infer by themselves. To eliminate that booby trap, I made these changes (copied for my original posting):

- In the pupdial modem dialer, changed the label of the "Stupid mode" checkbox to "Bypass log-in", which is what it does -- many new users get frustrated when they delete the login and password default, following their ISP's instructions, and cannot connect, only to be advised to turn on Stupid mode, which is not at all obvious.
- In pupdial, also ensured that a login and password are passed to wvdial (which requires them) by filling the empty fields with the default values.

Apparently it works the way I hoped that it would. By setting GDK_NATIVE_WINDOWS in /usr/local/apps/ROX-Filer/AppRun instead of earlier, it is affecting only ROX-Filer, not applications started by ROX-Filer. So other GTK/GDK applications will continue to use "client-side windows", and should not suffer any loss of speed when creating windows.

Thank you a lot for test, explanations and solution: I feel much better now!
On my side, I think I can say that this doesn't slow anything down.

Barry,
In the new "testing" version of lucid pup 5.2.8, I addressed issues that keep frustrating new users of pupdial. I submit them for consideration to be included in woof/wary/racy.

When instructed to omit the login ID and password for wireless modem connections, new users encounter the error message from wvdial complaining about the absence of those items. The remedy is to select "Stupid mode", which is not something novices could infer by themselves. To eliminate that booby trap, I made these changes (copied for my original posting):

- In the pupdial modem dialer, changed the label of the "Stupid mode" checkbox to "Bypass log-in", which is what it does -- many new users get frustrated when they delete the login and password default, following their ISP's instructions, and cannot connect, only to be advised to turn on Stupid mode, which is not at all obvious.
- In pupdial, also ensured that a login and password are passed to wvdial (which requires them) by filling the empty fields with the default values.

Trying to recall back when I last tried GDK_NATIVE_WINDOWS=true, I think that I put it as a prefix to the running of rox in /root/.xinitrc.

I was using it back then and noticed lots of gdk critical error reports on stderr, although I don't recall if anything actually crashed.

Anyway, I reckon that I will put your solution into the rox-filer PET pkg -- in the 'common' repo, the PET that most x86 Puppy builds use.

Disaster!

Now I recall what went wrong before, because it has happened again. I was scrolling down a fairly large directory, when the scrollbar froze. The entire rox window froze, but other rox window still work.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum