WIN500 (VO1.84) - Confusing Warning Pop-up

[qlajlu]

I decided to take the new version (1.84) of WIN500 for a test drive today and found two things.

First was it is very sluggish loading the data to the software after selecting the Country, State, etc. compared to the previous version. This may be the result of the changes RR made to the Database rather than the software itself, but it is quite noticeable.

Second was a pop-up (see below) that says, "The selected sites appears to be a mix of Default and Splinter 800 MHz frequencies and may not work in a single TSYS." This is NOT correct. UCAN (the system from which I was importing) is THE system for the entire state and the import I attempted was only one site (Site 003 - Salt Lake Simo). The entire state system under UCAN has been rebanded and is not a Splinter mix and no other systems are involved. The Custom Table that WIN500 created (I selected, "Yes" from the pop-up) was not close to the rebanded table now in use in our state. The correct rebanded table is a selection inside the WIN500 software under TSYS > Trunking Tables.

I would think that this warning pop-up should be removed or at least changed to warn that the system/site attempting to be imported has been rebanded and that after importing the data a custom trunking table must be selected from those offered by the software rather than offering to create the table itself.

This warning is very confusing and especially for "Newbies."

 

[DonS]

Yes, it's a lot slower to retrieve data with the new interface, primarily because there's a lot more data moving around.

I've added handling for the 'splinter' and 'rebanded' flags that now come from the RR DB. In Win500, I won't show the above warning message if either of those flags are set.

I'll be releasing new versions of all 3 apps later on today.

 

[qlajlu]

Still Have a Hiccup

Yes, it's a lot slower to retrieve data with the new interface, primarily because there's a lot more data moving around.

I've added handling for the 'splinter' and 'rebanded' flags that now come from the RR DB. In Win500, I won't show the above warning message if either of those flags are set.

I'll be releasing new versions of all 3 apps later on today.

Okay, I did another "test drive" of the software today with the newest version (V 1.85). As stated before, it is still really sluggish gathering the data, but that is the way the new interface works. No pop-up this time.

However, there were a couple of "hiccups" encountered:

1. I selected only one Site (UCAN Site 003 - Salt Lake County) and specified only three TGs to be imported. What I got was the Site's CCs and 379 TGs (all belonging to the UCAN system), a good share of which do not use nor could be used by this one Site. With that occurring, it will require going through the TGs, one-by-one, and edit them (delete) before uploading to the scanner. It should only import the objects selected, right?
2. Even though Scan List 1 was showing under the General Settings tab as the Default Scan List at the time of importing, no TG ended up being defaulted to any scan list. Shouldn't they be put into Scan List 1 when no Scan List selection is made?

Don, can these be fixed?

The program DID select the proper trunking table for the Site imported without having to make the selection manually.

 

[DonS]

I selected only one Site (UCAN Site 003 - Salt Lake County) and specified only three TGs to be imported. What I got was the Site's CCs and 379 TGs (all belonging to the UCAN system), a good share of which do not use nor could be used by this one Site. With that occurring, it will require going through the TGs, one-by-one, and edit them (delete) before uploading to the scanner. It should only import the objects selected, right?

Fixed in version 1.86.

Even though Scan List 1 was showing under the General Settings tab as the Default Scan List at the time of importing, no TG ended up being defaulted to any scan list. Shouldn't they be put into Scan List 1 when no Scan List selection is made?

If you leave the "Target Scan List" in the "Web Import Settings" dialog set to its default of "00 - <unassigned>", that's exactly what you'll get - talkgroups that are not assigned to any scan list. It's not that "no Scan List selection is made"; instead, you're leaving an explicit setting unchanged.

 

[qlajlu]

If you leave the "Target Scan List" in the "Web Import Settings" dialog set to its default of "00 - <unassigned>", that's exactly what you'll get - talkgroups that are not assigned to any scan list. It's not that "no Scan List selection is made"; instead, you're leaving an explicit setting unchanged.

In earlier versions if no selection was made at the dialog for Target Scan List, the imported TGs would still default to Scan List 1. You're saying that this is no longer the case. Is that right?

EDIT TO ADD: What kind of warning will be displayed by the scanner if no TGs are assigned to a Scan List on a pristine import and the user attempts to do some scanning? Would it be "Nothing Enabled?"

 

[DonS]

In earlier versions if no selection was made at the dialog for Target Scan List, the imported TGs would still default to Scan List 1. You're saying that this is no longer the case. Is that right?

If it ever did that, it was a very long time ago.

Comparing the current source code to the version back in Sept 2008, the "Target Scan List" handling is identical - for at least the last 10 months, it hasn't looked at "Default Scan List" when importing talkgroups.

EDIT TO ADD: What kind of warning will be displayed by the scanner if no TGs are assigned to a Scan List on a pristine import and the user attempts to do some scanning? Would it be "Nothing Enabled?"[/QUOTE]

Yes - "Nothing Enabled".

 

[qlajlu]

Downloaded V 1.86 and imported the same objects I used yesterday and encountered no problems or unusual hiccups that would throw a tizzy into a newbie.

Thanks, Don.