Adding code to try and reset the device if eglCreateWindowSurface and eglCreateSurface are

Adding code to try and reset the device if eglCreateWindowSurface and eglCreateSurface are
called while the device is reported as lost.

Currently only eglCreateContext attempts to reset the device. This is a short term fix until the whole device lost issue can be revisited.  One of the issues here is that if any of these egl entry points are called while the device is lost (e.g. while the screen saver is on in XP) ANGLE will spin until the device comes back.
Committed: http://code.google.com/p/angleproject/source/detail?r=746

[VangelisK, 2011-09-07 23:01:11]

Please review.

[John Bauman, 2011-09-07 23:30:40]

On 2011/09/07 23:01:11, VangelisK wrote:
> Please review.

Would it make more sense to create the surface in ANGLE, but with no actual D3D
resources behind it (those would be created in resetSwapChain later)? Or would
that cause more problems?

[vangelis, 2011-09-09 00:38:05]

On 2011/09/07 23:30:40, John Bauman wrote:
> On 2011/09/07 23:01:11, VangelisK wrote:
> > Please review.
> 
> Would it make more sense to create the surface in ANGLE, but with no actual
D3D
> resources behind it (those would be created in resetSwapChain later)? Or would
> that cause more problems?

I could move the code there but createWindowSurface calls Surface::initialize()
which calls resetSwapChain() so it will be called anyway.  The problem is that,
at least in the driver I was testing with, if you call
CreateAdditionalSwapChain() while the device is lost, the device suddenly
reports that it is S_OK but the next call to present returns an internal error. 
Unfortunately, we don't currently know when it's a good time to create the
window surface so we end up doing it right after we get a context lost event.

[dgkoch, 2011-09-09 17:15:28]

LGTM