Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggenstion: Segments will subdivide cursor region instead of expanding it #118

Open
fsch2 opened this issue Jan 6, 2017 · 1 comment
Open

Comments

@fsch2
Copy link
Contributor

fsch2 commented Jan 6, 2017

The cursors offer the magnificent feature of adding segments that can be used to calculate the symbol rate of a given signal. However, increasing and reducing the number of segments works not so intuitively: the cursor region is expanded/reduced by a whole segment size each time. I would find it more intuitive if the segments would not change the cursor region but subdivide the region into segments of increasingly smaller size.

When calculating the symbol rate, I put the cursors on the beginning and the end of a sequence of symbols. Then, I add segments until they line up with the symbols. This is easier if the implementation is changed as outlined above.

Do I use the cursors in a way they were not intended to be used? Should this be a configuration option? Do you prefer the current implementation? What do you think?

@miek
Copy link
Owner

miek commented Jan 6, 2017

The intention with the current behaviour (or at least how I use it) is that you start with ~10 segments and line those up with the first 10 symbols (usually part of a preamble), then increase the number of segments/symbols until it hits the end of the packet.

Ultimately I think both behaviours should be supported.

I'm thinking a modifier key + dragging a cursor would add/remove segments up to the cursor. This means dragging out to the end of a packet is quick and easy. It also adds the option of moving the left cursor backwards to add segments before the current view.

Editing the number of symbols text box would probably revert to the behaviour you describe of not changing the cursor region.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants