Stuck in a bad loop

[Nadian]

Hello all, newbie here, trying to write a very simple program which lets me write in a question, three possible answers, then stores them to file. Mostly working fine but for one strange thing. On the first run through i can enter question and answers, BUT when it loops after I have entered 'true' to continue entering questions it skips past the enter new question input and goes straight to the answer input stage, i cannot work out why?

import java.util.Scanner;
import java.io.File;
import java.io.FileNotFoundException;
import java.io.PrintStream;
import static java.lang.System.in;
import static java.lang.System.out;

public class Teacher {
	public static void main(String args[])
		throws FileNotFoundException{
		Scanner input=new Scanner(in);
		PrintStream output=new PrintStream("revisionquestions.txt");
		PrintStream ans=new PrintStream("revisionanswers.txt");
		int questionId=0;
		int answerId;
		String answers;
		String question;
		boolean yes=true;
   	for (;yes;){
  	out.print("Enter question: ");
  	question=input.nextLine();
	output.println(question);
  		for (int x=0;x<3;x++){
  		out.print("Enter answer: ");
  		answers=input.nextLine();    /*problen here on second loop*/
  		ans.println(answers);
  		}
  	questionId++;
  	out.print("question ID ");
  	out.println(questionId);
  	out.print(" Do you wish to add another question:(true or false) ");
  	yes=input.nextBoolean();
	}
  out.print("fin");
  }
}

edited post - removed attachment on advice

[KevinWorkman]

To post code, make sure you use the CODE tags to preserve formatting. Not many people are going to be willing to download your attached file.

[KevinWorkman]

Scanner.nextBoolean() does not scan past the current line, so it doesn't absorb the last "enter" pressed by the user after typing true.

Then when you get back to question = input.nextLine(), that absorbs that last "enter", giving you an empty String for the value of question.

You could simply call input.nextLine after you call input.nextBoolean().

[Nadian]

Scanner.nextBoolean() does not scan past the current line, so it doesn't absorb the last "enter" pressed by the user after typing true.

Then when you get back to question = input.nextLine(), that absorbs that last "enter", giving you an empty String for the value of question.

You could simply call input.nextLine after you call input.nextBoolean().

thanks I hadn't understood that scanner missed the enter like that, but it makes sense as it acts like I've pressed enter twice..

[Nadian]

thanks for that, i hadn't understood how scanner misses the enter, it makes sense as it was like I'd pressed enter twice.

[KevinWorkman]

Think about it this way: what if you had a whole row of booleans you wanted to read in via a Scanner? You would call Scanner.nextBoolean() for each one, which wouldn't read in the entire line, just the very next boolean.

Another way to do this would be to use nextLine() instead of nextBoolean(), then convert the String returned from nextLine() into a boolean.

[Nadian]

would reading it as a string then convert to boolean be typecasting? i.e
new boolean=Boolean.parseBoolean(string),

[KevinWorkman]

would reading it as a string then convert to boolean be typecasting? i.e
new boolean=Boolean.parseBoolean(string),

What happened when you tried that?

Depending on your definition of typecasting, that could be considered typecasting.

Although, you are mixing the syntax up a bit. You wouldn't need the new keyword if you're just trying to reference the Boolean returned from Boolean.parseBoolean() or Boolean.valueOf().

[Nadian]

I didn't try it as your solution has worked, and I'm not currently trying to read from several booleans in a line, but i may be back for help later when i'm trying to read my questions and answers back from the text files

[KevinWorkman]

The parseBoolean() or valueOf() approaches might be a better way to go, I'm not sure. Either way it wouldn't hurt to try :p

I only provided the example of reading several booleans in a line to show why nextBoolean() worked the way it did.

I'm glad you got it working though!