Bug 745 - Timing decoder display is greyed out even if there is enough space to display it
Summary: Timing decoder display is greyed out even if there is enough space to display it
Status: RESOLVED FIXED
Alias: None
Product: PulseView
Classification: Unclassified
Component: Data display (show other bugs)
Version: 0.3.0
Hardware: x86 Linux
: Normal normal
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
: 735 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-02-01 22:53 CET by Christian Thäter
Modified: 2016-02-05 20:28 CET (History)
3 users (show)


Attachments
sample (same as in bug #744) (1.61 KB, application/octet-stream)
2016-02-03 03:32 CET, Christian Thäter 		Details
View All 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 Christian Thäter 2016-02-01 22:53:54 CET 
Attaching a 'timing' decoder on a signal yields following view:

  http://public.pipapo.org/pulseview3.png

There is enough space on the long gap in the signal to display the timing, but
it is greyed out.

Surprisingly when scrolling to the right, so that the end of that gap is not visible, the timing is rendered correctly:

  http://public.pipapo.org/pulseview4.png

Scrolling to the left and changing zoom level still keeps it greyed out.
Comment 1 Soeren Apel 2016-02-02 07:14:58 CET 
Hi, please attach a measurement that this happens with.
Comment 2 Christian Thäter 2016-02-03 03:32:07 CET 
Created attachment 221 [details]
sample (same as in bug #744)

The problem shows up when you attach the 'timing' decoder to channel 2 or 3 (short spikes), but not on channel 5 (more evenly distributed signal)
Comment 3 Soeren Apel 2016-02-04 07:54:54 CET 
Fix is here: https://github.com/abraxa/pulseview/commit/920eb49e49115b2d9bd85b8f9ec1a82f5c6e7671

Please report any further issues you encounter, thanks
Comment 4 Uwe Hermann 2016-02-05 02:58:41 CET 
Fixed in bdc2a99bcaa5aba7c6de2543bab6534299b8a5ee, thanks!
Comment 5 Soeren Apel 2016-02-05 20:28:41 CET 
*** Bug 735 has been marked as a duplicate of this bug. ***