Jump to content

View more

Image of the Day

Inventory ! Va falloir trouver une autre couleur pour le cadre D: #AzTroScreenshot #screenshotsaturday https://t.co/PvxhGL7cOH
IOTD | Top Screenshots

The latest, straight to your Inbox.

Subscribe to GameDev.net Direct to receive the latest updates and exclusive content.

Sign up now

Unregistering Raw Input

4: Adsense

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
3 replies to this topic

#1 Hedanito   Members   


Posted 17 August 2012 - 09:38 AM

So I am changing my input system from directinput to raw input, because I want multi mouse/keyboard support.
I've figured out most parts, but I have trouble getting one major part right.

I have 2 classes, an inputmanager and a window class.
The window class just creates a basic frame in which I can draw etc.
The inputmanager, as the name suggests, manages all the input.
Instances of the window class can be registered at the inputmanager, which will then register the raw input devices, and peek for input messages every frame.
A requirement for this is that the window class ignores all WM_INPUT messages (does not remove them from the message que).
If it does not do this, input messages sometimes leak through between the inputmanager peeking for messages and the processing of the window message que, even if they are called right after each other.
This is not acceptable for a game engine, so the window just ignores the WM_INPUT messages.

This is works fine and all, until I tell the input manager to stop tracking input on that window.
The window is still ignoring all the WM_INPUT messages, while the inputmanager does not pop them anymore.
So basically the message queue just starts filling up with WM_INPUT messages and no one takes them out.

Now the best solution of course would be to just unregister the devices so that they stop sending WM_INPUT messages and everything acts just like it did before I registered them, but this does not seem to be possible.
I am unable to find a function that does this.
The closest thing I could find was RIDEV_REMOVE, but this does not do anything related to the window, and I am uncertain how much it actually affects.

So what I need is:
Something to unregister raw input devices.
Some other solution to this problem that doesn't mess up the architecture without any leaks.

A requirement is that the window does not have to know if it is being tracked at the moment.

OS: Windows
Language: C++

Edited by Hedanito, 17 August 2012 - 09:38 AM.

#2 krippy2k8   Members   


Posted 17 August 2012 - 01:16 PM

RIDEV_REMOVE is what you need. Call RegisterRawInputDevices with RIDEV_REMOVE and a NULL hwndTarget.

You can only register one window per device, per application, for raw input anyway. So when you remove it, it's global for the application and not just a specific window.

Edited by krippy2k8, 17 August 2012 - 01:17 PM.

#3 Hedanito   Members   


Posted 18 August 2012 - 12:59 PM

So when having multiple window frames, I'll have to register every time the window focus changes?

#4 krippy2k8   Members   


Posted 18 August 2012 - 08:37 PM

If you register your devices with the hwndTarget as NULL, the input messages will be sent to whichever window has keyboard focus.

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.