Sounds like c++, aalok.
@Rie: It'd be nice if you put your code into code tags.
Doing the following:
[code]for(int a;;)[/code] |
will transform into:
for(int a;;)
And will keep tabbing, giving our eyes better focus.
The problem here is we don't know your set-up.
1 2
|
#include "allocore/io/al_App.hpp"
#include "Ramp.h"
|
Allocore is a publicly available library (on github, thanks Google).
But ramp.h? We have no idea what it has inside.
One of the common problems on similar setups could be:
1. Check if the window is redrawn.
Check if onDraw is ever called (Probably is).
2. Check if the backbuffer (if available) is swapped.
Do you need to call a command similar to g.EndDraw() , and you forgot about it?
3. Calculations
Calculations inside onAnimate could be wrong. Do a simpler calculation system work? Do simple examples work?
The problem isn't about the 100 objects to animate.
Just get a single one to animate, and you're done, adding the others won't be such a big problem compared to your current one.
EDIT: Fixed typo