[fptex] Re: fptex digest, Vol 1 #133 - 2 msgs

[Frans Goddijn]

I also have a W2000 machine and a flat screen (Samsung SyncMaster 151s) and
WinEdt with fpTeX but I don't have that delay at all. But my TeX runs in a
small window instead of a full screen, that might be the difference. I use
WinEdt 5.3

Interesting how this seems to be specifically a Winedt issue and on the
WinEdt list one often reads general LaTeX questions :-)

----- Original Message -----
From: "John Frampton" <jframpto@lynx.dac.neu.edu>

> There is another issue, which I am sure other people have run
> into.  On my computer, a new 1.6GHz Windows 2000 machine,
> invoking Tex from WinEdt causes the screen to go blank for almost
> 2 seconds, before the output of Tex appears.  There is another 2
> seconds of blank screen on the way back to WinEdt.  I think the
> problem is that switching from digital output for my flatscreen
> monitor (which Windows uses) to line oriented output from a DOS
> program is a big deal for the graphics card (or whatever).  If
> output from fptex could be sent through a window, the whole
> operation would be much smoother.
>
> The problem is analagous to the problem of invoking cmd.exe from
> the desktop. If it is done through a shortcut with output
> specified to be a window, rather than full-screen, the process is
> instant and smooth.  If full-screen output is specified, or if
> cmd.exe is called directly, then there is the 2 second blank
> screen both on entering and leaving.  It must be possible to
> invoke the cmd.exe interpreter with a parameter to specify a
> window output.  That must be what the shortcut does.  I will try
> to look in a Windows manual and find out how the appropriate
> parameters are passed to cmd.exe, but if anyone knows the
> solution, it would be helpful to me.
>
> Thanks,
> John Frampton
>
> _______________________________________________
> fptex mailing list
> fptex@tug.org
> http://tug.org/mailman/listinfo/fptex