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

Get unique IDs by reading the Instruction Pointer Register

28 posts in this topic

In my code I have so far avoided the issue by not passing in an ID at all, and counting widgets internally per frame.

I use the ID to keep track of the current 'hot' and 'active' widgets. Not having fixed IDs means I cannot change the GUI while any widget is hot or active.

So I have a simple rule: the GUI can only change in response to a widget being triggered. At that point the hot and active flags are cleared, and the IDs are free to change.

This is in a level editor. It wouldn't work so well in a game environment where the interface could change in response to game events. There is the option though of explicitly setting the current ID through a function. It also wouldn't work if you used IDs to store information per widget, but I don't do that.
0

Share this post


Link to post
Share on other sites

. Maybe I find myself making lots of buttons with similar behavior/logic/etc... So I make a helper function to eliminate the boiler-plate parts of the API. Oops, nothing works anymore.

There should be helper functions to draw/process a button, draw/process a slider, etc. which presumably receive widget IDs as parameters (along with text, geometry, callback function pointers, etc.); you can do the same for composite or specialized widgets, and you can combine parent IDs and child IDs in case you process child widgets recursively, so what's the problem? Maybe that you are making lots of buttons, and you would be more comfortable with a retained mode GUI?
0

Share this post


Link to post
Share on other sites

Yeah I already tried to say that the linenumber is useless for composite widgets that get called more than 1 time.

If you for example make a do_okcancel function you cant just let it use __LINE__ for the ok button and __LINE__+1 for the cancel button it calls, because when dialog1 and dialog2 both call that it wouldnt work then cause of same id on the second call.

Thats why I hinted already at using the parent id, because it should by definition be unique already, and mangling it with a hashfunction. Then you could call the ok button with gen_id(id,2,0) and the cancel button with gen_id(id,2,1) and it magically just works, if you found a good gen_id hashfunction.

A simple example would be like gen_id(id,n,i)=id*n+i but it only works if n is the global max for all i=(childwidgetindex inside a widget) in all widgets and its guaranteed that it never overflows and nowhere a conflicting id is generated. I would encourage you to find a better one yourself. (I currently use some other, but it is more complicated and in some aspects better, in others possibly worse.)

0

Share this post


Link to post
Share on other sites

The ID is known at compile time, and in my case, I have a "std::vector<widget> DrawQueue" that I push widgets on with drawing information. I loop through this vector later at draw time for batching. This decouples the drawing and the interaction with the widget.

 

Nothing is stopping you from adding more data to the widget structure that gets added to the DrawQueue. A helper function could look for the widget with a certain ID and respond to whatever states are in that widget instance.

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