IFD100 bugs

• Rubberbanding course changes does not seem to work very well with the IFD100... you can rubberband a change... but the name of the new waypoint is not conveyed to the IFD's and the PFD does not see the new waypoint name either... (I have twin IFD0440s).
• Furthermore, the new waypoint is far away from the waypoint that is created in the IFD100.. to the tune of 1000's of miles... so, I guess the waypoint record is getting munged somehow or is being interpreted incorrectly. 
• I seem to get some alerts about issues with the traffic sensor (I have a SkyTrax100 running 4.1.0
• the IFDs do not appear to have the issues and the traffic seems to be fine... 
• Esp when I am on the ground and taxing around, the heading on the IFD100 can get off from the heading value in the IFDs (which are always identical to the MFD and PFD)... in flight I rarely see this but I suspect that perhaps my IFD100 instance is somehow using the heading information from the iPad?  Not sure why its off...
• The IFD100 should disable the screensaver... there is a simple programmatic way to do that in iOS...

Just put it in the overridden callback within your top level view controller:

// this is called when the application is placed into the foreground

-(void)applicationWillEnterForeground:(UIApplication *)application {

// disable the timer that causes the iOS device to sleep

[[UIApplication sharedApplication] setIdleTimerDisabled:YES];

}

And, actually, you want to "undo" this when the IFD100 gets placed in the background:

// we must explicitly handle sending the application into the background

-(void)applicationDidEnterBackground:(UIApplication *)application {

    // re-enable the timer that causes the iOS device to sleep

    [[UIApplication sharedApplication] setIdleTimerDisabled:NO];

}

Doug