When using fg.show() a nice gnuplot window pops up and everything is good until I try to zoom or move around or in any way interact with the window. As far as I understand this is normal behavior when using the -p gnuplot parameter.

I think it would be better to use pause mouse close as the last command instead of -p. This command keeps the gnuplot process running until the window is closed and is probably better than -p since the window becomes interactive.

Currently I am using this workaround, but if you agree I think this would be a nice addition to the library.

let p = Command::new("gnuplot")
    .arg("/dev/stdin")
    .stdin(Stdio::piped())
    .spawn().unwrap();

let mut stdin = p.stdin.unwrap();
fig.echo(&mut stdin);
stdin.write_all(b"pause mouse close\n").unwrap();

I have the following code:

// myexample.rs
let mut fg = Figure::new();
    
fg.set_terminal("qt", "");

fg.axes2d()
        .lines(&times, &lambda_values,
            &[
                Caption("λ(t)"),
                Color("#1E90FF"),
            ])
        .points(&event_times, &event_intens, 
            &[
                Caption("Events"),
                Color("black"),
                PointSymbol('O'),
                PointSize(0.8)])
        .set_x_label("Temps t", &[])
        .set_y_label("Intensité", &[]);
    
fg.show();

But when I run cargo run --example myexample, the gnuplot window doesn't show up (not even for a split second). When I choose a different backend such as pngcairo and an output file, it won't create the file either. I have to echo to a .gnuplot file and run gnuplot manually.

I'm running Windows 10 64-bit, with Rust 1.26.2 and gnuplot 5.3.

In axes_common.rs:

• in struct AxisData, add field reverse: bool.
• in AxisData::new(), initialize struct with reverse: false.
• in AxisData::write_out_commands(), write reverse.
• add AxisData::set_reverse() method.
• in trait AxesCommon : AxesCommonPrivate add set_x_reverse() and set_y_reverse() methods.

In axes3d.rs:

• add method set_z_reverse to Axes3D.

I want my rust code to loop {} until the plot window is closed. How do I do this?

This is needed, as most gnuplot terminals loose control facilities if the their gnuplot process dies, which always happens if the rust program which spawned gnuplot dies. So in order to have that rust program wait for the gnuplot terminal to terminate, one needs to know whether gnuplot is still running.

I re-implemented the multiplot options from pull request #47 using @SiegeLord's feedback on the API and where to generate the gnuplot commands. I also added an example showing how to use the new options.

Hi,

This patch relaxes the input type of all methods from Iterator<_> to IntoIterator<_>. Since every Iterator implements IntoIterator, this does not break any old code. On the other hand, it allows for a more ergonomic code:

let x = [0i32, 1, 2];
fg.axes2d().lines(&x, ...);

and such.

I had to update the examples since they do not build on nightly anymore. I have removed all unstable features so the examples now build on the stable branch.

not doing a close() on a figure leaves an unterminated zombie process in the operating system.

It makes sense to suggest best practices regarding resource management right in the main docs.

Not sure if I'm doing anything wrong but with this example both lines are drawn using the same color, making impossible to distinguish them. Using points() instead of lines() does alternate the color and pattern. Shouldn't lines() do it as well?

use gnuplot::*;

fn main() {
    let mut fg = Figure::new();

    fg.axes2d()
        .lines(&[1, 2, 3], &[1, 2, 3], &[Caption("fst")])
        .lines(&[1, 2, 3], &[4, 5, 6], &[Caption("snd")]);

    fg.show();
}

I was creating a bar chart using this library but found that it would not allow for strings to be attached to xtics. If this could be added it would be immensely useful for creating bar charts.

Thanks for this nice library! I discovered that RustGnuplot uses gnuplot's errorlines in order to plot points with error bars. Is there a way to use errorbar instead? If i understand the documentation correctly, one could achieve the former by using errorbar + plot. On the other hand it seems like one cannot turn off the lines once they are plotted with errorlines. I also tried setting the linewidth to 0 to no avail. Am I missing something?

This fixes issue #6, I'm not entirely sure this is the best way to fix it but as far as I can tell it works. I fixed it by passing borrowed references to the member, instead of moving out of it.