improve processClick, combinations, InputEventManager

[stolsky]

TODO

InteractionProcessor

• create InteractionProcessor to handle all interactions
• move/include processClick into InteractionProcessor
• Combinations and Commands will be to classes exclusively accessed by InteractionProcesser
• two method interface: "processInteraction", "getResults"
• InteractionProcesser stores results until they are requested
• interactionProperties must include the id/reference of the State from which "processInteraction" was fired

InputEventManager

• rename InputEventManager to something like "EventStore"
• two method interface: "addEvent", "getLastEvent"

State's update and render

• State's update method gets last event via getLastEvent, prepares via inputHandler and fires the processInteraction
• State's render method retrieves the results of the InteractionProcesser via getResults making addDataQueue and pushQueueData obsolete and simplifies render method a bit