JOptionPane buttons don't seem to work.

[Josh Rodrigues]

I'm trying to create a JOptionPane with yes and no options asking whether the person wishes to go into full screen mode or not. When the person clicks on yes, full screen mode should be set, but it's not. If I were to click on no, then it would do the correct thing. When I click on yes, it goes straight to normal screen. I'm not sure why and everything seems correct. Here's the Main class.

package com.xedrox;

import com.xedrox.frame.GameFrame;

import java.awt.Frame;
import javax.swing.JOptionPane;

public class Main {

	public static void main(String[] args) {
		int option = JOptionPane.showConfirmDialog(null, "Would you like to go into fullscreen mode?", "Choose", JOptionPane.YES_NO_OPTION);
		if (option == JOptionPane.YES_OPTION) {
			GameFrame.setFullScreen(true);
		} else if (option == JOptionPane.NO_OPTION) {
			GameFrame.setFullScreen(false);
		}
		new GameFrame();
	}
}

And the GameFrame constructor.

public GameFrame() {
	if (isFullScreen) {
		DisplayMode dM = new DisplayMode(800, 600, 16, DisplayMode.REFRESH_RATE_UNKNOWN);
		runFullScreen(dM);
	} else {
		runNormalScreen();
	}
}

The isFullScreen boolean has a setter and getter for it, so that's where setFullScreen(boolean isFullScreen) comes into play. I don't see anything wrong with it if I'm setting the boolean to make it full screen or not and then setting the display mode for it. Help is appreciated. Thanks.

[Rob Spoor]

Are you sure it's the JOptionPane that isn't working? Try adding some System.out.println statements in your if-else block. My guess is that the error is located elsewhere (like GameFrame.runFullScreen).

[Josh Rodrigues]

I fixed it. Seems like it wouldn't take the setter method:

private static boolean isFullScreen;

public static void setFullScreen(boolean isFullScreen) {
	isFullScreen = isFullScreen;
}

Had to change it to:

private static boolean isFullScreen;

public static void setFullScreen(boolean isFullScreen) {
	GameFrame.isFullScreen = isFullScreen;
}

Thanks anyway.

[Ernest Friedman-Hill]

Josh Rodrigues wrote:I fixed it. Seems like it wouldn't take the setter method:

Great!

Your posts sounds like you're not quite sure why this is. It's because a local variable always hides or "shadows" a member variable of the same name; what your first version is doing is assigning the value of the parameter to the parameter itself. Using the class name -- or "this" in a setter for an instance variable -- is always necessary if you use the same name for the parameter as for the member variable.