Some wishes for additions for measuring

[Bluescreen2001]

Hi

I just used this logic analyzer for the first real analysis. I want to analyze my HUB75 LED matrix.
First I must say, I like your software very much. It's much more responsive and modern than e.g. sigrok.
Using sigrok's protocol analyzers is a nice twist. Hope nobody is upset by that.

But I immediately missing some things, most I think are very easy to implement.

1. Why that restriction of 10.000 samples per screen. We can sample about 65.000 samples. I would really like to see the whole capture.
2. If 1 cannot be solved, there has to be a possibility to extend the marked measurement area beyond screen limits

And here we come to the next slightly bigger whish: marking an area for measurement:

3. Use Cursors for marking, you can keep the dragging thing in the sample marker area, but draw two dotted lines (cursors) across the data area. These cursors should the be draggable to position them exactly over a specific edge. Maybe even snap it to an edge.
   I would like the following workflow. Mark an area roughly by dragging in the sample marker area. Then selecting one cursor to drag it left and right to position it exactly. If there is an edge near the mouse snap to it. As an alternative to dragging in the marker area rightclick somewhere in the data area brings up a context menu with set cursor 1 or 2.

4. With the above exact positioning of the measurement area, you can add some info to the rightclick context menu for the marked area like duration, number of pulses, etc. Same as in the measurement popup on the marker area.

5. For navigation, in the above mentioned context menu for a data line, I would like two entries ore buttons to jump to the next/previous edge on the selected channel

That's it, I think. I have some more ideas, but these are mostly cosmetic and not so relevant.

But one big wish is there, but I think that is impossible due to hardware restrictions:

6. It woul be really cool if you can use one channel as sample clock. Lets look at my LED panel example: It has a pixelclock which all signals respond to. If we can use that as sample clock, it would save at least 3 times samples, because there is no use in a higer sample rate that signal rate then.

And add a nice flashing sign when device is currently sampling and read the sample memory when cancelling.

So, enough for now. I hope I don't bother you with my suggestions.

Greetings
Thorsten