Allowing mouse input to trigger key bindings while the cursor is on (TGEA).

The problem is, when you've got the cursor on ( cursorOn(); ) all mouse input goes to the gui and isn't used to trigger the key bindings. In the source code, ActionMap::handleEvent(event) is used to trigger functions in your key mappings (default.bind.cs). But the way it's set up, if the cursor is on, the gui will take that input with Canvas->processInputEvent(event) and not allow handleEvent to use your mouse input. This code in main.cpp should give you the general idea:

PROFILE_START(ProcessInputEvent);
   if (!ActionMap::handleEventGlobal(event))
   {

      // Other input consumers here...
      if (!(Canvas && Canvas->processInputEvent(event)))
	  ActionMap::handleEvent(event);
       
   }
   PROFILE_END();

...but all we're going to do is tell this section not to handle ANY mouse click events. We'll handle that somewhere else. we're not going to change the keyboard events because we don't want to be typing in a text box for example and having our character run forward every time we type a "w". So make it look like this (added code is in bold):

PROFILE_START(ProcessInputEvent);
   if (!ActionMap::handleEventGlobal(event))
   {
		//
      // Other input consumers here...
      if (!(Canvas && Canvas->processInputEvent(event)))
      [b]if (event->deviceType != MouseDeviceType)//if it's NOT a mouse click event[/b]
	  ActionMap::handleEvent(event);
       
   }
   PROFILE_END();

In gameInterface.cpp there's a section that looks like this (the places where I added code are in bold). I added tEvent so i can find out if the event is a mouse click or keyboard stroke. We only want handleevent to activate if it's a mouse click event:

[b]InputEvent *tEvent = (InputEvent *)event; [/b]

   switch(event->type)
   {
      case PacketReceiveEventType:
         processPacketReceiveEvent((PacketReceiveEvent *) event);
         break;
      case MouseMoveEventType:
         processMouseMoveEvent((MouseMoveEvent *) event);
         break;
      case InputEventType:
        [b] if (tEvent->deviceType == MouseDeviceType)//if its a mouse click event
         ActionMap::handleEvent((InputEvent *) event);//activate keymap[/b]
         processInputEvent((InputEvent *) event);
         break;
      case QuitEventType:
         processQuitEvent();
         break;
      case TimeEventType:
         processTimeEvent((TimeEvent *) event);
         break;
      case ConsoleEventType:
         processConsoleEvent((ConsoleEvent *) event);
         break;
      case ConnectedAcceptEventType:
         processConnectedAcceptEvent( (ConnectedAcceptEvent *) event );
         break;
      case ConnectedReceiveEventType:
         processConnectedReceiveEvent( (ConnectedReceiveEvent *) event );
         break;
      case ConnectedNotifyEventType:
         processConnectedNotifyEvent( (ConnectedNotifyEvent *) event );
         break;
   }
.... etc

When that line is put there, your mouse button bindings will work with the cursor on or off... But mouse movements are handled elsewhere. In order to make this work, a mousemoveevent needs to be converted into an input event so it can be sent with handleevent. I added new code in processMouseMoveEvent to keep things simple. You should see a call for processMouseMoveEvent in the above code. Go to the definition of processMouseMoveEvent in guiCanvas.cpp and turn it into this:

void GuiCanvas::processMouseMoveEvent(const MouseMoveEvent *event)
{
	InputEvent iEvent;
	iEvent.deviceType = MouseDeviceType;
	iEvent.modifier = event->modifier;
	iEvent.action = SI_MOVE;
	iEvent.deviceInst = 0;

	iEvent.objType = SI_XAXIS;
	iEvent.fValue = event->xPos - cursorPt.x;
	processInputEvent(&iEvent);
	ActionMap::handleEvent(&iEvent);

	iEvent.objType = SI_YAXIS;
	iEvent.fValue = event->yPos - cursorPt.y;
	processInputEvent(&iEvent);
	ActionMap::handleEvent(&iEvent);
}

You'll also need to make sure to include actionMap.h at the top of guiCanvas.cpp and gameInterface.cpp. my include line looks like this: #include "sim/actionMap.h"

I didn't do anything with the z axis (mouse wheel), but if you need to, you should be able to figure it out from this example. Rebuild, and now your mouse will trigger your key mappings along with the gui when your cursor is on.

Keep in mind that your cursor will now activate your mappings while in gui mode, so for example if your game moves your player when you click on the ground, your character will still move to the area underneath a gui menu if you click on the menu. There's ways around that problem, but now you're forewarned.

Like I said, this is my first resource and I'm still learning torque so feedback is welcome :)