Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Ethan A Merritt Newsgroups: comp.graphics.apps.gnuplot Subject: Re: set link via in version 5.0 vs 5.2 Date: Thu, 05 Oct 2017 09:30:55 -0700 Organization: A noiseless patient Spider Lines: 43 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit Injection-Date: Thu, 5 Oct 2017 16:30:59 -0000 (UTC) Injection-Info: reader02.eternal-september.org; posting-host="2b33c8b09e2947ae18fc0b57c3929278"; logging-data="13672"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+YRjBxloO1xjW92SNjbpo4" User-Agent: KNode/4.14.10 Cancel-Lock: sha1:pL/mFTrFtDa1FOXbDwkrU9GW5jE= Xref: csiph.com comp.graphics.apps.gnuplot:3765 Klaus Dahlke wrote: > I use gnuplot mainly by calling it from a ruby on rails application, > but the following behaviour difference is also observable just by > using gnuplot from the command line: > > I like to plot two datasets, one for axes x1 and y1 and the second one > for x2 and y2. In Gnuplot 5.0 the following set of commends works > fine: > > set autoscale xfixmax > set link x2 via x*0.319 inverse x/0.319 > > and plot has the expected outcome. The plot is then an rectangular > where the x1 axes and x2 axes ends just at/on the y2 axis. It is hard to say what the problem might be because you have not shown the plot command itself. What are you plotting? > After upgrade to version 5.2 plotting is aborted with 'x range is > invalid'. When replacing 'set autoscale xfixmax' with e.g 'set xrange > [0:7349]' the plot is produced fine, 'set xrange [0:*]' doesn't work. It works fine here, but I am probably testing a different plot command. Please show the entire series of commands that result in an error message. > In ruby it is easy to determine the maximum of the x-axes and then > construct the respective command to be parsed to gnuplot. > > Nevertheless, would be happyif the behaviour could be reverted back to > use 'set autoscale xfixmax'. There was no intentional change in the effect of command "set autoscale xfixmax". If there is a bug that caused an unintentional change we can try to fix it, but you will have to show an example of the bug so that it can be reproduced. Ethan > Thankd and best regards, > Klaus