perryh@xxxxxxxxxxxxxx writes: > James Mckenzie <jjmckenzie51@xxxxxxxxxxxxx> wrote: >> perryh@xxxxxxxxxxxxxx wrote on Sept. 10th: >> >Has there been any thought given to delaying wine's >> >initialization of its X connection, fonts, etc. until >> >the Windows program actually executes a call that >> >requires an X server? >> > >> This will cause Wine to crash with an X server not found error... >> >> In other words, there has to be a running X server in order for >> Wine to run. This is a requirement even for windowless operations. > > Again, has there been any thought given as to whether this > requirement is _necessary_? What problems would arise if it > delayed locating the X server, opening a connection, setting > up fonts, etc. until the Windows program actually performs > some operation that touches the display? Yes, a lot of thought has been given to the problem, and it's essentially what we already do, as far as it's possible within the constraints of the Windows API. -- Alexandre Julliard julliard@xxxxxxxxxx
