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

Identifying events

5 posts in this topic

I need a efficient way of identifieng events..

atm I have a event class;

[CODE]

class Event
{
public:
Event(int eventId)
:
m_eventId(eventId)
{
}
private:
int m_eventId;
}
[/CODE]

When users write events they do it like this:

[CODE]
enum
{
kCustomEvent = 'cste'
}

class CustomEvent
{
CustomEvent()
:
Event(kCustomEvent)
{
}
}
[/CODE]

This is an idea I got from using the C4 Engine.. Its efficient to use integers like this, but Its dangerous as events might be called the same using the four letter char.. I could use strings, but hashing and comparing them wouldn't be as efficient..

Any tips on how I could do this?
0

Share this post


Link to post
Share on other sites
I'm guessing your building your own engine/library intended for other people to use? Either way, my most personal opinion is that you can't protect another programmer from every silly mistake he or she might do. If it's documented that you should use enum values and someone attempts to use [font=courier new,courier,monospace]'4'[/font] it should simply fail, preferably with an error message telling that programmer to read the .. manual.

If you actually try to protect someone from every possible error you'll realize that you can never do that good enough. What if one programmer uses the string 'cast' hoping that you'll provide typecasting while another programmer uses the same string 'cast' hoping that his or hers character will throw a fireball?

[i][b]Summary:[/b] Use integers if only one option is available; if there's several options (flags) available you could use bitmasks. Make sure to document it.[/i]
0

Share this post


Link to post
Share on other sites
Guess I could have a check to see if its already one event registered with the same id..

But I also use the id's internaly in the engine so the user need to look through the code to know..
0

Share this post


Link to post
Share on other sites
Another automated solution would be:
[CODE]
struct Event
{
Event(void)
{
}
virtual ~Event(void)
{
}
virtual const int getID(void) const = 0;
private:
};
template<class E>
struct Event_ : Event
{
Event_(void)
{
}
static bool checkType(Event* event)
{
return (int)&Event_<E>::TypeIDRef == event->getID() ? true : false;
}
static E* convert(Event* event)
{
if ((int)&Event_<E>::TypeIDRef == event->getID())
return (E*)event;
return NULL;
}
virtual const int getID(void) const
{
return (int)&Event_<E>::TypeIDRef;
}
static const int TypeIDRef;
};
template<class E>
const int Event_<E>::TypeIDRef = 0;
[/CODE]

then you could use it like:
[CODE]
struct superEvent : Event_<superEvent>
{
};
Event* e = new superEvent();
if (superEvent.checkType(e))
{
//yes this is the event i am looking for
}
//or
superEvent* event = superEvent.convert(e);
if (event)
{
//yes this is the event i am looking for
}
[/CODE]
0

Share this post


Link to post
Share on other sites
There is a simple template trick for generating type ids. However they are different every time you start your application.

[code]
template<typename T> size_t getType() {
static T* ptr=0;
return (size_t)&ptr;
}

class EventA ...
class EventB ...

size_t typeA = getType<EventA>();
size_t typeB = getType<EventB>();
[/code]
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