Bug 1289 - UX problems when there are more channels than fit in the view
Summary: UX problems when there are more channels than fit in the view
Status: CONFIRMED
Alias: None
Product: PulseView
Classification: Unclassified
Component: UI (show other bugs)
Version: unreleased development snapshot
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-29 12:41 CEST by Soeren Apel
Modified: 2018-09-29 12:41 CEST (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Soeren Apel 2018-09-29 12:41:10 CEST 
As testjarfalla63@gmail.com wrote on the ML in July 2018:

"when rescaling, the view is set on the top traces regardless of where I was looking earlier. I also notice that moving a trace is a little difficult when I go beyond the farthest down one, seen from the top. If I grab a trace far down, the window is immediately moved to showing the top traces and I can only drop the trace there - I can't move it further down. In the analyser I have 32 channels, but only the top 15 (approx) are simple to view. The other ones can of course be viewed, but I need to rescale and then move the window down. I'm also careful not to grab these as they then drop at the top and I can't move them down."

So there appear to be at least two issues here:

1) scaling changes the view to show the top traces
2) moving a trace changes the view to show the top traces