LWJGL on Linux says 50 Hertz instead of 60 ?

[quote]Knoppix does not protect application memory space properly, and will attempt to overwrite memory pages in use by programs with user data saved on the RAM drive when the RAM drive gets full. This generally results in an unrecoverable crash or a freeze of the X11 server.
[/quote]
Wow, that’s … stunningly broken. I’m guessing the RAM drive is Knoppix’s thing, and it must be implemented as a kernel mode driver or something. You have to make a serious deliberate effort to screw up memory protection that badly on any modern OS.

[quote]Stop thinking of Linux as a single OS! Ubuntu, Fedora, etc. are OS’s
[/quote]
That is the entire root of the problem. Linux users seem to think they can exist in a dichotomy where “Linux” is just one OS to support, but in reality, it’s about 20 main variants, none of which are really compatible with each other.

Cas :slight_smile:

That is the entire root of the problem. Linux users seem to think they can exist in a dichotomy where “Linux” is just one OS to support, but in reality, it’s about 20 main variants, none of which are really compatible with each other.

Cas :slight_smile:
[/quote]
That is Linux’s strength, and why it gets used in so many different ways and places. I understand your concerns around support, though, but why not just specify support for the main 2 desktop distributions - Ubuntu & derivatives and RedHat / Fedora? For everyone else, caveat emptor! :slight_smile: Those commercial companies that do support Linux software often seem to take this approach.

Yeah but try selling mass-market software to Linux users and doing support for it :confused: Let me assure you it’s not at all fun and costs more to support than we actually make from it.

Cas :slight_smile:

Even something simple, like opening a web page using the default browser, is tricky to do in a cross-distro way on Linux.

Opening the default browser is not hard when you code to gnome and kde, and those use pretty much the same launcher conventions. For everything else you just assume a default. Anyone running lxde on debian with iceweasel can probably figure things out on his own.

Problem is, there’s just about nothing else consistent. Heck gnome 3 probably broke the basic “launch a web browser” action too.

So if it’s neither fun or making you money, directly or indirectly (loss leader, good PR, etc), why do it? And if you do, as I said before, just target any support at the 1 or 2 distros that provide the bulk of your income. Aren’t you doing what you’re criticising some Linux users for, and treating it all as one OS?

Anyway, maybe gone enough OT. I’m under no illusion that Linux is some perfect OS, far from it, but in a thread asking for help on Linux your comment above was a little too much bordering on flaming if you ask me! :persecutioncomplex:

xdg-open? No idea how perfectly it’s implemented across distros but that is what it’s meant for.

As far as I know, ths information can be obtained in SWT:

[quote]display.getPrimaryMonitor().getClientArea()
[/quote]
XRandR can return it.

i thought so too, also I thought this was a standard for “all” Linux’

We are in fact using the output from XRandR to determine available screen resolutions in LWJGL I believe so there’s probably a bit more work to be done parsing the results.

Cas :slight_smile:

AFAIR default refresh rate of compiz is 50hz. New installations are set to auto detect which should normally use the screen refresh rate.
hope that helps

yeah not really. Syncing to 50 (getHertz of the Desktop) has screen tearing, and 60 has it also
looks different depending which one you use, but yeah…

As I said earlier, does this all work OK without compiz enabled?

Try googling compiz vsync and you’ll find loads of stuff about it basically not working, and loads of suggested fixes that probably won’t work! ;D

Not 100% sure right now, will have a look later.
But normally I always disable all compiz stuff right when I install a Linux OS ;D