Yeah, I had some problems with classes until I realized I was initializing them in the wrong place. Besides, global class instances are evil anyway. Just remember to instance them from main--after you initialize PAlib. If you don't, the screen turns turquoise (at least mine did).XianForce wrote:You can use C++ with PAlib but I've heard there can be problems with it... although I'm not sure if it's true or not.
<off-topic>Omg. That happened to me, too. But it was only my flashcart. That had to have been months ago. And when I woke up today, it was sitting on my desk. I'm not sure who found it, or took it in the first place, but I don't care as long as I have it now.</off-topic>XianForce wrote:Yeah I got into DevKitPro a little bit, but then my DS along with the flashcart mysteriously disappeared. All I remember was, I was testing an app for a friend, set the DS on my desk when I was done... Went to sleep, woke up and it was gone. It's been gone for 2-3 months and I haven't the slightest clue of where it is... I just know it's in the house somewhere (I think...)
No, you can use the current one. It's just that some of the functions don't work at all, or don't work correctly. Though in all fairness, they weren't important ones. Sprite flippping\sprite effects\etc... But finding the new version will probably require a few google searches of the palib forums.zapakitul wrote:I for one would recomand you to use Libnds, and not PALib, hence last time I checked PALib forces you to use an outdated version of DevkitPro.
<sarcasm>Surprise!</sarcasm> *freakin' post padding pickzell*Pickzell wrote:I really have no comment.
Oh and for the record, I have a CycloDS Evolution. http://www.cyclopsds.com/cgi-bin/cyclod ... sevolution