|
From: Sylwester A. <sa...@ig...> - 2013-03-06 23:50:44
|
Hi, On 06/03/13 16:51, pl...@pi... wrote: > On 03/06/13 15:22, Mojca Miklavec wrote: >> On Wed, Mar 6, 2013 at 12:10 PM, Sylwester Arabas wrote: >>> >>> Then maybe issuing a warning before overwriting an existing png file >>> would be a solution? >> >> This would be problematic. Many people simply run the same plotting >> commands/scripts multiple times (either during development/improvement >> of graphs or to display measurement results for different data), >> *expecting* the files to be overwritten. I'm not using SVG, but for >> any format that I'm using, I would be annoyed if I would have to >> confirm overwriting files. Wouldn't you be annoyed if you "simply run the same plotting commands/scripts multiple times" with different data and different output file specified, but get the data from just the last plot in all of the output files? :) $ cat full.gpi set term svg set palette negative set view map set output "full.svg" splot '-' matrix with image notitle 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 e $ cat half.gpi set term svg set palette negative set view map set output "half.svg" splot '-' matrix with image notitle 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 e $ gnuplot full.gpi $ gnuplot half.gpi Now both full.svg and half.svg contain the same image (half) even though the input data was different, and the output file was different! Basically, anything you plot with "splot with image" on an svg terminal silently damages all svg files in the current directory previously plotted "with image". Unfair. HTH, Sylwester P.S. Is there any way to force gnuplot not to use external png files but instead draw the images pixel-by-pixel with svg rectangles as it was done in older versions of gnuplot? -- http://www.igf.fuw.edu.pl/~slayoo/ |