I have my Java game I wanted to put on my chromebook. It works at 640 x 480 resolution and then adjusts the screen mode using device.getDisplayModes(). This works fine on most monitors but for some reason fails on my chromebook. The above method tells me it does have that resolution.
The exclusive fullscreen mode of AWT has been broken under GNU Linux for several years. Most of the time, depending on the window manager, I still get the task bar above the fullscreen window.
How does it fail? Please can you give us more details?
It wouldn’t bother me too much having a small task bar - it’s obviously not perfect but it’s better than the little 640 x 480 window I’m getting at the moment. I should of said what’s currently happening shouldn’t I :
to get the full screen which works on most windows screens but then I usually also call the jar with the following which tends to make it work for nearly all the windows screens I’ve tried (even my own 24" wide screen). It doesn’t seem to have any effect on Linux.
/**
* Value of the bit depth if multiple bit depths are supported in this
* display mode.
* @see #getBitDepth
*/
public final static int BIT_DEPTH_MULTI = -1;
Riven’s suggestion is nice and you should do the same for the refresh rate instead of picking 60. Some desktop managers badly support the modification of the refresh rate, they leave your desktop with tons of straight lines, I thought it was a bug of a Java library but I was wrong. I still reproduce it with KDE.