[Kst] [Bug 115970] Datamode doesn't work on images.

Ted Kisner tskisner.public at gmail.com
Wed Nov 9 02:27:34 CET 2005

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

------- Additional Comments From tskisner.public gmail com  2005-11-09 02:27 -------
It seems like we need to come up with a general solution for when there are 
multiple basecurves on the current plot.  For example, we could have a bunch 
of vcurves, one image displayed as a colormap, another image (with different 
matrix) displayed as contour map, etc.

Perhaps kstbasecurve should have generic member functions to return "nearest 
data point for a given coordinate pair".  Then each basecurve (vcurve, image, 
etc) can decide how it wants to do this.  The vcurves would return the 
nearest vector point and the image would return the nearest matrix element.

Then each 2DPlot will query *all* basecurves for the closest data point to a 
current location.  The closest datapoint among all basecurves "wins" and this 
is where we draw the marker.

Any thoughts?


On Tuesday 08 November 2005 17:12, Matthew D Truch wrote:
> For the case of: Data mode -> curves don't exist, I think it's important
> that instead of x,y,z of image under the cursor, it needs to be nearest
> x,y,z that is data in the underlying matrix, with the appropriate
> 'datamode marker' indicating where that is.
> But this conflicts with the behavior of: data mode -> curves exist ->
> over an image, as if the x,y of the nearby curve are shown, there's no
> reason that it would coorespond with an x,y of the image's data.  The
> point of datamode is that you can see actual values that coorespond to
> actual data, not an interpolation thereof.

More information about the Kst mailing list