<br><br> <div class="gmail_quote">On Dec 10, 2007 10:38 AM, Brian Paul <<a href="mailto:brian.paul@tungstengraphics.com">brian.paul@tungstengraphics.com</a>> wrote:<br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> <div> <div></div> <div class="Wj3C7c"> </div></div>I think Tom mostly answered your question, but I think the crux of your<br>problem is the difference in interpretation of "Display".<br><br>There's the X concept of Display which can be a collection of screens <br>which is controlled by the X server.  Or you can think of the Xlib<br>'Display' datatype which has a default screen field and can identify a<br>particular screen.<br><br>For multi-screen EGL, I think you'd simply have to obtain an EGLDisplay <br>handle for each screen.<br><font color="#888888"><br>-Brian<br><br></font></blockquote></div> <div> </div> <div><br>Yes, in X, a display can have multiple screens but it's not the same in EGL. That's the problem. Your solution would be ideal, but how would you do it? How would you get an EGLDisplay handle for each screen when eglGetDisplay wants a X Display as a parameter. Calling XOpenDisplay multiple times to create multiple X Display structures is not a option. X applications don't work that way. The application only wants a single "display" with multiple screens. </div> <div> </div> <div>Mike</div> <div> </div>