Problem with some fullscreen applications

[joewing]

JWM does not properly handle some fullscreen applications (milkytracker, perhaps others).
For milkytracker, the application will take over the screen briefly, but then go back into a window. JWM never detects that the application is attempting to be a full-screen client.

[scsijon]

Hi, joe i'm back for now.
have a look at this for another report
http://www.murga-linux.com/puppy/viewtopic.php?t=83949&start=191

[joewing]

As far as I can tell, the issue here is that the programs in question aren't using a standard way of entering full screen mode. Apparently JWM isn't alone as far as being able to handle this (openbox and fluxbox show the same problems).

[JakeSFR]

Hi Joe & Scsijon

I did not have GitHub account at a time when I was reporting this issue @murga forum, but now I can interact directly. :)

Joe: Openbox, IceWM and Fluxbox somehow can handle correctly xrick and milkytracker in fullscreen mode for me - re-tested for sure, right now, using Slacko-5.6 in VirtualBox.
In which distro did you try it? Perhaps it's partially also a distro-specific issue..?

BTW, I just recalled that there is one condition, where those apps are able to enter the fullscreen mode properly in JWM - if screen resolution is set to the lowest available, please see:
http://www.murga-linux.com/puppy/viewtopic.php?p=650146#650146
Hope it will help somehow.

Thank you &
Greetings!

[joewing]

With Openbox 3.5.2 and Fluxbox 1.3.5 on a Debian system, fullscreen doesn't seem to work.
I think the problem is with the way the SDL library does fullscreen. JWM only supports the EWMH method, which, as far as I know, is the only standard way to do fullscreen in X11. It would appear that the SDL library does not use that method. I have SDL 1.2, so hopefully newer versions of SDL do this correctly (I think newer versions give the program a choice between "legacy" and the EWMH method).

If I knew of an easy way to make it work, I'd do it, but supporting non-standard and undocumented things like this can be a pain.

[JakeSFR]

Yeah, it seems to have more to do with SDL than JWM, indeed.
I didn't notice that it (SDL) is the common factor in all those apps...
Anyway, I found this today;
http://lists.suckless.org/dev/1201/10563.html
Although, later in that thread, the author does report that this solution doesn't work on his another, x86_64 box/system and provides different patch (for DWM), I did apply it (to SDL-1.2.15) and the problem, at least in 32bit Slacko, is gone. :)

Greetings!

[joewing]

I have no plans to fix this, so I'm marking it as such. If SDL decides to do something to inform JWM of it intentions, this would be worth revisiting.