Voters 24
-
-
F
-
K
-
R
-
M
-
-
T
- + 17 voters
-
A
-
R
-
R
-
P
-
P
-
S
-
J
-
P
-
O
-
H
-
V
-
T
-
A
-
-
B
-
D
-
A
- + 1 anonymous
24
Minimap of trace
- Open
- Subscribe
|
V |
vaj rasana |
In modern Editors like sublime, vscode, intellij, there is a mini-map of the whole file, allowing a quick visual search.
- something like a small bar on the lower section of the screen or a small screen in the lower right corner.
Activity Newest / Oldest
Tim
(#77530)
"Suggestion: A magnifying glass feature. Sometimes, I have a long trace, and I want to see both small details and large details simultaneously for the same channel.
For instance, I have a slow packet that is being sent multiple times. It would be great to know where the packet begins and ends. However, the header and footer for that packet are tiny in time compared to the packet as a whole, so constantly zooming in and out with the current set up is very disorienting.
The magnifying glass doesn't need to be a pop-up. It can be a second view of the the channel (i.e. just listed as a special channel waveform like analog vs. digital) linked to a selected and draggable measurement period window (a setting could be to set the size of the magnification area in time)."
Tim
"Actually, the idea is a little different than the minimap. In a minimap, you can't actually really read the text. In my suggestion, I still want to maintain the original view of the channel so whatever zoom level I have is still maintained there.
View adjustment is in reverse of a typical minimap. In the typical minimap, clicking on the minimap will change the "original" zoomed in view to match the minimap. What I'm suggesting is the opposite: clicking a movable "window" in the original to alter what is displayed in the "further zoomed in view" (second "magnified" view of the original channel).
A half solution might be to just allow for us to have multiple views of the same channel (i.e. just like you have both a digital and analog view of the same channel). It still won't be as easy to track, but it might be a little better, since we can try to look at the timing bar at the top of each view."
Peter Jaquiery
Making any channel clicked in high priority for display, perhaps displacing a previous channel in the minimap, would help with context for next/prev edge skips.
A solid rectangle isn't a deal breaker if the current view region within the minimap is clear. The context within the capture is still clear, even if there isn't much "structure" in the map display.
Neel
Status changed to: Open
Peter Jaquiery
A minimap would resolve a major problem I have: zooming in enough to read bubble text means that I lose big picture context, especially when I use the "skip to edge" feature.
Almost always I'm dealing with bursty I2C or Async serial activity in the context of slow moving other activity (CC lines and VBus state changes in my current use case). Seeing the slow changes in some channels and blocks of activity in others would provide great context. Zooming the minimap would probably help a lot too by giving a big picture view of local context rather than an overview of the entire recording.
Peter Jaquiery
Shading the main view area in the minimap helps a lot for providing context.
Peter Jaquiery
Being able to select the channels used in the minimap would make it much more useful. That probably resolves the "solid rectangle" issue - any signals that are solid can be removed (or for bonus points, don't appear by default).
Saleae
Status changed to: Under review
Saleae
If the data is dense, I think that the minimap will look like a solid rectangle. Would showing timing markers and ranges over the scrollbar section be helpful?