Campbell Ritchie wrote:You will find the explanation here, along with a possible solution. If you search my posts for Scanner and nextLine you will find a different solution, but there was a serious error in the first version.
Thanks Ritchie for point that out!
However, I read through it a couple of times and I'm starting to think this is a good solution for if I was calling .nextLine() after I did a .nextAnythingElse();
I'm trying to call .nextLine() before I do .nextAnythingElse(); Never really had a issue with calling .nextLine() before doing .nextInt() before.