• 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.
  • entries
  • comments
  • views

C++11 variable args applied to signals/slots system

Sign in to follow this  
Followers 0


Quick snippetty post today. Been looking at making a clean signals/slots system using varadic templates. This is only tested with GCC 4.7.2#ifndef DELEGATE_H#define DELEGATE_H#include #include template class Event;class BaseDelegate{public: virtual ~BaseDelegate(){ }};template class AbstractDelegate : public BaseDelegate{protected: virtual ~AbstractDelegate(); friend class Event; virtual void add(Event *s){ v.push_back(s); } virtual void remove(Event *s){ v.erase(std::remove(v.begin(), v.end(), s), v.end()); } virtual void call(Args... args) = 0; std::vector*> v;};template class ConcreteDelegate : public AbstractDelegate{public: ConcreteDelegate(T *t, void(T::*f)(Args...), Event &s);private: ConcreteDelegate(const ConcreteDelegate&); void operator=(const ConcreteDelegate&); friend class Event; virtual void call(Args... args){ (t->*f)(args...); } T *t; void(T::*f)(Args...);};template class Event{public: Event(){ } ~Event(){ for(auto i: v) i->remove(this); } void connect(AbstractDelegate &s){ v.push_back(&s); s.add(this); } void disconnect(AbstractDelegate &s){ v.erase(std::remove(v.begin(), v.end(), &s), v.end()); } void operator()(Args... args){ for(auto i: v) i->call(args...); }private: Event(const Event&); void operator=(const Event&); std::vector*> v;};template AbstractDelegate::~AbstractDelegate(){ for(auto i : v) i->disconnect(*this);}template ConcreteDelegate::ConcreteDelegate(T *t, void(T::*f)(Args...), Event &s) : t(t), f(f){ s.connect(*this);}class Delegate{public: Delegate(){ } ~Delegate(){ for(auto i: v) delete i; } template void connect(T *t, void(T::*f)(Args...), Event &s){ v.push_back(new ConcreteDelegate(t, f, s)); }private: Delegate(const Delegate&); void operator=(const Delegate&); std::vector v;};#endif // DELEGATE_H
Everything is non-copyable, can't quite work out sensible copying strategies for events or slots.

I haven't used Signal and Slot terminology because I use QtCreator and it highlights words like "slots" as they are sort of Qt defined keywords which was annoying.

Some usage:class SomeObject{public: Event someEvent; void f(){ someEvent(23, 45.0f); }};class AnotherObject{public: AnotherObject(SomeObject *o);private: void handle(int i, float f){ /* ... */ } Delegate delegate;};AnotherObject::AnotherObject(SomeObject *o){ delegate.connect(this, &AnotherObject::handle, o->someEvent);}
So defining an event in an emitter is just a case of adding a an Event<> object to its public interface. You can then call it using function syntax.

A listener just needs a Delegate object and can then connect events to any member function using the standard address-of syntax. This is compile-time type safe and will only allow connection to a member function with the correct parameter types.

The destructors of the Event and Delegate classes take care of doing auto-disconnects when the owning objects get destroyed.

A nice example of how varadic templates are taking traditionally complex and ugly code and making it almost trivial. I also like the way that you don't have to use any template syntax in the actual usage, apart from when you define the Event itself.

Thanks for reading.

If anyone wants to see an article on this, explaining step by step how it works, just let me know. Not something I'd do without some interest first but happy to contribute if anyone wants it.

Sign in to follow this  
Followers 0


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