DSD+ 1.074 Bug

Status
Not open for further replies.

SCPD

QRT
Joined
Feb 24, 2001
Messages
0
Location
Virginia
Bug: DSD+ doesn't remove the network name on subsequent frequency changes

Example: 119-10 DCC: 7 is displayed in the Event Log window but when changing frequencies the "119-10" name is still present despite the frequency change.

Workaround: If I close out DSD+ then the network name is reset.
 

DSDPlus

Member
Joined
Jul 24, 2014
Messages
377
Bug: DSD+ doesn't remove the network name on subsequent frequency changes

Example: 119-10 DCC: 7 is displayed in the Event Log window but when changing frequencies the "119-10" name is still present despite the frequency change.
What frequency / signal are you changing to?
 

racingfan360

Member
Joined
Dec 19, 2005
Messages
1,190
I occasionally see this bug when scanning between Conventional and Cap+ channels. The previous channel settings are held, and can give a false impression of what type of system/DCC/RAS in use until sufficient data is received on the next channel to reset the displayed information to the correct settings.

It's a similar pattern on NXDN too, when a false impression of RAN can be seen at times, when scanning across multiple NXDN freqs.

Maybe one solution would be to add the System/DCC/RAN decoded data into the main body of the Event Log window (which would have other additional benefits) and clear down the display at the bottom of the Event Log window when no data is being decode???

Jim
 

slicerwizard

Member
Joined
Sep 19, 2002
Messages
7,774
Location
Toronto, Ontario
Maybe one solution would be to add the System/DCC/RAN decoded data into the main body of the Event Log window (which would have other additional benefits) and clear down the display at the bottom of the Event Log window when no data is being decode???
With some of the trunking systems I monitor, that information would scroll off the screen in less than ten seconds, maybe closer to five. Personally, do not want!

Maybe a better solution would be to show that the information on the bottom line is "stale", but possibly still valid, if a NID or whatever hasn't been seen for 5-10 seconds. Maybe use a different text color?
 

racingfan360

Member
Joined
Dec 19, 2005
Messages
1,190
> that information would scroll off the screen
Sure....i think that was my point re writing the information into the Event Log window and not just displaying it at the bottom. In fact having it written there would mean you could more easily see what was going on irrespective of the time window.

Using different colors to distinguish active from stale decode info is a good idea.
 

SCPD

QRT
Joined
Feb 24, 2001
Messages
0
Location
Virginia
Maybe a better solution would be to show that the information on the bottom line is "stale", but possibly still valid, if a NID or whatever hasn't been seen for 5-10 seconds. Maybe use a different text color?

That would work...

Another suggestion would be to move that information to the channel window... and have it show the "last updated" time...

Basically, the problem is the stale info. I've now grown accustomed to just closing/re-opening DSD+ to make sure I have the most accurate information...

I suppose a manual reset key would also work. User switches frequencies and then presses "F" key to reset the stats?
 

DSDPlus

Member
Joined
Jul 24, 2014
Messages
377
We will add this to the 'N'eighbor list reset function. It will reset current NID and site number as well.
 
Status
Not open for further replies.
Top