Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#45 Showing next descriptor string also

open
nobody
5
2012-10-30
2012-10-30
Wim van Halen
No

In case of applying a 'user block' and attaching a string descriptor to a user block start event, the string attached to the next block is also shown in the TimeDoctor viewer (using version 1.4.3). So in case of the example below, when putting the mouse pointer in the first user block area, the pop-up shows 'state = initializing' and 'state = on'.

It appears that this only happens when the stop time stamp equals the start time for the next block.

So this problem typically occurs when you use a time ticker with a relatively low frequency (2000Hz in my case).

Following TDI shows the problem:
SPEED 24000000
TIME 2000
NAM 8 1 system-state
DNM 0 1 state
STA 8 1 15
DSC 3 1 2
DSC 0 1 initializing
STO 8 1 20
STA 8 1 20
DSC 3 1 3
DSC 0 1 on
STO 8 1 30

In case STA is a bit later than STO, problem is not there:

SPEED 24000000
TIME 2000
NAM 8 1 system-state
DNM 0 1 state
STA 8 1 15
DSC 3 1 2
DSC 0 1 initializing
STO 8 1 20
STA 8 1 21
DSC 3 1 3
DSC 0 1 on
STO 8 1 30

Discussion