Personally I think it would be great to add in an Autorelease behavior and a Release behavior. GS could even put a little note in the behavior saying "If you do not understand how to use this behavior, it is best to not use it", or even "lock" these behaviors in the menu and have the note come up when they are unlocked by the user.
Although it would be nice to have both, you could get away with just a Release behavior by adding the Autorelease code to the Destroy behavior. Right now I see no point in Destroy as it doesn't appear to remove the allocated RAM from the pool.
Not knowing how GS handles the Alloc/Init of the "actors", it's hard to see where memory is going or how it's handled, but in my eyes it is a major issue. Read any book on Objective-C and you'll realize that because garbage collection doesn't exist in the iphone, memory management falls FULLY on the hands of the programmer. Allowing users who understand memory management to control the releases will allow for muuuuuch smoother large games. Much less RAM waste, and best of all, faster loading times if Alloc/Init are changed as well. Sure it's a big project, but it would be wholly valuable to the program and the user base.
Why are you bumping this thread?? You didn't even make it, you asked a question not even an hour ago, and no one answered-so you bump it. Give people time to answer, or make your own thread asking your question.
iTouchGamer said: Why are you bumping this thread?? You didn't even make it, you asked a question not even an hour ago, and no one answered-so you bump it. Give people time to answer, or make your own thread asking your question.
Yes it is, for the people that look at the bottom of the main page to see who posted recently, if they see you posted and they click on it, if it just says "bump" they're pissed!
I will take my time now (For tim), just thought it was a massive community. iTouchGamer, that's nice to know. Don't really care myself if there's one little bar in front of another topic I'd like to read
so using the iOS keyboard is for only inserting names into gamecenter? Its not incoporated into our game usage? Its not a new tool for our games?
K this needs to be answered. because if using the keyboard is only for gamecenter. Then this should have been noted when roadmap came out. Ive been holding off on 6 apps because I was under the impression people where going to be able to use the keyboard to insert player names. And dont go preaching that you can make your own keyboard in GS.
Comments
Will it make it run Game Betters or The Same?
Cheers.
Although it would be nice to have both, you could get away with just a Release behavior by adding the Autorelease code to the Destroy behavior. Right now I see no point in Destroy as it doesn't appear to remove the allocated RAM from the pool.
Not knowing how GS handles the Alloc/Init of the "actors", it's hard to see where memory is going or how it's handled, but in my eyes it is a major issue. Read any book on Objective-C and you'll realize that because garbage collection doesn't exist in the iphone, memory management falls FULLY on the hands of the programmer. Allowing users who understand memory management to control the releases will allow for muuuuuch smoother large games. Much less RAM waste, and best of all, faster loading times if Alloc/Init are changed as well. Sure it's a big project, but it would be wholly valuable to the program and the user base.
Matt
Matt
K this needs to be answered. because if using the keyboard is only for gamecenter. Then this should have been noted when roadmap came out. Ive been holding off on 6 apps because I was under the impression people where going to be able to use the keyboard to insert player names. And dont go preaching that you can make your own keyboard in GS.
Matt
Cheers.
Ace
Ace
Maybe something good is coming. checking for an update now.
Dang.
lol