On 04/25/12 19:37, Ethan A Merritt wrote:
> On Wednesday, April 25, 2012 02:09:19 am plotter@... wrote:
>> I have not tested this problem on canvas but I'm guessing it would be
>> the same as seen in svg.
>> Part of the value of scalable formats is the lack of granularity and the
>> ability to zoom to the desired resolution.
>> In testing mouse coords on svg I find there is granularity at the scale
>> of the decimal point character. (or one dot of the colon).
> The precision of the coordinates is indeed one decimal place.
> Not sure what you mean by "one dot of the colon".
>> I have configured Firefox to allow very high zoom levels , this is
>> excellent for looking at my data plots and allows seeing this problem
> I cannot speak to exactly what happens when you zoom in Firefox.
> Ideally it would employ the precision of the coordinates in the file,
> meaning that it would still be accurate to one display pixel when the zoom
> factor is 10X.
>> The mouse cursor moves smoothly as expected but the coord readout only
>> moves in jumps that are the size of the dot.
>> Each jump moves the cursor text by a similar amount and updates to coords.
> Quantization of mouse movement is a whole separate issue.
> If there is a limitation there, it's at the level of the X input layer
> or whatever serves that purpose on your platform. I am told that some newer
> platforms treat mouse position as a continuous variable, but to the best of
> my knowledge X only provides an integer pixel coordinate, and the minimum
> "delta" of mouse motion may be larger than one pixel.
>> Is this due to the svg_scale bug I caught last week?
> The internal precision of the plot is set by SVG_SCALE, yes.
> You could set it to 100. rather than 10. to get higher precision.
> The tradeoff is that printing an additional decimal place in every
> coordinate of every command in the output file will make the file
> significantly larger for a typical gnuplot graph.
> It is also possible that changing the precision would uncover additional
> bugs, but we could consider that a good thing rather than a bad thing :-)
I just tried a build with CANVAS_OVERSAMPLE aka SVG_SCALE=100
Good news is nothing too bad happens but I'm not sure what I get for my
<path d='M489.2,197.0 L484.7,197.0 M489.2,193.3 L484.7,193.3
M489.2,189.6 L484.7,189.6 M489.2,186.0 L484.7,186.0
M489.2,182.3 L484.7,182.3 M489.2,178.6 L484.7,178.6 M489.2,175.0
L484.7,175.0 M489.2,171.3 L484.7,171.3
M489.2,167.7 L484.7,167.7 M489.2,164.0 L480.2,164.0 h0.01'/>
What difference should I see ? I thought this was supposed to add and
extra d.p. to the x,y coords.
From the source, it just looks like it changes the preset variables it
prints for the js mouse code.
// plot boundaries and axis scaling information for mousing
gnuplot_svg.plot_term_xmax = 60;
gnuplot_svg.plot_term_ymax = 48;
gnuplot_svg.plot_xmin = 6.4;
gnuplot_svg.plot_xmax = 48.9;
gnuplot_svg.plot_ybot = 40.2;
gnuplot_svg.plot_ytop = 5.4;
gnuplot_svg.plot_width = 42.6;
gnuplot_svg.plot_height = 34.8;
gnuplot_svg.plot_axis_xmin = 0;
gnuplot_svg.plot_axis_xmax = 1980;
gnuplot_svg.plot_axis_ymin = -5;
gnuplot_svg.plot_axis_ymax = 90;
gnuplot_svg.polar_mode = false;
gnuplot_svg.plot_axis_x2min = "none"
gnuplot_svg.plot_axis_y2min = -50;
gnuplot_svg.plot_axis_y2max = 900;
gnuplot_svg.plot_logaxis_x = 0;
gnuplot_svg.plot_logaxis_y = 0;
gnuplot_svg.plot_timeaxis_x = "Time";
also mouse coords gets a bit confused though I don't understand how.
y mouse coord is upside down , x TIME coord gets 24h in several times
across the plot that is just a daily plot.
x=00:30 reads 05:53 ; y1=30 reads -640 !?
Needs a fix.