I'm trying to get this to work... here is the pastebin if you'd rather look at it through that http://pastebin.bafserv.com/699

Anyway, when using an iterator to call the Draw() method nothing actually draws. Pressing space in the example will draw them as Draw() is being called directly.

What am I doing wrong/how can I correct this?

Hehe don't ask why I used gnolam's avatar.

EDIT:

Here is the fix for this.. is there anyway to do this with the above example?

FYI: CGamesPlay was a major contributor to this being fixed :-D.

Another error that I'm having that CGamesPlay said was the right syntax and I thought so myself is this line:

...
vector < Avatars* > CurrentList, AvatarList;
// Avatar List gets filled so don't worry there is stuff in it
...

CurrentList.reserve(MAX_AVATARS_ON_SCREEN);
for(int i = 0; i < MAX_AVATARS_ON_SCREEN; i++)
  CurrentList.push_back(AvatarList.at(rand() % AvatarList.size()));

*.at() should return a pointer and so it compiles correctly. The problem is that it stops things from being drawn and causes my CPU to be 100% and lags like crazy. I comment that line out and "bam" it's fixed. Is their a correct way to do this or is their a workaround like maybe setting a temp Avatar instance setting it equal to *.at(...) then pushing it to the back of CurrentList? I would rather have a one line simple thing.

MAX_AVATARS_ON_SCREEN is set to 15 for now.

This is how they're drawn:

bool Game::DrawAvatars()
{
  vector< Avatar* >::iterator curAvatar;
  for(curAvatar = CurrentList.begin(); curAvatar != CurrentList.end(); curAvatar++)
    (*curAvatar)->Draw();
  //Log::log("CurrentList.size() = %i", CurrentList.size());
  return true;
}

This is the Avatar's Draw method:

bool Avatar::Draw(void)
{
  this->m_Avatar.Blit(10, 10);
  return true;
}

EDIT: I hate having difficult questions that no one knows the exact answer to or just ignore me

Donno why its hanging there, likely a copy paste error or something.

CurrentList.reserve(MAX_AVATARS_ON_SCREEN);
for(int i = 0; i < MAX_AVATARS_ON_SCREEN; i++)
  CurrentList.push_back(AvatarList.at(rand() % AvatarList.size()));

Should be:

#include <algorithm>

CurrentList.resize(AvatarList.size());
random_sample(AvatarList.begin(), AvatarList.end(), CurrentList.begin(), CurrentList.end());

Its not pretty:

random_sample(AvatarList.begin(), AvatarList.end(), CurrentList.begin() + dead_avatar_index, CurrentList.begin() + dead_avatar_index + 1);That will make it replace 1. I have no idea why you wouldn't just use your code.

Err, maybe std::random_sample or "using namespace std;" would help? These seem like errors you get when you forget about a namespace . This and the fact that <algorithm> probably only wraps <algo.h> in a namespace .

Tried that and I am already using the standard namespace.

Then how do I set the size that CurrentList is going to be filled up to?

Bah I never saw resize() on cppreference.com, I always overlook things. That's totally what I wanted to use in my other projects too not reserve(). Umm where can I get an update for all the standard libraries because no matter what I try I can't get random_sample() to work with <algorithm>.

MinGW (the version that came with Dev-C++ beta 5 [4.9.9.2 or whatever])

#define MAX_AVATARS_ON_SCREEN 15
...
#include <algorithm>
...
CurrentList.resize(MAX_AVATARS_ON_SCREEN);
random_sample(AvatarList.begin(), AvatarList.end(), CurrentList.begin(), CurrentList.end());

When I use #include <algo.h>
I get errors when trying to draw my CurrentList using (*iter)->Draw() My logfile is full of

for all of my Avatars in CurrentList. I changed CurrentList and AvatarList from vector < Avatar* > to vector < Avatar > and I got their names instead of that weird A but they were still not valid >.<. I'm thinking about trying this with an array instead of a vector. Or maybe try and STL::List (but lists and vectors are so similar I wouldn't see how that would effect things.

Avatar.hpp

Avatar.cpp

Ok to get the log file to produce this:

This is what I did
Game.cpp area:

Same log file. The object isn't being copied. Is that good or bad?

Baaaaah, this is what always defers me away from programming sometimes. Everything always looks right, seems like it should work... BAM! RUN TIME ERRORS that are hard as hell to solve.