Activity for dima
-
dima posted a comment on ticket #2841
Oh. OK. I understand what it's doing now, but I guess it just feels like a very strange thing to be doing. The output window is xy. The autoscaler untimately decides on xrange and yrange. So the xy data is what it should be using to make that decision. It sounds like it makes sense to you, so then yeah, there's no bug. Thanks for explaining.
-
Hold on! I've been busy, and haven't had time to reply. I've read your comments multiple times, and I'm sure it makes sense to you, but it doesn't make sense to me. First, the regression. I check out the "5.4" git tag, and I see the old behavior. The breaking commit is linked above. I cannot say if it does the right thing. Next, the intent was not to limit the input (as rrange would do) but to limit the output (as yrange should do). The autoscaling logic, as I always understood it, should select...
-
Hello. This plot is autoscaled on the x (where the data appears in a very small range), but the yrange is locked to [-5:5]. The data outside this yrange shouldn't affect this, and it didn't previously. I just did a bisection. 5.4 worked properly, 5.5 does not. The specific commit that broke it is: https://github.com/gnuplot/gnuplot/commit/6d3c518a5bdd0da34d7e7ba40e88d7e7576c41b2
-
Incorrect autoscale regression in polar plots
-
Hi. I don't think this is the case. I have this script: set yrange [10:0] set y2range [0:10] set link y2 via y inverse y set y2tics plot x If I remove one of "set yrange/y2range" commands, then the remaining one IS respected, despite the "set link" coming after. I.e. the "set link" doesn't override the existing setting. If I leave both "set yrange/y2range" in there, it's impossible to respect them both, and the "set y2range" is ignored.
-
Thanks for patching this. Can we release a 6.0.3 that includes this patch in the near future? The new Debian release will be cut in the next few months, and I would really like to not have this bug in that release. Thanks.
-
Hi. I just did a bisection, and the breaking commit is this: https://sourceforge.net/p/gnuplot/gnuplot-main/ci/d26fbee37127ed910a03e3c181bc4362b443c9ba/ It looks like you probably already know this, since you made an update "3 minutes ago". Thanks for working on this.
-
Regression in 6.0.2: "splot with points palette" produces incorrect colors
-
If "set link" is given, gnuplot should warn or barf if impossible constraints are given
-
gnuplot 6.0.2 has new, overly-assertive warning
-
Thanks for the note! I just didn't know about it. One tweak I had to make: "refresh" instead of "replot" to handle volatile data. Leaving it as "replot" makes gnuplot quit immediately. With "refresh" it's perfect. Thanks!
-
Hi. Can I get a comment about this one? It's VERY useful for some of my use cases, and it would be nice to get it merged
-
New interactive command: 'M' to toggle "set view map"
-
Hi. Thanks for the response. Once I figured out what the issue was, I found the FreeImage_ConvertTo24Bits() function to do what I wanted. A load-time flag would be useful to make the life of the user easier by handling this common use case instead of asking the user to do it. This would be similar to the JPEG_GREYSCALE flag. The user CAN make that conversion themselves if they want to, but the flag makes it nicer. Something like FIF_EXPAND_PALETTE or something. A very related issue is how to make...
-
Hi. I figured out the problem. This image uses a palette, so it really is 8 bits per pixel. So this isn't a bug, but I have a feature request: FreeImage_Load() should be able to take a flag to automatically convert all palettized images to 24bpp. This is a special case, but an extremely common one. Thanks.
-
I'm attaching a demo program that demos the problem. It does this: $ gcc -o tstimage tstimage.c -lfreeimage && ./tstimage /tmp/tst.png width = 256 height = 256 pitch = 256 bpp = 8
-
PNGs from openstreetmap tiles always load as grayscale
-
Thanks for working on this. Also, I didn't know about "set view projection", so that will be helpful in the future also.
-
splot with 'set view 90,90' draws the xy plane in the wrong place
-
Inconsistent behavior: "pause mouse close" doesn't work with "x11" terminal, X-forwarding, feeding gnuplot via a pipe
-
QT terminal can leave zombie processes
-
I just ran a test, and it works now. Thanks!!
-
I accidentally pasted the wrong thing. Yes, 1973 is the other report I saw.
-
I should say that a similar issue was reported previously: https://sourceforge.net/p/gnuplot/bugs/2186/ The bug tracker says that this has been fixed, but I'm still seeing MY problem with latest gnuplot from git: commit 9cdef3d0362d2ea2e27248e4659fc083a86afa3e (HEAD -> master, github_gnuplot/master) Author: Ethan A Merritt merritt@u.washington.edu Date: Sat Jul 13 20:29:35 2019 -0700 truncate_to_one_utf8_char: This function was not acting as claimed. Now it is. Bugfix: previously could not set pointtype...
-
Autoranging doesn't work with linked axes
-
Hi. Thanks for the reply. You were correct: the inline nature of this data is what was tickling this bug. Two questions: Bug 1709 was very similar, but somebody (you?) ended up fixing it without requiring the workaround. Could a similar fix be applied here? I didn't know about the writeback functionality. This sounds like a good, general method that should be utilized more by default. How about this logic: when plotting: if( we have only inline data) { save writeback } when replotting: if( we have...
-
error in edge3d_intersect
-
I forgot to mention: this is from the bleeding edge gnuplot from the repo.
-
autoscale logic is different (and incomplete) on replot (same as bug 1709)
-
Oh yes. You're right. Would it be difficult to change the error message to make this obvious? I tested this again with an actual auction, and it works now. Thank you! Finally, what is your sense about how pervasive the issue was? Was it something specific to my account, or do you think this was broken for everybody? If it was broken for everyone, I'm going to try to get the Debian package updated asap, since the new Debian release is coming out soon. Thanks again.
-
Thanks a lot for the patches! Unfortunately the latest on CVS still doesn't solve the issue for me. Logs: http://pub.secretsauce.net/esniper.TitleNotFound.bug.2.tar.gz
-
Thank you for replying. Log is here: http://pub.secretsauce.net/esniper.TitleNotFound.bug.tar.gz This is from a fresh build from CVS as of today (2017-05-27), although I see the same issue when running from a Debian package.
-
Hi. I'm still seeing this issue in 2.33.0. Are you sure this was fixed?
-
Thanks for the note. I just investigated a bit, and I can observe this problem as...
-
Regression x11 terminal can no longer draw lines with splot
-
The patch
-
PATCH: normalized, non-cumulative histogram
-
plot has incorrect x extent when plotting dynamic data 'with boxes'; replot fixes it
-
replot has incorrect y extent when plotting dynamic data 'with boxes'
-
replot has inconsistent autoscaling with points, inline data, logscale
-
Hi. Thanks for checking. I just ran a few more experiments and have more information....
-
regression: splot with image now throws an error
-
autoscale logic is different (and incomplete) on replot
-
Hi Ethan. I agree that 3.25,5.5,7.75 isn't "nice", but it doesn't mean that the current...
-
Default logscale mtics are weird
-
plotting from an open file descriptor set to 'volatile' is seek() is not available
-
OK. That's a good workaround for this particular case. Are you suggesting this as...
-
Uneven default extents with image plots
-
Hi. I tested the patch, and it fixes both issues. Thank you very much for a lightning-fast...
-
Wrong point types with binary matrix plots and the default colorsequence
-
Attaching a tagged workspace to a frame makes things confused
-
Added default bindings to move workspaces between screens
-
Hmmm. I tried all 4 directions with both x11 and qt terminals and two different builds...
-
Hi Ethan. I'm happy to break up the patch, but I'd like to observe the issue you're...
-
Another line-clipping issue
-
OK. Those are fine points, and I need to think about how to resolve those. Do you...
-
Another line clipping regression
-
patches attached
-
X11 clipboard paste fixes
-
Regression: 'with steps' doesn't always render horizontal lines
-
This is a duplicate of 677. Sorry; sourceforge got confused.
-
I fixed this and related issues. Patch tracker: https://sourceforge.net/p/gnuplo...
-
Fixed many small mouse-triggered-zoom bugs
-
Fixed many small mouse-triggered-zoom bugs
-
Silly sourceforge only lets me attach one file. Here's the second patch.
-
fixed broken y2 rescaling in do_zoom_scroll_down()
-
Hi Ethan. I replied to this earlier, but sourceforge apparently doesn't believe in...
-
You're right about that detail. The benchmarks in question start a new cscope process...
-
I think it's real. Unless you pass -d, cscope updates the database on each query,...
-
I ran some cscope timing tests earlier, so I ran this patch through the evaluation...
-
Autoscale logic now has a margin
-
zoom_around_mouse() doesn't work with volatile 2d data plots
-
Zoom-around-mouse is imprecise
-
Flipped horizontal mouse-wheel scrolling direction
-
Docs: clarified "set object circle" behavior with a skewed aspect ratio
-
qt terminal can't zoom into large images
-
I sent this reply over email earlier, but I don't see it here. Sourceforge has odd...
-
Plots with the 'unknown' terminal now produce obvious output
-
Removed build system references to the 'cgi' terminal
1
