video_driver_state_t::widgets_flags becomes main_flags, the display
state only the main thread writes and reads, and VIDEO_FLAG_ACTIVE and
VIDEO_FLAG_CRT_SWITCHING_ACTIVE move into it from 'flags', which the
video thread's drivers also change. video_driver_frame() sets both
every frame - ACTIVE from the driver's frame() result, the CRT bit while
switching is off - and run-ahead flips ACTIVE around every hidden frame;
all of that is plain writes rather than video_driver_modify_disp_flags()
under display_lock. The frame's snapshot still carries both words.
That is two lock and unlock pairs fewer per frame, with threaded video
or without, and more with run-ahead.