Ogre Forums

xavier wrote: Also, what do you mean by "WinAPI mouse system"?

igorvlassov wrote:

xavier wrote: Also, what do you mean by "WinAPI mouse system"?

Sorry for late reply.
Classical WM_MOUSE* Windows messages processing.

xavier wrote:

igorvlassov wrote:

xavier wrote: Also, what do you mean by "WinAPI mouse system"?

Sorry for late reply.
Classical WM_MOUSE* Windows messages processing.

You process them the same as you do for any other Win32 application. The problem you will run into with Ogre, is that the Win32 message dispatching is done in an internal class (WindowEventUtilities) so you'll probably want to make your own Win32 window and embed the Ogre render window in that, so that you have complete control over the message processing. Note, however, what sorts of things the Ogre code does in various scenarios, because you'll need to duplicate it.

Of course, you can always subclass the window class and call the Ogre WndProc when yours is done.

Azgur wrote:What's wrong with IOS?

Yes that is I wondered: entry point for my callback message processing func and where to put dispatchmessage etc. stuff.

// A global to store ogre's winproc. 
// I could just use WindowEventUtilities::_WndProc directly, but this way preserves chaining in case something else did this first.
WNDPROC g_ogreWinProc = NULL;

// Your winproc code, which calls ogre's one when finished.
LRESULT APIENTRY SubclassProc(HWND hwnd, UINT uMsg, WPARAM wParam, LPARAM lParam)
{
	switch(uMsg)
	{
		// handle your WM_**** stuff here
	}
	return CallWindowProc(g_ogreWinProc, hwnd, uMsg, wParam, lParam);
}


// insert this code somewhere in your initialisation:
HWND hwnd;
m_window->getCustomAttribute("WINDOW", (void*)&hwnd);
g_ogreWinProc = (WNDPROC) SetWindowLong(hwnd, GWL_WNDPROC, (LONG) SubclassProc); 

xavier wrote:

igorvlassov wrote:

xavier wrote: Also, what do you mean by "WinAPI mouse system"?

Sorry for late reply.
Classical WM_MOUSE* Windows messages processing.

You process them the same as you do for any other Win32 application. The problem you will run into with Ogre, is that the Win32 message dispatching is done in an internal class (WindowEventUtilities) so you'll probably want to make your own Win32 window and embed the Ogre render window in that, so that you have complete control over the message processing. Note, however, what sorts of things the Ogre code does in various scenarios, because you'll need to duplicate it.

Of course, you can always subclass the window class and call the Ogre WndProc when yours is done.

igorvlassov wrote:Yes that is I wondered: entry point for my callback message processing func and where to put dispatchmessage etc. stuff.

Kojack wrote:I just wrote some code

Kojack wrote:Yes that is I wondered: entry point for my callback message processing func and where to put dispatchmessage etc. stuff.

I just wrote some code to intercept messages before the ogre winproc about an hour ago. Here's what I did:
(Note: this was part of a quick hacked together test for several random things I'm working on, so ignore crappiness)

Code: Select all

// A global to store ogre's winproc. 
// I could just use WindowEventUtilities::_WndProc directly, but this way preserves chaining in case something else did this first.
WNDPROC g_ogreWinProc = NULL;

// Your winproc code, which calls ogre's one when finished.
LRESULT APIENTRY SubclassProc(HWND hwnd, UINT uMsg, WPARAM wParam, LPARAM lParam)
{
	switch(uMsg)
	{
		// handle your WM_**** stuff here
	}
	return CallWindowProc(g_ogreWinProc, hwnd, uMsg, wParam, lParam);
}


// insert this code somewhere in your initialisation:
HWND hwnd;
m_window->getCustomAttribute("WINDOW", (void*)&hwnd);
g_ogreWinProc = (WNDPROC) SetWindowLong(hwnd, GWL_WNDPROC, (LONG) SubclassProc); 

Now you get to handle your stuff and ogre still handles stuff like window move events, etc. At least it does for me so far.

\Escape_Main.cpp|383|error: invalid use of member (did you forget the '&' ?)|

ogreWndProc = (WNDPROC) SetWindowLongA(hwnd, GWL_WNDPROC,(LONG) EscapeWndProc);