Since the console object is only used inside consoleMode, it might as well reside in consoleMode rather than being a singleton.
Yeah, I think pausing could be implemented as a mode. I think pausing currently will require pausing/stopping the server thread as well as altering the inputs. I think it would be best to first make sure we have separated the map loading and gameplay stuff so it doesn't start automatically on the application start first.
My idea was that the modes would be classes managing the objects that were unique to the current mode. Then modes could optionally have an object that does the actual input handling, which would be a different class depending on the mode. Though the way it's done now might be a better approach. The name would depend on whether the mode objects should contain other objects that are unique to the mode, e.g GameMap. Or is there another approach here that is better?
- {l Code}: {l Select All Code}
second I think the main program or ODapplication control should be more sophisticated , at least having several modes is too poor....
I'm not quite sure what you mean by this, what do you propose we do here?
NOTE: I will be away until Sunday evening, I can't reply more until then.