Re: Gnuplot version 5 release candidate

[Tatsuro M. <tma...@ya...>]

--- On Wed, 2014/5/21, Tatsuro MATSUOKA  wrote:

> --- On Wed, 2014/5/21, Tait wrote:
> > I don't see the windows binaries on SourceForge, but I did pull them
> > from Tatsuro's site, and the default wxt terminal behaves oddly, now.
> > When I load a script containing "set contour" and a plot or splot, the
> > plot window does not appear until after I move the mouse. Without the
> > "set contour", without the (s)plot, or when not from within a script,
> > the plot displays immediately.
> > 
> > To try it out, create a script:
> >     reset
> >     set contour
> >     plot x
> > 
> > then 'load "thatscript.gps"' from within gnuplot, without touching the
> > mouse. No plot or plot window is displayed. As soon as the mouse
> > moves, the window appears, with the plot as expected. The behavior is
> > repeatable, for me. Does anybody else see this as well?
> > 
> > 
> > Ethan A Merritt <sf...@us...> said (on 2014/05/19):
> > > A source tarball for the version 5.0-rc1 release candidate 
> > > is now publically accessible on SourceForge:...
> 
> Tait. Please confirm whether your operation works well on windows terminal.
> 
> I suspect that the change on 2014-01-04 is related to that you pointed out.
> I have aware the phenomenon that all .dem on wxt terminal on windows does not work correctly. Shigeharu Takeno also pointed out that point in the private mail to me.
> 
> The change below perhaps related to the phenomena that you have met.
> *************************************************************************
> 2014-01-04  Bastian Maerkisch  <bma...@we...>
> 
>     * src/win/wcommon.h src/win/wgdiplus.cpp|h src/win/wgnuplib.h
>     src/win/wgraph.c src/win/resourc.h term/win.trm:  New (optional)
>     variant of the windows terminal backend which draws using the GDI+ API
>     whenever possible. This is much faster in some cases than the old
>     backend which switches between GDI and GDI+ to support antialiasing
>     and RGBA colors. Images are drawn using GDI since GDI+ always uses some
>     sort of interpolation when scaling images. Enhanced text is currently
>     still drawn using GDI. Adjacent polygons of the same color are merged
>     in order to avoid "seams" between them caused by antialiasing. See also
>     Bug #1096.
> 
>     * src/term_api.h src/graphics (plot_image_or_update_axes):  Wrap
>     the fallback image output with term->layer() commands using
>     TERM_LAYER_BEGIN_IMAGE and TERM_LAYER_END_IMAGE. This can be
>     used by terminals to optimize output.
> 
>     * src/win/wgraph.c (drawgraph):  Move GDI image drawing code from
>     drawgraph() to a new routine draw_image().
> 
>     * src/command.c src/fit.c|h src/plot.c|h src/term.c src/win/wgraph.c 
>     src/win/winmain.c src/win/wtext.c term/win.trm:  Handle Ctrl-C
>     asynchronously on Windows (GUI and console mode). This is done by
>     setting ctrlc_flag and testing it in check_for_mouse_event(). Thus,
>     scripts etc. can now finally be interrupted by pressing Ctrl-C in
>     console mode gnuplot or Ctrl-Break in wgnuplot.
> 
>     * src/win/winmain.c (ConsoleGetch):  Remap Shift-Tab key-code in
>     console mode, too.
> 
> ***********************************************************************
> The above change solves the CTRL+C issue on gnuplot on windows for a long term.
> The change seems to be well on windows terminal but not be well on wxt terminal.
> 
> To confirm my assumption, I have to downgrade the cvs source but I have not tried yet.  
> 
> Please give me a little bit time to confirm that the change above is an origin of the fault on the wxt terminal.

My assumption is wrong.  Using the cvs source dated 2014-01-02, the same phenomena occur on the wxt terminal for windows.

Perhaps it will take time which change is the origin this fault.

Tatsuro