<d1b2>
<azonenberg> So i have y axis cursors about 90% done
<d1b2>
<azonenberg> the main thing remaining is to display position indicators on the line
<d1b2>
<azonenberg> The question is where? my natural inclination would be at the far right, but then it'll step on the grid markings
<d1b2>
<azonenberg> the two obvious options are a) somewhere else (left? center?) or b) on the right but with like a black background or something to make it easier to read, at the cost of covering up the y axis markings for the grid
<dingwat>
azonenberg: I think that looks good, pretty similar to how some other software does it. Definitely don't want to cover up the y-axis
<azonenberg>
dingwat: one open question is if we want to add any kind of data readout and if so, how
<azonenberg>
for x axis it's easy as a waveform can have only one value at a given x coordinate
<azonenberg>
but it will likely cross a given y axis value many times
<dingwat>
hmm. closest y-crossing to cursor? that might get kinda distracting as it bounces around though
<dingwat>
azonenberg: honestly it would be kinda cool if you could over your mouse near cursor-trace intersections and it would pop up the point.
<dingwat>
s/over/hover/
<azonenberg>
So that's the sort of thing i have in mind looking forward
<azonenberg>
making it fast would be nontrivial
<azonenberg>
but thats something i want to explore
<azonenberg>
as you start getting e.g. multiple waveforms in one plot it would be even more fun
<dingwat>
azonenberg: yeah, I imagine it's non-trivial to implement, but it seems like the most useful behaviour. Maybe you can compute all the intersections as the cursor(s) are adjusted, so then it's a matter of figuring out when the mouse is close to a given point? That could get really painful for a big waveform though
<azonenberg>
yeah exactly the challenge is doing it at >60 FPS on potentially a >100M point waveform
<azonenberg>
lots of things are easy to do by brute force on small waveforms
<azonenberg>
but on big ones, much less so
<azonenberg>
anyway food for thought
<azonenberg>
Near term my priority is banging out the remaining... 17? issues blocking the v0.1 release
<dingwat>
maybe it could be something that only shows up when the acquisition is stopped? So it's not something that has to happen every frame, and it could be an async task to find all the intersections
<azonenberg>
it's more a quesiton of how to make the UX work
<azonenberg>
this will tie into other things like having markers and cursors snap to data points on digital waveforms when you're dragging them
<dingwat>
ah yeah, good point
<dingwat>
saleae does a really good job on that IMO
<azonenberg>
yeah
<azonenberg>
right now my focus is on knocking out issues blocking the release and not merging any other PRs or doing any new feature dev