• 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
Aardvajk

Win32 API "EDIT" controls

6 posts in this topic

Probably a bit of a dopey question, but if I create an edit control with the C Win32 API: HWND Edit=CreateWindow("EDIT","",WS_CHILD, ... etc How would I go about intercepting keystrokes made when typing in that control so that I can do special processing? I'm tring to put a borderless edit control on top of a grid to implement property editing and want to move the edit box up or down when the appropriate arrow keys are pressed but I can't find anything in the docs about custom responding to keypresses. Thanks. [EDIT] I've just been reading about sub-classing, i.e. providing a custom WndProc for the edit control and deferring any messages I don't process to the original WndProc for the control. Is that the simplest way to do what I want, does anyone know?
0

Share this post


Link to post
Share on other sites
Yes, this is the most proper way of doing it and it is fairly simple (maybe not for the first time). In fact, it is commonly used for other control too ;-)
0

Share this post


Link to post
Share on other sites
Yup, I agree that subclassing the window is the easiest way. From my code (For a RichEdit, but same thing really):

// Bloody Microsoft headers
#ifdef _WIN64
# define CAST_TYPE (LONG_PTR)
#else
# define CAST_TYPE (LONG)(LONG_PTR)
#endif

// Create window
m_hWnd = CreateWindowEx(WS_EX_TRANSPARENT, RICHEDIT_CLASS, "", dwFlags, x, y, w, h, hWndParent,
NULL, hInstance, NULL);
if(!m_hWnd)
return false;
SetWindowLongPtr(m_hWnd, GWLP_USERDATA, CAST_TYPE this);

// Subclass RichEdit
m_pfnOldProc = (WNDPROC)(LONG_PTR)GetWindowLongPtr(m_hWnd, GWLP_WNDPROC);
SetWindowLongPtr(m_hWnd, GWLP_WNDPROC, CAST_TYPE CDruinkEdit::StaticWindowProc);

// Snip...

LRESULT CALLBACK CDruinkEdit::StaticWindowProc(HWND hWnd, UINT uMsg, WPARAM wParam, LPARAM lParam)
{
CDruinkEdit* pParent;

pParent = (CDruinkEdit*)(LONG_PTR)GetWindowLongPtr(hWnd, GWLP_USERDATA);
if(!pParent) return DefWindowProc(hWnd, uMsg, wParam, lParam);
return pParent->WindowProc(uMsg, wParam, lParam);
}

LRESULT CDruinkEdit::WindowProc(UINT uMsg, WPARAM wParam, LPARAM lParam)
{
switch(uMsg)
{
case WM_DESTROY:
OnDestroy();
break;

// Snip...
}
return m_pfnOldProc(m_hWnd, uMsg, wParam, lParam);
}

void CDruinkEdit::OnDestroy()
{
SetWindowLongPtr(m_hWnd, GWLP_WNDPROC, CAST_TYPE m_pfnOldProc);
SetWindowLongPtr(m_hWnd, GWLP_USERDATA, 0);
}



The reason for that CAST_TYPE mess is to get the code to compile correctly and without warnings in both x86 and x64 configurations. The MS headers seem to make that particularly difficult...
0

Share this post


Link to post
Share on other sites
Cheers Steve.

I note that when you handle the WM_DESTROY message, you then break out and still call the original handler. Do you have to do that for all messages? If I want to override a keypress, is it good practise to just return from my Proc without calling the original or should I modify the keycode in the message (to zero or something) and hand it on to the default Proc?

I'll play around and see what happens either way but just wondered what people thought. Cheers for the code though.
0

Share this post


Link to post
Share on other sites
Quote:
Original post by EasilyConfused
Cheers Steve.

I note that when you handle the WM_DESTROY message, you then break out and still call the original handler. Do you have to do that for all messages? If I want to override a keypress, is it good practise to just return from my Proc without calling the original or should I modify the keycode in the message (to zero or something) and hand it on to the default Proc?

I'll play around and see what happens either way but just wondered what people thought. Cheers for the code though.
Yes, you should pass all messages off to the original handler, otherwise the control won't behave like an Edit control unless you override all the relevant messages. For keystrokes, I don't think it'll be nessecary to pass them to the original handler, unless you want the key to be typed. I wouldn't change the keystroke message then pass it on.
0

Share this post


Link to post
Share on other sites
Just got it all implemented and all works like a dream. Really handy new thing to know about, this subclassing stuff.

Thanks all.
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