Re: Implement LockWindowUpdate [take 2]

[Alexandre Julliard]

Mike Hearn  writes:
> The other reason it might have bounced is if we're not allowed to extend
> WND, though as it's purely internal and not accessible from the APIs that
> should be OK? I'm not sure how to do this otherwise without exporting the
> currently locked window variable from USER to X11DRV which probably breaks
> dll separation. Either that, or adding a new driver procedure.

Extending the WND structure is OK (though it doesn't seem necessary in
that case), but accessing it from x11drv is a violation of dll
separation. We still do that in a number of places but they will have
to be fixed, so we probably shouldn't add new ones.