Comment 1 for bug 1170510

For displays with multiple possible resolutions-- like my monitor-- glmark2's current logic is generating events for, and handling, every modeline supported by the display and setting it. So, in my case, my display lists modelines from 1920x1080 at various frequencies down to, say, 640x480. N output_mode events are generated, and the benchmark's surface is resized n times, with the final modeline entry being "the" dimensions for the duration of program execution-- in my case, 640x480. After all those events are handled, I have a fullscreen surface (1920x1080) drawing a 640x480 benchmark.

Locally, I set a bit after the first output_mode event is handled, which properly scales the benchmark, and then early-return every event thereafter. In other words, "the first event is right." This gives me the desired result. This is clearly a hack and not a proper fix. Investigating the "right" way to do this.