Behaviors not being loaded on device?

#1 On the simulator, I noticed it auto-loaded any scripts in the Behaviors directory. Not sure of the mechanism but it did. Apparently however that doesn't carry over to the device.

So I added an exec call for the behaviors I need and now they are being loaded, but the onUpdate is never being called.

#2 There is a flag that you have to set in the level file to enable the onUpdate callback (I think). Personally I never saw the advantage of behaviours.

#3 @Scott
I set the flag. In the simulator the onUpdate runs fine. It doesn't run at all on my iPad.

As for why? Well it seemed the easiest way to go about doing what I wanted, which is a constant animation of the objects alpha value over time. What other method would you suggest?

#4 You could achieve the same with a function and a schedule? I tried behaviours but found the onUpdate (every 33ms) to be a performance inhibitor and preferred to have more control. As they say ... your mileage may vary :)

#5 Don't you have to set the flag USE_COMPONENTS for the device build (memory might be failing me here)?

#6 I haven't looked into schedules. I'll take a look at the docs and see if that will work. Sounds like it would, based on the name :)

#7

Quote:
Don't you have to set the flag USE_COMPONENTS for the device build (memory might be failing me here)?

That appears to be defined by default.

Scott, could you possibly give an example of scheduling? I found the docs for it in the TGB docs, but I can't get it to work.

%tile = new t2dStaticSprite()
{
    Class = "Tile";
};
%tile.schedule(1000, "testSchedule");
function Tile::testSchedule(%this)
{
	echo("testSchedule");
}

But the method never gets called.

#8 So ironically i'm having the same problem as with the behavior :(

When I run this on the simulator the scheduled method gets called as expected. On my iPad it does not.

#9 All these problems... I just close my eyes and pretend they don't exist :).

Sorry I usually can't be much of help because I'm still on itgb 1.2.

But definitely use schedule instead of onupdate as much as possible (when it makes sense of course). Schedules are better on performance usually.

@John - Haven't tested the function on your post but I believe it should work.

The advantage of using object scheduling like the example above is if the objects get deleted before the schedule is called the schedule also gets deleted.

Here's a very simple example.

function main()
{
   // Run this schedule after 1 second.
   // You can replace 0 with an object name to associate this schedule 
   // with an object.
   $scheduleID = schedule(1000, 0, foo, %arg1); 
   
   // To cancel the schedule
   // cancel($scheduleID);
}

function foo(%arg1)
{
   echo("Foo");
}

#10 Yeah I have rewritten things to use schedule instead, and it works -- on the simulator and my iPhone4. It does not work on my iPad3.

How strange is that. Schedules appear to not function on iPad3. This is a pretty show stopping bug for me :(

#11 @John - Is there a different in the OS or SDK versions between your iPhone 4 and new iPad?

#12 @John, my gut tells me that there is something not quite right in your iPad3 code. It's possible there is some error that is stopping your main.cs from running.

The actual script engine should be no different across all the iDevices. Can you put debug in from the top down to where you expect to see things - just to see that the scripts are executing in order.