gnuplot-beta — Developers and beta testers of new gnuplot code

Gnuplot plans: the start of version 6

[Ethan A M. <me...@uw...>]

I have pushed a new branch-6-0-stable to the git repository for
for development and eventual release of a version 6 gnuplot.
Further development of version 5 can continue in the main branch
(5.5) although I don't foresee much happening on that side.


Current state of branch-6-0-stable
----------------------------------
So far the changes from the 5.5 branch are mostly to the documentation.
The introductory sections describing new and changed features are
revised to focus on version 6;  several pages of text about "new" things
in version 5 have greatly trimmed back to a summary.
Perhaps these could be removed altogether.

I have no set timeline for a version 6 release.
As a point of reference, transition from version 4->5 took most of a
year back in 2014 and went through three release candidates before
version 5 was announced.

What needs to be done for a version 6?
--------------------------------------
I have started a list of choices that should be made.
I will post them to the mailing list one at a time for separate discussion.
Each one might end in decision to leave things as they are
in version 5 (not much work required) or to make a change
not appropriate in the context of an update to a "stable'
version 5.


What about version 5?
---------------------
I expect to package 5.4.6 in the first part of 2023, with the
usual sort of bug fixes and small additions to the current stable
branch.  Beyond that I do not know.  Depending on how long it takes
to test and revise release candidates for version 6, there might
be additional updates to 5.4.

Is the next stable release 6.0.0?

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

https://sourceforge.net/p/gnuplot/gnuplot-main/ci/0b5abbcf6dd98e30ac422333f051d7f32063251e/
The stable branch for version 6.0 was started.

Is the next stable release 6.0.0?

The sharpen feature seems to be implemented only to branch-6-0-stable but not to the development branch.

Tatsuro

Re: pngcairo terminal: "crop" does different things if background color is specified

[Dima K. <gn...@di...>]

Ethan A Merritt <me...@uw...> writes:

> Fixed now.

Thank you very much, Ethan!

Re: pngcairo terminal: "crop" does different things if background color is specified

[Ethan A M. <me...@uw...>]

On Monday, 28 November 2022 22:55:34 PST Ethan A Merritt wrote:
> On Monday, 28 November 2022 21:52:19 PST Dima Kogan wrote:
> > Hi. I'm using a recent gnuplot shipped in Debian, and I'm seeing an odd
> > behavior.
> >
> > I make a trivial .png plot like so:
> >
> >   set terminal pngcairo size 1024,768 notransparent crop
> >   set output "/tmp/tst.png"
> >   plot x
> >
> > Because of the "crop", the resulting image size is a bit smaller than
> > requested. "file /tmp/tst.png" says:
> >
> >   tst.png: PNG image data, 995 x 751, 8-bit/color RGB, non-interlaced
>
> > But if I change the background color by adding to the end of the "set
> > terminal" command:
> >
> >   background "#e8dfd0"
> >
> > then I get a full 1024x768 image. This shouldn't happen: the background
> > color should not be doing anything to the image size.
>
> True.  The current code seems to only test for transparent/non-transparent.
> It should also test for background/non-background.
>
> That's a fixable bug specific to cairopng.

Fixed now.


        Ethan

Re: pngcairo terminal: "crop" does different things if background color is specified

[Ethan A M. <me...@uw...>]

On Monday, 28 November 2022 21:52:19 PST Dima Kogan wrote:
> Hi. I'm using a recent gnuplot shipped in Debian, and I'm seeing an odd
> behavior.
>
> I make a trivial .png plot like so:
>
>   set terminal pngcairo size 1024,768 notransparent crop
>   set output "/tmp/tst.png"
>   plot x
>
> Because of the "crop", the resulting image size is a bit smaller than
> requested. "file /tmp/tst.png" says:
>
>   tst.png: PNG image data, 995 x 751, 8-bit/color RGB, non-interlaced
>
> Not entirely sure why it's cropping anything here, but that's how it is.

It crops all whitespace around the edges, so of course it is smaller.


> But if I change the background color by adding to the end of the "set
> terminal" command:
>
>   background "#e8dfd0"
>
> then I get a full 1024x768 image. This shouldn't happen: the background
> color should not be doing anything to the image size.

True.  The current code seems to only test for transparent/non-transparent.
It should also test for background/non-background.

That's a fixable bug specific to cairopng.

You could still clip by filtering the output through an external
tool like ImageMagick.


        Ethan


--
Ethan A Merritt
Biomolecular Structure Center,  K-428 Health Sciences Bldg
MS 357742,   University of Washington, Seattle 98195-7742

pngcairo terminal: "crop" does different things if background color is specified

[Dima K. <gn...@di...>]

Hi. I'm using a recent gnuplot shipped in Debian, and I'm seeing an odd
behavior.

I make a trivial .png plot like so:

  set terminal pngcairo size 1024,768 notransparent crop
  set output "/tmp/tst.png"
  plot x

Because of the "crop", the resulting image size is a bit smaller than
requested. "file /tmp/tst.png" says:

  tst.png: PNG image data, 995 x 751, 8-bit/color RGB, non-interlaced

Not entirely sure why it's cropping anything here, but that's how it is.
But if I change the background color by adding to the end of the "set
terminal" command:

  background "#e8dfd0"

then I get a full 1024x768 image. This shouldn't happen: the background
color should not be doing anything to the image size.

Thanks!

R: Is there any explanation for function block?

[Franco <fra...@ng...>]

Dear Professor Merritt

 

Many thanks for your excellent work and for the commitment in keeping Gnuplot up to date.

This page   https://www.sixsigmain.it/Blog_AEX.html

contains videos of a Gnuplot application (*) perfectly operational both on 5.4.x and on all 5.5.x (released this year).

I am sure that with this new feature, the code will be even more simplified. 

 

Franco

 

(*) Given your personal background, the videos will be easy to understand.

 

Da: Ethan A Merritt [mailto:me...@uw...] 
Inviato: sabato 15 ottobre 2022 19:06
A: Tatsuro MATSUOKA <tma...@ya...>
Cc: beta <gnu...@li...>
Oggetto: Re: Is there any explanation for function block?

 

Function blocks are implemented in a new branch that I have not yet committed.  The "local" property for variables was part of that branch but is useful already by itself, so I added it first.  The idea of function blocks is similar to datablocks, except that the text in the block is executed as a function rather than used as data. See earlier discussion attached to Bug #2547 https://sourceforge.net/p/gnuplot/bugs/2547/ and Feature Request 521  https://sourceforge.net/p/gnuplot/feature-requests/521/

 

Here is a draft section of the documentation for the new branch.  It still has a few rough edges, but I expect to merge it in the next week or so.

 

The `function` command signals the definition of a here-document containing 
a named block of gnuplot code that can be called as a function. 
As with data blocks, the name of a function block must begin with a '$'. 
Up to nine named parameters may be specified as part of the definition. 
These names may be used inside the function block as local variables. 
See `local` and `scope`. 

Once the function block is defined, you can invoke it by name anywhere

that a normal function could be used. 

Example: 
     function $sinc(arg) << EOF 
         if (arg == 0) { return 1.0 } 
         return sin(arg) / arg 
     EOF 

     gnuplot> plot $sinc(x) with lines title "sinc(x) as a function block" 

It is not necessary to specify a list of named arguments to a function block 
at the time it is declared. Arguments to the function passed from the command 
line can be accessed inside the function block as ARGV[1] etc, as would be the 
case for a `call` command.  See `ARGV`.  This allows defining a function 
block that can operate on a variable number of arguments.

 

The primary motivation for function block support is to allow definition of 
complicated functions directly in gnuplot.  Execution is of course slower 
than if the same function were coded directly in C or Fortran, but this is 
acceptable for many purposes.  If execution speed matters then the function 
can be implemented later as a plugin instead (see `plugins`). 

A non-trivial example of using function blocks to implement and plot 
a 15-term Lancosz approximation for the complex lngamma function is 
provided in the demo collection as 
^ <a href="http://www.gnuplot.info/demo_5.5/function_block.html"> 
     function_block.dem 
^ </a> 
The function block implementation is slower by a factor of roughly 25 compared 
to the built-in lnGamma function using the same algorithm coded directly in C. 
Nevertheless it is still fast enough for 3D interactive rotation.



 

On Fri, Oct 14, 2022 at 11:40 PM Tatsuro MATSUOKA via gnuplot-beta <gnu...@li... <mailto:gnu...@li...> > wrote:

I found the option --enable-function-blocks is implemented to the development branch.

Is there any explanation for the function block?

Tatsuro



_______________________________________________
gnuplot-beta mailing list
gnu...@li... <mailto:gnu...@li...> 
Membership management via: https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/gnuplot-beta__;!!K-Hz7m0Vt54!i-6R1LQEUOPOg9GRf_E7o8MGHFaWf_cXfyDWcdAF0zC6EGVNvS-Yx-0U-vtqT0DdmY1ubirVqocHtClLZsrDvB2_cxG8J_Z9dvdW$ <https://urldefense.com/v3/__https:/lists.sourceforge.net/lists/listinfo/gnuplot-beta__;!!K-Hz7m0Vt54!i-6R1LQEUOPOg9GRf_E7o8MGHFaWf_cXfyDWcdAF0zC6EGVNvS-Yx-0U-vtqT0DdmY1ubirVqocHtClLZsrDvB2_cxG8J_Z9dvdW$>   




 

-- 

Ethan A Merritt 
Biomolecular Structure Center,  K-428 Health Sciences Bldg 
MS 357742,   University of Washington, Seattle 98195-7742

Re: Is there any explanation for function block?

[Ethan A M. <me...@uw...>]

Function blocks are implemented in a new branch that I have not yet
committed.  The "local" property for variables was part of that branch but
is useful already by itself, so I added it first.  The idea of function
blocks is similar to datablocks, except that the text in the block is
executed as a function rather than used as data. See earlier discussion
attached to Bug #2547 https://sourceforge.net/p/gnuplot/bugs/2547/ and
Feature Request 521  https://sourceforge.net/p/gnuplot/feature-requests/521/

Here is a draft section of the documentation for the new branch.  It still
has a few rough edges, but I expect to merge it in the next week or so.

The `function` command signals the definition of a here-document containing
a named block of gnuplot code that can be called as a function.
As with data blocks, the name of a function block must begin with a '$'.
Up to nine named parameters may be specified as part of the definition.
These names may be used inside the function block as local variables.
See `local` and `scope`.

Once the function block is defined, you can invoke it by name anywhere
that a normal function could be used.

Example:
     function $sinc(arg) << EOF
         if (arg == 0) { return 1.0 }
         return sin(arg) / arg
     EOF

     gnuplot> plot $sinc(x) with lines title "sinc(x) as a function block"

It is not necessary to specify a list of named arguments to a function
block
at the time it is declared. Arguments to the function passed from the
command
line can be accessed inside the function block as ARGV[1] etc, as would be
the
case for a `call` command.  See `ARGV`.  This allows defining a function
block that can operate on a variable number of arguments.

The primary motivation for function block support is to allow definition of
complicated functions directly in gnuplot.  Execution is of course slower
than if the same function were coded directly in C or Fortran, but this is
acceptable for many purposes.  If execution speed matters then the function
can be implemented later as a plugin instead (see `plugins`).

A non-trivial example of using function blocks to implement and plot
a 15-term Lancosz approximation for the complex lngamma function is
provided in the demo collection as
^ <a href="http://www.gnuplot.info/demo_5.5/function_block.html">
     function_block.dem
^ </a>
The function block implementation is slower by a factor of roughly 25
compared
to the built-in lnGamma function using the same algorithm coded directly in
C.
Nevertheless it is still fast enough for 3D interactive rotation.



On Fri, Oct 14, 2022 at 11:40 PM Tatsuro MATSUOKA via gnuplot-beta <
gnu...@li...> wrote:

> I found the option --enable-function-blocks is implemented to the
> development branch.
>
> Is there any explanation for the function block?
>
> Tatsuro
>
>
>
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via:
> https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/gnuplot-beta__;!!K-Hz7m0Vt54!i-6R1LQEUOPOg9GRf_E7o8MGHFaWf_cXfyDWcdAF0zC6EGVNvS-Yx-0U-vtqT0DdmY1ubirVqocHtClLZsrDvB2_cxG8J_Z9dvdW$
>
>


-- 
Ethan A Merritt
Biomolecular Structure Center,  K-428 Health Sciences Bldg
MS 357742,   University of Washington, Seattle 98195-7742

Is there any explanation for function block?

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

I found the option --enable-function-blocks is implemented to the development branch.

Is there any explanation for the function block?

Tatsuro

Re: Gnuplot version 5.4.5 release

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

I have uploaded Windows binary packages.

https://sourceforge.net/projects/gnuplot/files/gnuplot/5.4.5/gp545-win64-mingw.exe/download Windows 64bit binary self-installer
https://sourceforge.net/projects/gnuplot/files/gnuplot/5.4.5/gp545-win64-mingw.7z Windows 64bit complete package

Tatsuro

> ----- Original Message -----
> 
> From: "Ethan A Merritt" <me...@uw...>
> To: "gnu...@li..." <gnu...@li...>
> Date: 2022/10/03 月 02:31
> Subject: Gnuplot version 5.4.5 release
> 
> 
> Release 5.4.5 is now available for download from SourceForge
> 
> Source tarball
> 
>     https://sf.net/projects/gnuplot/files/gnuplot/5.4.5/gnuplot-5.4.5.tar.gz
> 
> This release fixes a regression affecting 5.4.4 (only) that caused
> string->integer
> type promotion to incorrectly interpret leading '0' characters as indicating an
> octal number.  For example in extracting sequence numbers from file names
> run_001.dat through run_010.data would fail on run_009.dat ('9' is not a legal
> octal character) and file_010.dat would yield 8 rather than 10.
> 
> This release also fixes mousing the Windows qt terminal during a "pause"
> command.
> 
> There are two new features back-ported from 5.5;  both are illustrated
> in this plot from the development version demo collection.
>    https://gnuplot.sourceforge.net/demo_5.5/histogram_colors.html
> 
> Release Notes date:  28-Sep-2022
> 
> Changes in 5.4.5
> ================
> * NEW    "set key offset <dx>, <dy>" tweaks placement of the key
> * NEW    data-driven histogram colors (variable color from extra using column)
> * CHANGE re-order drawing 3D labels to come after pm3d depthorder surfaces
> * CHANGE hpgl: add terminal option "fontscale <value>"
> * CHANGE for nonuniform matrix data, column(0) returns linear position in matrix
> * CHANGE set pointintervalbox 0 disables drawing the background box   Bug #2544
> * FIX    svg: hypertext font handling
> * FIX    track columnheaders of multiple data blocks in a single file Bug #2538
> * FIX    Clean up positioning of polar border, raxis, and theta tics  Bug #2130
> * FIX    Autoscaling of logscaled raxis
> * FIX    memory corruption if a small plot structure is recycled      Bug #2550
> * FIX    regression in 5.4.4 - promotion of string to integer should
>             should not assume that a leading 0 means octal
>   Bug #2551
> * FIX    Windows qt: "pause -1" should not block mousing              Bug #2549
> * FIX    invalid free of active datablock
> 
> 
> 
> 
>         Ethan
> 
> 
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> 

Gnuplot version 5.4.5 release

[Ethan A M. <me...@uw...>]

Release 5.4.5 is now available for download from SourceForge

Source tarball

    https://sf.net/projects/gnuplot/files/gnuplot/5.4.5/gnuplot-5.4.5.tar.gz

This release fixes a regression affecting 5.4.4 (only) that caused
string->integer
type promotion to incorrectly interpret leading '0' characters as indicating an
octal number.  For example in extracting sequence numbers from file names
run_001.dat through run_010.data would fail on run_009.dat ('9' is not a legal
octal character) and file_010.dat would yield 8 rather than 10.

This release also fixes mousing the Windows qt terminal during a "pause"
command.

There are two new features back-ported from 5.5;  both are illustrated
in this plot from the development version demo collection.
   https://gnuplot.sourceforge.net/demo_5.5/histogram_colors.html

Release Notes date:  28-Sep-2022

Changes in 5.4.5
================
* NEW    "set key offset <dx>, <dy>" tweaks placement of the key
* NEW    data-driven histogram colors (variable color from extra using column)
* CHANGE re-order drawing 3D labels to come after pm3d depthorder surfaces
* CHANGE hpgl: add terminal option "fontscale <value>"
* CHANGE for nonuniform matrix data, column(0) returns linear position in matrix
* CHANGE set pointintervalbox 0 disables drawing the background box   Bug #2544
* FIX    svg: hypertext font handling
* FIX    track columnheaders of multiple data blocks in a single file Bug #2538
* FIX    Clean up positioning of polar border, raxis, and theta tics  Bug #2130
* FIX    Autoscaling of logscaled raxis
* FIX    memory corruption if a small plot structure is recycled      Bug #2550
* FIX    regression in 5.4.4 - promotion of string to integer should
            should not assume that a leading 0 means octal
  Bug #2551
* FIX    Windows qt: "pause -1" should not block mousing              Bug #2549
* FIX    invalid free of active datablock




        Ethan

Re: early release of version 5.4.5 (please test)

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

Gnuplot startup
On 5.4.5 Beta
        G N U P L O T
        Version 5.4.5 patchlevel 5    last modified 2022-09-22On 5.4.4
        G N U P L O T
        Version 5.4 patchlevel 4    last modified 2022-07-10

5.4.5 patchlevel 5  ->  5.4 patchlevel 5

Tatsuro

> ----- Original Message -----
>  
> From: "Tatsuro MATSUOKA via gnuplot-beta" <gnu...@li...>
> To: "me...@uw..." <me...@uw...>; "gnu...@li..." <gnu...@li...>
> Date: 2022/09/26 月 09:05
> Subject: Re: early release of version 5.4.5 (please test)
> 
> 
> Thank you for your efforts.
> 
> I build gnuplot-5.4.5 beta on Windows and confirmed that bug #2549 and bug #2551 were fixed.
> 
> Tatsuro 
> 
> > ----- Original Message -----
> > 
> > From: "Ethan A Merritt" <me...@uw...>
> > To: "gnu...@li..." <gnu...@li...>
> > Date: 2022/09/26 月 02:55
> > Subject: early release of version 5.4.5 (please test)
> > 
> > 
> > I have uploaded a testing copy of a version 5.4.5 release to the "testing"
> > area on SourceForge:
> >   https://sourceforge.net/projects/gnuplot/files/gnuplot/testing/
> > 
> > The reason for an earlier than usual release is to correct a regression
> > that affected version 5.4.4 (only) and to provide a fix for mousing in
> > the Windows qt terminal.
> > 
> > The regression in 5.4.4 caused string->integer type promotion to
> > incorrectly interpret leading '0' characters as indicating an octal number.
> > For example in extracting sequence numbers from filenames "run_009.dat",
> > "run_010.dat", the first conversion would fail ('9' is not a legal octal
> > character) and the second would yield 8 rather than 10.
> > 
> > My thought is to leave a week for testing and then announce the actual
> > release at the end of this month.
> > 
> > Changes in 5.4.5
> > ================
> > * NEW    "set key offset <dx>, <dy>" tweaks placement of the key
> > * NEW    data-driven histogram colors (variable color from extra using column)
> > * CHANGE re-order drawing 3D labels to come after pm3d depthorder surfaces
> > * CHANGE hpgl: add terminal option "fontscale <value>"
> > * CHANGE for nonuniform matrix data, column(0) returns linear position in matrix
> > * CHANGE set pointintervalbox 0 disables drawing the background box   Bug #2544
> > * FIX    svg: hypertext font handling
> > * FIX    track columnheaders of multiple data blocks in a single file Bug #2538
> > * FIX    Clean up positioning of polar border, raxis, and theta tics  Bug #2130
> > * FIX    Autoscaling of logscaled raxis
> > * FIX    memory corruption if a small plot structure is recycled      Bug #2550
> > * FIX    regression in 5.4.4 - promotion of string to integer should
> >          should not assume that a leading 0 means octal               Bug #2551
> > * FIX    Windows qt: "pause -1" should not block mousing              Bug #2549
> > 
> >         Ethan
> > 
> > 
> > _______________________________________________
> > gnuplot-beta mailing list
> > gnu...@li...
> > Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> > 
> 
> 
> 
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> 

Re: early release of version 5.4.5 (please test)

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

Thank you for your efforts.

I build gnuplot-5.4.5 beta on Windows and confirmed that bug #2549 and bug #2551 were fixed.

Tatsuro 

> ----- Original Message -----
> 
> From: "Ethan A Merritt" <me...@uw...>
> To: "gnu...@li..." <gnu...@li...>
> Date: 2022/09/26 月 02:55
> Subject: early release of version 5.4.5 (please test)
> 
> 
> I have uploaded a testing copy of a version 5.4.5 release to the "testing"
> area on SourceForge:
>   https://sourceforge.net/projects/gnuplot/files/gnuplot/testing/
> 
> The reason for an earlier than usual release is to correct a regression
> that affected version 5.4.4 (only) and to provide a fix for mousing in
> the Windows qt terminal.
> 
> The regression in 5.4.4 caused string->integer type promotion to
> incorrectly interpret leading '0' characters as indicating an octal number.
> For example in extracting sequence numbers from filenames "run_009.dat",
> "run_010.dat", the first conversion would fail ('9' is not a legal octal
> character) and the second would yield 8 rather than 10.
> 
> My thought is to leave a week for testing and then announce the actual
> release at the end of this month.
> 
> Changes in 5.4.5
> ================
> * NEW    "set key offset <dx>, <dy>" tweaks placement of the key
> * NEW    data-driven histogram colors (variable color from extra using column)
> * CHANGE re-order drawing 3D labels to come after pm3d depthorder surfaces
> * CHANGE hpgl: add terminal option "fontscale <value>"
> * CHANGE for nonuniform matrix data, column(0) returns linear position in matrix
> * CHANGE set pointintervalbox 0 disables drawing the background box   Bug #2544
> * FIX    svg: hypertext font handling
> * FIX    track columnheaders of multiple data blocks in a single file Bug #2538
> * FIX    Clean up positioning of polar border, raxis, and theta tics  Bug #2130
> * FIX    Autoscaling of logscaled raxis
> * FIX    memory corruption if a small plot structure is recycled      Bug #2550
> * FIX    regression in 5.4.4 - promotion of string to integer should
>          should not assume that a leading 0 means octal               Bug #2551
> * FIX    Windows qt: "pause -1" should not block mousing              Bug #2549
> 
>         Ethan
> 
> 
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> 

early release of version 5.4.5 (please test)

[Ethan A M. <me...@uw...>]

I have uploaded a testing copy of a version 5.4.5 release to the "testing"
area on SourceForge:
  https://sourceforge.net/projects/gnuplot/files/gnuplot/testing/

The reason for an earlier than usual release is to correct a regression
that affected version 5.4.4 (only) and to provide a fix for mousing in
the Windows qt terminal.

The regression in 5.4.4 caused string->integer type promotion to
incorrectly interpret leading '0' characters as indicating an octal number.
For example in extracting sequence numbers from filenames "run_009.dat",
"run_010.dat", the first conversion would fail ('9' is not a legal octal
character) and the second would yield 8 rather than 10.

My thought is to leave a week for testing and then announce the actual
release at the end of this month.

Changes in 5.4.5
================
* NEW    "set key offset <dx>, <dy>" tweaks placement of the key
* NEW    data-driven histogram colors (variable color from extra using column)
* CHANGE re-order drawing 3D labels to come after pm3d depthorder surfaces
* CHANGE hpgl: add terminal option "fontscale <value>"
* CHANGE for nonuniform matrix data, column(0) returns linear position in matrix
* CHANGE set pointintervalbox 0 disables drawing the background box   Bug #2544
* FIX    svg: hypertext font handling
* FIX    track columnheaders of multiple data blocks in a single file Bug #2538
* FIX    Clean up positioning of polar border, raxis, and theta tics  Bug #2130
* FIX    Autoscaling of logscaled raxis
* FIX    memory corruption if a small plot structure is recycled      Bug #2550
* FIX    regression in 5.4.4 - promotion of string to integer should
         should not assume that a leading 0 means octal               Bug #2551
* FIX    Windows qt: "pause -1" should not block mousing              Bug #2549

        Ethan

Re: New gnuplot subsystem "watchpoints"

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

The output of demo of watchpoints (watchpoints.dem) was prepared in pdf file and the file was uploaded to 
http://tmacchant33.starfree.jp/Files/watchpoits.pdf

Tatsuro

> ----- Original Message -----
> 
> From: "Tatsuro MATSUOKA via gnuplot-beta" <gnu...@li...>
> To: "Ethan A Merritt" <me...@uw...>; "gnu...@li..." <gnu...@li...>
> Date: 2022/09/07 水 23:48
> Subject: Re: New gnuplot subsystem "watchpoints"
> 
> 
> I have made windows and cygwin binary packages with "watchpoints" and uploaded the below.
> http://tmacchant33.starfree.jp/gnuplot_bin.html
> 
> Tatsuro
> 
> > ----- Original Message -----
> > 
> > From: "Ethan A Merritt" <me...@uw...>
> > To: "gnu...@li..." <gnu...@li...>
> > Date: 2022/09/06 火 16:03
> > Subject: New gnuplot subsystem "watchpoints"
> > 
> > 
> > This is a project I started a couple of years ago.
> > I think it is now ready for general testing and use, so I have
> > added it to the development branch with a configuration option
> > 
> >     configure --enable-watchpoints
> > 
> > The "help" text is below:
> > 
> >  Syntax:
> >        plot FOO watch {x|y|z|F(x,y)} = <value>
> >        plot FOO watch mouse
> > 
> >        set style watchpoints nolabels
> >        set style watchpoints label <label-properties>
> > 
> >        unset style watchpoints      # return to default style
> > 
> >        show watchpoints    # summarizes all watches from previous plot command
> > 
> >  A watchpoint is a target value for the x, y, or z coordinate or for a function
> >  f(x,y).  Each watchpoint is attached to a single plot within a `plot` command.
> >  Watchpoints are tracked only for styles `with lines` and `with linespoints`.
> >  Every component line segment of that plot is checked against all watchpoints
> >  attached the plot to see whether one or more of the watchpoint targets is
> >  satisfied at a point along that line segment. A list of points that satisfy the
> >  the target condition ("hits") is accumulated as the plot is drawn.
> > 
> >  For example, if there is a watchpoint with a target y=100, each line segment
> >  is checked to see if the y coordinates of the two endpoints bracket the target
> >  y value.  If so then some point [x,y] on the line segment satisfies the target
> >  condition y = 100 exactly.  This target point is then found by linear
> >  interpolation or by iterative bisection.
> > 
> >  Watchpoints within a single plot command are numbered successively.
> >  More than one watchpoint per plot component may be specified.
> >  Example:
> >       plot DATA using 1:2 smooth cnormal watch y=0.25 watch y=0.5 watch y=0.75
> > 
> >  Watchpoint hits for each targets in the previous plot command are stored in
> >  named arrays WATCH_n.  You can also display a summary of all watchpoint hits
> >  from the previous plot command;  see `show watchpoints`.
> > 
> >       gnuplot> show watchpoints
> >       Plot title:     "DATA using 1:2 smooth cnormal"
> >         Watch 1 target y = 0.25         (1 hits)
> >                 hit 1   x 49.7  y 0.25
> >         Watch 2 target y = 0.5          (1 hits)
> >                 hit 1   x 63.1  y 0.5
> >         Watch 3 target y = 0.75         (1 hits)
> >                 hit 1   x 67.8  y 0.75
> > 
> >  Smoothing: Line segments are checked as they are drawn.  For unsmoothed data
> >  plots this means a hit found by interpolation will lie exactly on a line
> >  segment connecting two data points.  If a data plot is smoothed, hits will
> >  lie on a line segment from the smoothed curve.  Depending on the quality
> >  of the smoothed fit, this may or may not be more accurate than the hit from
> >  the unsmoothed data.
> > 
> >  Accuracy: If the line segment was generated from a function plot, the exact
> >  value of x such that f(x) = y is found by iterative bisection.
> >  Otherwise the coordinates [x,y] are approximated by linear interpolation
> >  along the line segment.
> > 
> >  Using the current mouse x coordinate as a watch target generates a label
> >  that moves along the line of the plot tracking the horizontal position of
> >  the mouse.  This allows simultaneous readout of the y values of multiple
> >  plot lines in the same graph.  The appearance of the point indicating the
> >  current position and of the label can be modified by `set style watchpoint`
> >  and `set style textbox`
> > 
> >  Example:
> > 
> >       set style watchpoint labels point pt 6 ps 2 boxstyle 1
> >       set style textbox 1 lw 0.5 opaque
> >       plot for [i=1:N] "file.dat" using 1:(column(i)) watch mouse
> > 
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > gnuplot-beta mailing list
> > gnu...@li...
> > Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> > 
> 
> 
> 
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> 

Re: New gnuplot subsystem "watchpoints"

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

I have made windows and cygwin binary packages with "watchpoints" and uploaded the below.
http://tmacchant33.starfree.jp/gnuplot_bin.html

Tatsuro

> ----- Original Message -----
> 
> From: "Ethan A Merritt" <me...@uw...>
> To: "gnu...@li..." <gnu...@li...>
> Date: 2022/09/06 火 16:03
> Subject: New gnuplot subsystem "watchpoints"
> 
> 
> This is a project I started a couple of years ago.
> I think it is now ready for general testing and use, so I have
> added it to the development branch with a configuration option
> 
>     configure --enable-watchpoints
> 
> The "help" text is below:
> 
>  Syntax:
>        plot FOO watch {x|y|z|F(x,y)} = <value>
>        plot FOO watch mouse
> 
>        set style watchpoints nolabels
>        set style watchpoints label <label-properties>
> 
>        unset style watchpoints      # return to default style
> 
>        show watchpoints    # summarizes all watches from previous plot command
> 
>  A watchpoint is a target value for the x, y, or z coordinate or for a function
>  f(x,y).  Each watchpoint is attached to a single plot within a `plot` command.
>  Watchpoints are tracked only for styles `with lines` and `with linespoints`.
>  Every component line segment of that plot is checked against all watchpoints
>  attached the plot to see whether one or more of the watchpoint targets is
>  satisfied at a point along that line segment. A list of points that satisfy the
>  the target condition ("hits") is accumulated as the plot is drawn.
> 
>  For example, if there is a watchpoint with a target y=100, each line segment
>  is checked to see if the y coordinates of the two endpoints bracket the target
>  y value.  If so then some point [x,y] on the line segment satisfies the target
>  condition y = 100 exactly.  This target point is then found by linear
>  interpolation or by iterative bisection.
> 
>  Watchpoints within a single plot command are numbered successively.
>  More than one watchpoint per plot component may be specified.
>  Example:
>       plot DATA using 1:2 smooth cnormal watch y=0.25 watch y=0.5 watch y=0.75
> 
>  Watchpoint hits for each targets in the previous plot command are stored in
>  named arrays WATCH_n.  You can also display a summary of all watchpoint hits
>  from the previous plot command;  see `show watchpoints`.
> 
>       gnuplot> show watchpoints
>       Plot title:     "DATA using 1:2 smooth cnormal"
>         Watch 1 target y = 0.25         (1 hits)
>                 hit 1   x 49.7  y 0.25
>         Watch 2 target y = 0.5          (1 hits)
>                 hit 1   x 63.1  y 0.5
>         Watch 3 target y = 0.75         (1 hits)
>                 hit 1   x 67.8  y 0.75
> 
>  Smoothing: Line segments are checked as they are drawn.  For unsmoothed data
>  plots this means a hit found by interpolation will lie exactly on a line
>  segment connecting two data points.  If a data plot is smoothed, hits will
>  lie on a line segment from the smoothed curve.  Depending on the quality
>  of the smoothed fit, this may or may not be more accurate than the hit from
>  the unsmoothed data.
> 
>  Accuracy: If the line segment was generated from a function plot, the exact
>  value of x such that f(x) = y is found by iterative bisection.
>  Otherwise the coordinates [x,y] are approximated by linear interpolation
>  along the line segment.
> 
>  Using the current mouse x coordinate as a watch target generates a label
>  that moves along the line of the plot tracking the horizontal position of
>  the mouse.  This allows simultaneous readout of the y values of multiple
>  plot lines in the same graph.  The appearance of the point indicating the
>  current position and of the label can be modified by `set style watchpoint`
>  and `set style textbox`
> 
>  Example:
> 
>       set style watchpoint labels point pt 6 ps 2 boxstyle 1
>       set style textbox 1 lw 0.5 opaque
>       plot for [i=1:N] "file.dat" using 1:(column(i)) watch mouse
> 
> 
> 
> 
> 
> 
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> 

New gnuplot subsystem "watchpoints"

[Ethan A M. <me...@uw...>]

This is a project I started a couple of years ago.
I think it is now ready for general testing and use, so I have
added it to the development branch with a configuration option

    configure --enable-watchpoints

The "help" text is below:

 Syntax:
       plot FOO watch {x|y|z|F(x,y)} = <value>
       plot FOO watch mouse

       set style watchpoints nolabels
       set style watchpoints label <label-properties>

       unset style watchpoints      # return to default style

       show watchpoints    # summarizes all watches from previous plot command

 A watchpoint is a target value for the x, y, or z coordinate or for a function
 f(x,y).  Each watchpoint is attached to a single plot within a `plot` command.
 Watchpoints are tracked only for styles `with lines` and `with linespoints`.
 Every component line segment of that plot is checked against all watchpoints
 attached the plot to see whether one or more of the watchpoint targets is
 satisfied at a point along that line segment. A list of points that satisfy the
 the target condition ("hits") is accumulated as the plot is drawn.

 For example, if there is a watchpoint with a target y=100, each line segment
 is checked to see if the y coordinates of the two endpoints bracket the target
 y value.  If so then some point [x,y] on the line segment satisfies the target
 condition y = 100 exactly.  This target point is then found by linear
 interpolation or by iterative bisection.

 Watchpoints within a single plot command are numbered successively.
 More than one watchpoint per plot component may be specified.
 Example:
      plot DATA using 1:2 smooth cnormal watch y=0.25 watch y=0.5 watch y=0.75

 Watchpoint hits for each targets in the previous plot command are stored in
 named arrays WATCH_n.  You can also display a summary of all watchpoint hits
 from the previous plot command;  see `show watchpoints`.

      gnuplot> show watchpoints
      Plot title:     "DATA using 1:2 smooth cnormal"
        Watch 1 target y = 0.25         (1 hits)
                hit 1   x 49.7  y 0.25
        Watch 2 target y = 0.5          (1 hits)
                hit 1   x 63.1  y 0.5
        Watch 3 target y = 0.75         (1 hits)
                hit 1   x 67.8  y 0.75

 Smoothing: Line segments are checked as they are drawn.  For unsmoothed data
 plots this means a hit found by interpolation will lie exactly on a line
 segment connecting two data points.  If a data plot is smoothed, hits will
 lie on a line segment from the smoothed curve.  Depending on the quality
 of the smoothed fit, this may or may not be more accurate than the hit from
 the unsmoothed data.

 Accuracy: If the line segment was generated from a function plot, the exact
 value of x such that f(x) = y is found by iterative bisection.
 Otherwise the coordinates [x,y] are approximated by linear interpolation
 along the line segment.

 Using the current mouse x coordinate as a watch target generates a label
 that moves along the line of the plot tracking the horizontal position of
 the mouse.  This allows simultaneous readout of the y values of multiple
 plot lines in the same graph.  The appearance of the point indicating the
 current position and of the label can be modified by `set style watchpoint`
 and `set style textbox`

 Example:

      set style watchpoint labels point pt 6 ps 2 boxstyle 1
      set style textbox 1 lw 0.5 opaque
      plot for [i=1:N] "file.dat" using 1:(column(i)) watch mouse

Re: gnuplot latex documentation error with (MiKTeX 22.7)

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

Thank you for your reply.

I have been using MiKTeX for documentation of the LaTeX in the development branch of gnuplot.
I changed the TeX program from the MiKTeX to the TeXLive (+ghostscript) on the Msys2.
Now everything works as expected.

Tatsuro
 

> ----- Original Message -----
> 
> From: "Ethan A Merritt" <me...@uw...>
> To: "gnu...@li..." <gnu...@li...>
> Cc: "Tatsuro MATSUOKA" <tma...@ya...>
> Date: 2022/08/26 金 13:49
> Subject: Re: gnuplot latex documentation error with (MiKTeX 22.7)
> 
> 
> On Thursday, 25 August 2022 21:06:33 PDT Tatsuro MATSUOKA via gnuplot-beta wrote:
> > I have a situation to make gnuplot.pdf on windows (MinGW-w64) with MiKTeX 22.7
> > 
> > ************************************************************************************************.
> >   :
> >   :
> > LaTeX Warning: Reference `set label' on page 70 undefined on input line 6036.
> > 
> > 
> > LaTeX Warning: Reference `hypertext' on page 70 undefined on input line 6059.
> > 
> > 
> > 
> > pdfTeX warning: pdflatex.exe (file ./figure_labels2.pdf): PDF inclusion: found
> > PDF version <1.7>, but at most version <1.5> allowed
> > 
> > ! LaTeX Error: Unicode character ∙ (U+2219)
> >                not set up for use with LaTeX.
> 
> 
> U+2219 is \bullet in LaTeX.
> Perhaps the unicode support package included with MiKTeX 22.7 is incomplete?
> The file .../texmf-dist/tex/generic/unicode-data/UnicodeData.txt
> should contain a line
> 
> 2219;BULLET OPERATOR;Sm;0;ON;;;;;N;;;;;
> 
> 
> As a work-around, this thread 
>   https://tex.stackexchange.com/questions/598469/package-inputenc-error-unicode-character-%E2%88%99-u2219
> 
> suggests it may be possible to say
>     \usepackage{newunicodechar}
>     \newunicodechar{^^^^2219}{\cdot}
> 
> but I think it would be better to figure out what is wrong with the MiKTeX
> installation.
> 
> 
> 	Ethan
> 
> 
> 

Re: gplt_x11 ignores SIGINT and SIGTSTP. Why?

[Dima K. <gn...@di...>]

Ethan A Merritt <me...@uw...> writes:

>> But in addition to that, gnuplot complains on the terminal:
>> 
>>   qt_gnuplot exiting on read error
>
> I am pretty sure you can only get that error if there is a mismatch
> between the gnuplot version and the gnuplot_qt version. It means that
> one of the commands set via the pipe from gnuplot to gnuplot_x11 is
> not recognized.

Good tip. It was calling /usr/bin/gnuplot, and setting the PATH made it
work. It maybe should fail more gracefully, and anybody actually using
this as a Qt widget would need to make it more robust. It's a good
starting point, though.

Re: gplt_x11 ignores SIGINT and SIGTSTP. Why?

[Ethan A M. <me...@uw...>]

On Saturday, 3 September 2022 18:39:19 PDT Dima Kogan wrote:
> Ethan A Merritt <me...@uw...> writes:
> 
> > Do you have the option of logging in with a different window manager?
> > I normally us Plasma, which is maximally compatible with Qt, but I just
> > checked with an IceWM setup and it works fine there too.
> 
> This would be a good test, yes. I just tried on another box. I tried
> with both my tiling WM (notion) and an old "normal" WM (twm). Both have
> the same broken behavior as before. But in addition to that, gnuplot
> complains on the terminal:
> 
>   qt_gnuplot exiting on read error

I am pretty sure you can only get that error if there is a mismatch
between the gnuplot version and the gnuplot_qt version.
It means that one of the commands set via the pipe from gnuplot
to gnuplot_x11 is not recognized.

	Ethan

Re: gplt_x11 ignores SIGINT and SIGTSTP. Why?

[Dima K. <gn...@di...>]

Ethan A Merritt <me...@uw...> writes:

> Do you have the option of logging in with a different window manager?
> I normally us Plasma, which is maximally compatible with Qt, but I just
> checked with an IceWM setup and it works fine there too.

This would be a good test, yes. I just tried on another box. I tried
with both my tiling WM (notion) and an old "normal" WM (twm). Both have
the same broken behavior as before. But in addition to that, gnuplot
complains on the terminal:

  qt_gnuplot exiting on read error

This sounds fatal, but isn't: after a few minutes a single qt plot
window does still pop up, as before.

Re: gplt_x11 ignores SIGINT and SIGTSTP. Why?

[Ethan A M. <me...@uw...>]

On Saturday, 3 September 2022 16:47:18 PDT Dima Kogan wrote:
> Ethan A Merritt <me...@uw...> writes:
> 
> >> I just tried it, and it doesn't work right for me. The embed_example
> >> program builds. Running it pops up a window that disappears immediately.
> >> Then I get the shell prompt back implying that the embed_example
> >> application has exited. BUT it keeps running in the background
> >> apparently. And I do get a qt window with a plot maybe a minute later.
> >> Sometimes. Sometimes the background process just exits after a few
> >> minutes without showing me a plot.
> >
> > I cannot explain any of that.  It works normally for me here.
> > A qt window pops up immediately with four embedded gnuplot widgets
> > and a text pane.  Output from gnuplot appears in the text pane.
> > The demo replots to one of the widgets every second or so and
> > continues to do so until I close the window or hit Ctrl-C in the
> > controlling terminal.   No zombies either :-)
> 
> Must be nice :)
> 
> I just tried it again. Grabbed fresh sources from git. Rebuilt from
> scratch. Same broken behavior consistently. 

Do you have the option of logging in with a different window manager?
I normally us Plasma, which is maximally compatible with Qt, but I just
checked with an IceWM setup and it works fine there too.

	Ethan



> Some things that could be a
> problem that weren't:
> 
> - I have in my ~/.gnuplot: "set terminal x11 noenhanced". A
>   gnuplot-based Qt widget shouldn't care. It's not clear if it does or
>   doesn't, since taking that away doesn't fix it
> 
> - I'm using a tiling window manager. This constrains the window
>   geometry. So fresh windows are resized immediately after they come up.
>   This tickles bugs in some applications (like the wxt terminal, by the
>   way). It's not the problem here, though: turning off the tiling
>   behavior doesn't fix it.
> 
> - The outboard driver could be using the system gnuplot_qt instead of
>   the just-built one. Setting the GNUPLOT_DRIVER_DIR to point to the
>   local copy doesn't fix it.
> 
> I can help debug, if you're interested in looking into it. I'm doing
> other things at the moment, though, so not going to dig into this myself
> for now.
> 


-- 
Ethan A Merritt
Biomolecular Structure Center,  K-428 Health Sciences Bldg
MS 357742,   University of Washington, Seattle 98195-7742

Re: gplt_x11 ignores SIGINT and SIGTSTP. Why?

[Dima K. <gn...@di...>]

Ethan A Merritt <me...@uw...> writes:

>> I just tried it, and it doesn't work right for me. The embed_example
>> program builds. Running it pops up a window that disappears immediately.
>> Then I get the shell prompt back implying that the embed_example
>> application has exited. BUT it keeps running in the background
>> apparently. And I do get a qt window with a plot maybe a minute later.
>> Sometimes. Sometimes the background process just exits after a few
>> minutes without showing me a plot.
>
> I cannot explain any of that.  It works normally for me here.
> A qt window pops up immediately with four embedded gnuplot widgets
> and a text pane.  Output from gnuplot appears in the text pane.
> The demo replots to one of the widgets every second or so and
> continues to do so until I close the window or hit Ctrl-C in the
> controlling terminal.   No zombies either :-)

Must be nice :)

I just tried it again. Grabbed fresh sources from git. Rebuilt from
scratch. Same broken behavior consistently. Some things that could be a
problem that weren't:

- I have in my ~/.gnuplot: "set terminal x11 noenhanced". A
  gnuplot-based Qt widget shouldn't care. It's not clear if it does or
  doesn't, since taking that away doesn't fix it

- I'm using a tiling window manager. This constrains the window
  geometry. So fresh windows are resized immediately after they come up.
  This tickles bugs in some applications (like the wxt terminal, by the
  way). It's not the problem here, though: turning off the tiling
  behavior doesn't fix it.

- The outboard driver could be using the system gnuplot_qt instead of
  the just-built one. Setting the GNUPLOT_DRIVER_DIR to point to the
  local copy doesn't fix it.

I can help debug, if you're interested in looking into it. I'm doing
other things at the moment, though, so not going to dig into this myself
for now.

Re: gplt_x11 ignores SIGINT and SIGTSTP. Why?

[Ethan A M. <me...@uw...>]

On Saturday, 3 September 2022 15:07:23 PDT Dima Kogan wrote:
> Ethan A Merritt <me...@uw...> writes:

> > In the file .../src/Makefile.am is a commented out section that builds
> > a simple Qt app with embedded gnuplot windows.  
> >
> > Edit that file to un-comment the section and re-run
> >     ./prepare; ./configure; make
> >     ./embed_example
> 
> Cool! If this works, should building this be enabled by default?
> 
> I just tried it, and it doesn't work right for me. The embed_example
> program builds. Running it pops up a window that disappears immediately.
> Then I get the shell prompt back implying that the embed_example
> application has exited. BUT it keeps running in the background
> apparently. And I do get a qt window with a plot maybe a minute later.
> Sometimes. Sometimes the background process just exits after a few
> minutes without showing me a plot.

???
I cannot explain any of that.  It works normally for me here.
A qt window pops up immediately with four embedded gnuplot widgets
and a text pane.  Output from gnuplot appears in the text pane.
The demo replots to one of the widgets every second or so and
continues to do so until I close the window or hit Ctrl-C in the
controlling terminal.   No zombies either :-)

	Ethan

Re: gplt_x11 ignores SIGINT and SIGTSTP. Why?

[Dima K. <gn...@di...>]

Ethan A Merritt <me...@uw...> writes:

> On Saturday, 3 September 2022 13:12:11 PDT Dima Kogan wrote:
>> >> Let's say the request was "I want a gnuplot-powered plotting widget in
>> >> my GTK application". What would you suggest in that case?
>> >
>> > Isn't that what wxt is? 
>> 
>> Is it? If I was building a GTK application (not wx; plain GTK), could I
>> use the gnuplot wxt terminal as a widget in that application? The docs
>> don't make that clear, and definitely don't tell you how to do that.
>
> You seem to be asking for a cross-platform UI with widgets based on gtk.
> What I meant was that wxWidgets claims to be exactly that, although it
> doesn't use (or at least doesn't default to using) gtk on all the 
> supported platforms.  So if you base your UI on wxWidgets, then gnuplot's
> wxt terminal is a natural fit.

I don't actually write GTK applications, so *I* don't want this. But
somebody could be writing a GTK application, and they could want a
plotting widget. As I understand it, this isn't something that gnuplot
can provide today, unless that person rewrites their application with
wxt.


>> Similarly, what if I was building a Qt application? "help qt" mentions a
>> "widget" option, which maybe provides this function, but that option
>> isn't documented, so I don't know what it does.
>
> In the file .../src/Makefile.am is a commented out section that builds
> a simple Qt app with embedded gnuplot windows.  
>
> Edit that file to un-comment the section and re-run
>     ./prepare; ./configure; make
>     ./embed_example

Cool! If this works, should building this be enabled by default?

I just tried it, and it doesn't work right for me. The embed_example
program builds. Running it pops up a window that disappears immediately.
Then I get the shell prompt back implying that the embed_example
application has exited. BUT it keeps running in the background
apparently. And I do get a qt window with a plot maybe a minute later.
Sometimes. Sometimes the background process just exits after a few
minutes without showing me a plot.