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

Pretty advanced pointer problem

28 posts in this topic

[quote name='dimitri.adamou' timestamp='1344857998' post='4969021']
Oops. My bad, I went through your code and saw that in item.h virtual is defined.. but it is derived from yet another class.

Your classes are trying to do too much, the design is a bit confusing - you should try seperate everything as much as possible. Someone wrote a really good article on gdev.net, but I can't seem to find it.. it spoke about foward declaration and just maintaining neatness in code

I haven't spent much time in there though. But yeah, back to my original point - your classes are trying to do too much
[/quote]

Yeah, i've gathered that.

Sp basically i'll have to look up how i use inheritage as well as splitting up my code further into "master classes" that can be accessed to all classes that needs to use that code. So for example instead of having a movement function in both player and enemy i should just make that one function in the Entity class (which is their interface class)? That's what you mean right?

Someone mentioned that my loadFiles class is inherit weirdly. He said that the code is probably being run several times (meaning the files that are loaded are loaded several times). He continued to say that i should look up composition vs inheritance. I'm guessing that after reading up on that i might help to solve some of the problems i am having.
0

Share this post


Link to post
Share on other sites
[quote name='dimitri.adamou' timestamp='1344892563' post='4969191']
It almost sounds like you have a race condition going on, is there any multi threading involved?
[/quote]

I haven't created any additional threads. So unless they can be created without me actively writing the code for it it's not
0

Share this post


Link to post
Share on other sites
[quote name='Bluefirehawk' timestamp='1344849432' post='4968990']
I'm sorry Servant of the Lord, I have to disagree strongly.

A "break;" statement in a for loop doesn't make sense. By doing this:
[CODE]
for(vector<Container*>::iterator it = containers.begin(); it != containers.end(); it++)
{
if(!(*it)->getFull())
{
(*it)->addItem(itemAdd);
break;
}
}
[/CODE]
You modified a for loop to a while loop. Hence what you really need here is a while loop.
Both works fine, it makes a difference when a Theoretical IT guy needs to verifiy the program.
A for loop is simple, it knows at runtime the exact amount of times the body is executed. A while loop is a bit more complicated. And by camouflaging a for loop in a while loop, you make the poor guy cry.

[/quote]


I would just like to point out that this is almost exactly backwards. Using a while loop here would be emulating a for loop, not the other way around. I still see a lot of people espousing the antiquated C coding standards that say not to use a break in a for loop, but they are just that; outdated. The only time you will ever know at runtime how many times a for loop will be executed is if you use a constant value in a conditional test.

Obviously the preferable method here would be to use an algorithm like std::find_if as another poster mentioned. But absent that, a for loop is a better option than a while loop. Indeed, std::find_if itself is typically implemented as a for loop with a break, i.e.:

[CODE]
// TEMPLATE FUNCTION find_if
template<class _InIt, class _Pr> inline
_InIt _Find_if(_InIt _First, _InIt _Last, _Pr _Pred)
{
// find first satisfying _Pred
for (; _First != _Last; ++_First)
if (_Pred(*_First))
break;
return (_First);
}
[/CODE]
1

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