--- Operating System, Graphics card ---

Archlinux
Nvidia GeForce 7900GT


--- Blender version with error, and version that worked ---

occurs with 2.68a, 2.69RC1 (r60597), 2.69RC2 (r60761).


--- Short description of error ---

Clicking directly (not dragging) in the timeline or typing (not sliding) the value in the Frame value in the header of the timeline results in the camera being updated correctly, except when going from a frame < marker bound to camera to a frame > marker bound to camera, or going from a frame > marker bound to camera < marker binding the camera that should be active. Then it results in the active camera not being drawn as active.

Dragging the cursor in the timeline and sliding the Frame value in the timeline header works.

Setting the frame from the python console with bpy.context.scene.frame_set() does not update the camera drawn as active at all.


--- Steps for others to reproduce the error (based on attached .blend file) ---

-- Setting from the python console --
1. With the scene frame set at < 160, run bpy.context.scene.frame_set(200) (or any number => 160). The solid triangle above the active camera indicating it is active does not change, even though the camera is no longer active.
2. Dragging the cursor in the timeline after setting the frame past a marker from the console does not update the camera unless you drag the cursor back and forth over the marker that has not been updated.

-- Setting from the timeline --
1. In the example file, there are two markers. One on frame 80, setting 'Camera' as the active camera, and one on frame 160 setting 'Camera.001' as the active camera. If you set the frame from > 160 to < 80 by either clicking (not dragging) in the timeline, or by typing in the Frame value in the header, the camera will ne update.