OOTP Developments Forums - View Single Post

KBLover · 07-11-2006, 12:20 PM

Admittedly, I'm using a test file from an on-line league I'm in and something happened where the managers didn't show up and the one that did was passworded, and I don't know the password.

That's not the problem I'm mentioning here, though. The problem is that I couldn't quit the game. I had to force windows to close it down. Otherwise, I'd be stuck looking at that screen with nothing to do.

If this is by design, then I propose that it not be so. Clicking the x at the top-right should always bring up a "quit the game now?" box and allow the user to exit the game if desired.

This wasn't the only place I noticed this behavior. Other times, the "do you want to quit" dialog would show up after moving to a certain screen. I can't remember where I was, but I do remember it happening more than a few times until I got used to the interface acting that way.

But I believe it shouldn't act that way, and am putting it here in case it's a bug in the mix instead of a intended behavior.

07-11-2006, 12:20 PM	#1
KBLover All Star Reserve Join Date: Aug 2002 Posts: 580	Can't quit when you want? Admittedly, I'm using a test file from an on-line league I'm in and something happened where the managers didn't show up and the one that did was passworded, and I don't know the password. That's not the problem I'm mentioning here, though. The problem is that I couldn't quit the game. I had to force windows to close it down. Otherwise, I'd be stuck looking at that screen with nothing to do. If this is by design, then I propose that it not be so. Clicking the x at the top-right should always bring up a "quit the game now?" box and allow the user to exit the game if desired. This wasn't the only place I noticed this behavior. Other times, the "do you want to quit" dialog would show up after moving to a certain screen. I can't remember where I was, but I do remember it happening more than a few times until I got used to the interface acting that way. But I believe it shouldn't act that way, and am putting it here in case it's a bug in the mix instead of a intended behavior.