The view will be updated according to the MapControl.UpdateMode of the map control. If the current mode is Scheduled or OnTimer, there may be a delay until the actual update takes place.

This is the recommended kind of update to use in most situations, since it doesn't add any extra load to the system.

This tells the map control to ignore the behavior of its current update mode, and update the view as soon as possible. The call will return immediately, without waiting for the update to finish.

This kind of update can be useful for instance if you run the map control on slow timer, but want result of a user interactions to show up immediately, without waiting for the next timer update. But note that it will result in an increased load on the system.

This kind of update should almost never be used. The update will be carried out directly, on the calling thread, completely bypassing the update scheduler of the map control. The call will not return until the update is complete.

The only reason to use this is if you want to do something with the screen output immediately afterwards, like calling Drawable.Save or similar to make a screen shot of the map window. In all other cases, use Default or Immediate.

The view will be updated according to the MapControl::updateMode of the map control. If the current mode is MapControlUpdateModeScheduled or MapControlUpdateModeOnTimer, there may be a delay until the actual update takes place.

This is the recommended kind of update to use in most situations, since it doesn't add any extra load to the system.

This tells the map control to ignore the behavior of its current update mode, and update the view as soon as possible. The call will return immediately, without waiting for the update to finish.

This kind of update can be useful for instance if you run the map control on slow timer, but want result of a user interactions to show up immediately, without waiting for the next timer update. But note that it will result in an increased load on the system.

This kind of update should almost never be used. The update will be carried out directly, on the calling thread, completely bypassing the update scheduler of the map control. The call will not return until the update is complete.

The only reason to use this is if you want to do something with the screen output immediately afterwards, like calling Drawable::save or similar to make a screen shot of the map window. In all other cases, use ViewUpdateKindDefault or ViewUpdateKindImmediate.

The view will be updated according to the MapControl.updateMode of the map control. If the current mode is SCHEDULED or ONTIMER, there may be a delay until the actual update takes place.

This is the recommended kind of update to use in most situations, since it doesn't add any extra load to the system.

This tells the map control to ignore the behavior of its current update mode, and update the view as soon as possible. The call will return immediately, without waiting for the update to finish.

This kind of update can be useful for instance if you run the map control on slow timer, but want result of a user interactions to show up immediately, without waiting for the next timer update. But note that it will result in an increased load on the system.

This kind of update should almost never be used. The update will be carried out directly, on the calling thread, completely bypassing the update scheduler of the map control. The call will not return until the update is complete.

The only reason to use this is if you want to do something with the screen output immediately afterwards, like calling Drawable.save or similar to make a screen shot of the map window. In all other cases, use DEFAULT or IMMEDIATE.

The view will be updated according to the MapControl.updateMode (not available in Python) of the map control. If the current mode is (not available in Python) or (not available in Python), there may be a delay until the actual update takes place.

This is the recommended kind of update to use in most situations, since it doesn't add any extra load to the system.

This tells the map control to ignore the behavior of its current update mode, and update the view as soon as possible. The call will return immediately, without waiting for the update to finish.

This kind of update can be useful for instance if you run the map control on slow timer, but want result of a user interactions to show up immediately, without waiting for the next timer update. But note that it will result in an increased load on the system.

This kind of update should almost never be used. The update will be carried out directly, on the calling thread, completely bypassing the update scheduler of the map control. The call will not return until the update is complete.

The only reason to use this is if you want to do something with the screen output immediately afterwards, like calling Drawable.save or similar to make a screen shot of the map window. In all other cases, use ViewUpdateKind.Default or ViewUpdateKind.Immediate.