• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
fir

raw input troubles

4 posts in this topic

I was writing some pices in winapi's raw input 

It seem to working though I am not sure how reliable (unfaliable) it is

(and if it will be working on all systems machines etc, this is a bit worry)

 

also there appears many question, the one is 

 

I would like to use my first (I mean normal/base mouse) in old way,

it is processint WM_MOUSEMOVE etc and moving arrow cursor, only the

secondary mouse I need processing by raw_input (primary can stay untouched by rawinput), the problem is

 

1) how can i be sure which mouse detected by rawinput is the

secondary?

 

2) the second mouse moves also my arrow -cursor, if I disable 

it by RIDEV_NOLEGACY then both are not moving cursor (it bacame hourglass) and it is wrong too

 

think maybe i should setup it a bit differently my setrup rawinput function is like

 
void SetupRawInput()
{
 
    static RAWINPUTDEVICE Rid[1];
 
    Rid[0].usUsagePage = 0x01;
    Rid[0].usUsage = 0x02;
    Rid[0].dwFlags = 0;     //   Rid[0].dwFlags =  RIDEV_NOLEGACY;   /
    Rid[0].hwndTarget = NULL;
 
     int r = RegisterRawInputDevices( Rid, 1, sizeof(Rid[0]) );
 
    if (!r)  ERROR_EXIT("raw input register fail");
 
}
 

how to resolve this issueas andmake it work? tnx

Edited by fir
0

Share this post


Link to post
Share on other sites

It seem to working though I am not sure how reliable (unfaliable) it is
(and if it will be working on all systems machines etc, this is a bit worry)
I've been using raw input for a while. I started using it... I think a year before D3D10 was announced. Reliability depends on the specific input device, some are just not so good but mouse support is solid.

 

 


how can i be sure which mouse detected by rawinput is the secondary?

RawInput will detect all devices, whatever you use them or not is your business. Enumerate them and use GetRawInputDeviceInfo, it gives you a blob of device-specific data, but it has a well known format for mice and it has a device index dwId.

It's a while since I've used that. If memory serves, the first mouse is a virtual mouse obtained by coalescing input from all mice, then the real mouse device follows. But I'd suggest to check that more accurately before going on.

 

 

the second mouse moves also my arrow -cursor, if I disable it by RIDEV_NOLEGACY then both are not moving cursor (it bacame hourglass) and it is wrong too

Unfortunately as far as I recall, windows pointer ballistics are always computed using all the mice connected. I'm following the thread in case someone posts a solution.

Edited by Krohm
1

Share this post


Link to post
Share on other sites

 

It seem to working though I am not sure how reliable (unfaliable) it is
(and if it will be working on all systems machines etc, this is a bit worry)
I've been using raw input for a while. I started using it... I think a year before D3D10 was announced. Reliability depends on the specific input device, some are just not so good but mouse support is solid.

 

 


how can i be sure which mouse detected by rawinput is the secondary?

RawInput will detect all devices, whatever you use them or not is your business. Enumerate them and use GetRawInputDeviceInfo, it gives you a blob of device-specific data, but it has a well known format for mice and it has a device index dwId.

It's a while since I've used that. If memory serves, the first mouse is a virtual mouse obtained by coalescing input from all mice, then the real mouse device follows. But I'd suggest to check that more accurately before going on.

 

 

the second mouse moves also my arrow -cursor, if I disable it by RIDEV_NOLEGACY then both are not moving cursor (it bacame hourglass) and it is wrong too

Unfortunately as far as I recall, windows pointer ballistics are always computed using all the mice connected. I'm following the thread in case someone posts a solution.

 

 

I mean I am using one mouse (call it "1") in normal cursor way,

then i plug the second mouse (call it "2") - in raw input routine i receive deltas for both of them but i do not know how to make sure which mouse in rawinput routine is "1" (though i was not searching to much yet for avaliable options or understanding i was tired) - I need some ok way to get know which mouse in raw input is the secondary (so in raw input i can skip the primary mouse deltas - and use mouse moves for it and deltas for secondary)

 

 

the second thing is how to off dragging cursor behaviour for secondary mouse - Is it can be seen i would like to use "1"

in old wm_mousemove way dragging cursor and stuff , and "2"

as a rawinput deltas device without affecting cursor dragging

 

has someone was doing it and has clea view on this and could hint a bit?

0

Share this post


Link to post
Share on other sites

When enumerating devices, you get an hDevice HANDLE each one.

Note RAWINPUT structures include a a RAWINPUTHEADER. Inside, you will find the very same HANDLE. This allows you to map each VM_INPUT message to a specific enumerated device.

I cannot figure out what you're trying to write in the rest of your message. I hope that's enough for you!

0

Share this post


Link to post
Share on other sites

When enumerating devices, you get an hDevice HANDLE each one.

Note RAWINPUT structures include a a RAWINPUTHEADER. Inside, you will find the very same HANDLE. This allows you to map each VM_INPUT message to a specific enumerated device.

I cannot figure out what you're trying to write in the rest of your message. I hope that's enough for you!

 

allright i will be trying to check this up

 

(in the second part i was asiking again if it is possible

to disable mouse cursor draging for "2" mouse leaving it anebled for "1" - maybe it is just posssible by setuping rawinput in

other way - I do not understand it yet)

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0