[Bug 1358] "GraphicsDriver" = "none" wanted

[Wine Bugs]

http://bugs.winehq.com/show_bug.cgi?id=1358

------- Additional Comments From [e-mail]  2003-28-06 10:33 -------
Bug comments restored from Gmane.org:

I suggest making a dummy graphicsdriver such "GraphicsDriver" = "none" which
just makes stdout and stdin transparent.

The two existing drivers x11drv and ttydrv won't do when running console
programs many times in a row (e.g. a win32 console compiler from a gnumakefile):

x11drv: initialization due to communication with xfs is painful over a slow
network (e.g. a modem line)

ttydrv: uses ncurses which means restoring the contents of the window each time
wine finishes. This erases the output of the console program.

Here is the code:

// original code beginning in line 73 of user_main.c (rev 1.50):

if (!(graphics_driver = LoadLibraryA( buffer )))
    {
        MESSAGE( "Could not load graphics driver '%s'\n", buffer );
        return FALSE;
    }

----

// could be changed to something along these lines:

if (strncmp( "none", buffer, MAX_PATH) == 0 ) ; // do nothing
    else if (!(graphics_driver = LoadLibraryA( buffer )))
    {
        MESSAGE( "Could not load graphics driver '%s'\n", buffer );
        return FALSE;
    }

------- Additional Comments From mike <at> theoretic.com  2003-04-03 02:56 -------
What is wrong with wineconsole? It was patched lately to use the standard
stdin/stdout, so you can run winedbg in the xterm from which it was started for
instance.

Is that what you're thinking of?

------- Additional Comments From wine <at> how.dk  2003-04-03 16:49 -------
Not sure (haven't tried the latest version). If wineconsole still uses ncurses
clearing/restoring the console after the program finishes, then the "none"
driver is still needed.

------- Additional Comments From mike <at> theoretic.com  2003-04-04 03:18 -------
I don't think it does, running winedbg with the console driver is just like
running gdb. Please try Wine CVS and see if this is fixed.