|
From: Russell L. <gs...@gh...> - 2005-02-05 09:41:17
|
Hans-Bernhard, > That would be putting it mildly. As of the current release version, > 4.0, the 16-bit version no longer even compiles. So do you want all 16-bit code removed? > And the 32-bit version is known to have various problems. Apparently, > it never worked on Win9x at all. Neither the "print this" menu entry in > the graph context menu, nor the 'set output 'PRN:' method. Neither of these should have been broken in the move to 32-bit. Note that it is "set output PRN", not "set output PRN:". > As a matter of fact, I sometimes think it's time to rewrite the entire > Windows-specific part of gnuplot from scratch, given that with Win32 > it's possible to have gnuplot behave the same way X11 gnuplot does. In > particular, I would really like to get rid of the home-grown terminal > emulator and all the problems and limitations it causes. Doing it on one thread may be a little tricky. Do you want gnuplot to provide the command line editing, or do you want the default Windows command line editor? If gnuplot provides it, then we might be able to do it on a single thread. If you use the Windows console to provide line editing, then we might have to use two threads. The first thread is the console and the main gnuplot code. The second thread handles the image window. A small amount of synchronisation code is required to lock the image window data structures as each new plot is drawn. This is the method I have used in ghostscript. The code is probably simpler than a single thread version. Russell Lang gs...@gh... Ghostgum Software Pty Ltd http://www.ghostgum.com.au/ |