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

Modifying a traditional GUI on the fly

4 posts in this topic

By traditional, I mean the usual sort where you create the UI elements, you hold onto their state, and then render them based on their current state. As opposed to immediate mode GUIs where there is little state and your code determines what to draw and how to draw it every frame.

My current issue is with modifying UI elements based on game state. For example, you have a button tied to an object in the game. Depending on the object, that button might be disabled. Whether or not it should be disabled could change at any point. With an immediate mode GUI, it sounds very obvious how you would handle this, since you are already having your code evaluate the button to draw it. But in a traditional GUI where the button already exists and you have to actually put more effort into changing it, I'm curious how people handle this situation.

My current attempt is resulting in a lot of UI code being sprinkled throughout my game logic, changing UI states as game objects change, with lots of checks to see if the object changing is the one currently selected in the UI. This feels very messy, but I don't see an alternative without taking it to the immediate mode extreme.

Are there other ways of handling this more cleanly?
0

Share this post


Link to post
Share on other sites
You can use some form of message passing or observers.

We use messages; a class can register to listen for specific messages from a specific game object, or for a specific message at the global level. We implemented this for core game logic, but it works equally well for UI or any kind of plugin that can act on or modify game state. Edited by turch
0

Share this post


Link to post
Share on other sites
But isn't that essentially the same thing? Whether I litter my game code with sending messages, or with direct UI state changes, I'm still ending up with UI-specific code within the game logic.

The only way I can think of to keep UI updates out of the game logic is to go the IMGUI route and have the UI do its own checking of game state before drawing each component. But that ends up at the other extreme, where I'm implementing game logic twice, once for the game and once for the UI to check on the game. There has to be a middle ground.
0

Share this post


Link to post
Share on other sites
[quote]Whether I litter my game code with sending messages, or with direct UI state changes, I'm still ending up with UI-specific code within the game logic.
[/quote]

Messages aren't UI specific. When a player game object takes damage, it doesn't know or care about the UI. All it knows is it needs to send a "health changed" message.
0

Share this post


Link to post
Share on other sites
UI code should hold references to the data it is displaying. That way, when the data changes, the UI changes also.

If the UI code caches values, so that you have to explicitly update it in order for the content to change, consider making the UI an observer of the data in question. When the data changes, all observers are notified that a change has taken place, and the UI will get this notification and read the latest value as a result.

I find this much preferable to immediate mode GUI programming - with IMGUIs it's easier to switch buttons off and on based on game state but the functionality is so limited. A regular GUI might have 5 or 10 different events that a simple control like a button or a text field might give out, such as focus changes, content changes, mouse over/out, mouse down/up/drag-in/drag-out... immediate mode just can't handle that in a reasonable way.
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