PC Zello 1.17 Bug List
Doug Lee
Last Revised July 22, 2012

These are bugs I have found in PC Zello version 1.17 as of the above date.

Bug #1

Summary

Messages marked as unread retain this marking on Zello restart but cease being counted as such in the channel's message count.

Steps To Reproduce

• In a running PC Zello, make sure there is at least one channel containing unread messages, with a message count (below the channel name) that is greater than zero (i.e., a number appears). Remember the channel name.
• Exit Zello completely so that it shuts down and leaves the system tray.
• Restart Zello and sign in (automatic is ok).
• Examine the above-noted channel and its specific history list (RightArrow can be used to open the channel-specific history list).

Actual Results

The channel's displayed message count is gone, but messages still appear as unread in the channel's specific history list. (This triggers Bug #2; see below.)

Expected Results

The unread message count should precisely reflect the number of unread messages shown in the channel's specific history list.

Workaround

None known.

Bug #2

Summary

Desynch between played and marked-read messages is possible when the user clicks on a channel message count.

Steps To Reproduce

• Execute the Steps To Reproduce for Bug #1, which will cause at least one channel to contain unplayed messages that are not reflected in the channel's displayed message count.
• Wait for a few messages to arrive in the channel. Notice that the message count shown below the channel name begins counting from 1 even though unplayed messages already appear in the channel's specific history list.
• Left-click the message count to begin playing unplayed messages.

Actual Results

The message that begins playing is the first message that arrived since the message count began incrementing from zero. In the case of a Zello restart (see Bug #1), the messages begin playing starting with the first unplayed message that arrived after the restart. However, the messages are automatically marked as read starting with the first actual unplayed message. This means that Zello begins to believe old messages that were never played were in fact played.

Expected Results

Messages should begin playing starting with the oldest unplayed message as shown in the channel's specific history list, and each time a message is automatically marked as read, it should be the message that has just played.

Workaround

Play unread messages from channel-specific history lists rather than by clicking message counts.

Bug #3

Summary

Playing messages by left-clicking a channel's message count can cause a condition where clicking history items plays the wrong message.

Steps To Reproduce

• Execute the Steps To Reproduce for Bug #2, which includes those for Bug #1 and which will result in messages playing but not starting from the first unplayed message.
• Open the channel's specific history list and click a message other than the one currently playing. Note which message actually plays. Then open the history for a different channel and try to play a message from it.

Actual Results

Trying to play a message in the already-playing channel will begin playing the next unplayed message after the one interrupted by the click, rather than playing the message actually clicked. If the clicked message is unread, however, it will still automatically be marked as read (see Bug #2). Trying to play a message from a different channel will still play the next unread message after the one currently playing - not even a message from the correct channel.

Workaround

• Switch Zello to status Busy.
• Transmit a short message to the Echo user and wait for its message count to show as "1."
• Click the "1" to stop the stream of playing messages in the original channel.

After this, clicking messages in channel-specific history lists will again work as intended.

Workaround

Play unread messages from channel-specific history lists rather than by clicking message counts.

Bug #4

Summary>

Clearing history does not clear message counts and still allows playing of old messages by clicking message counts.

Steps To Reproduce

• Make sure Zello contains a message history and that at least one channel shows a numeric count of unplayed messages below its name in Contacts.
• Clear all of Zello's message history by choosing View (from the menu bar), then History, then "Delete all" from the right-click menu of any history item.
• Close the history list and return to Contacts.

Actual Results

Message counts below channel names remain, and clicking them begins playing messages that are no longer shown in general or channel-specific history lists.

Expected Results

When any message is cleared from history, it should not be represented in message counts or remain playable by any means.

Workaround

Shut down and restart Zello once after clearing history. (If only part of history is being cleared though, this action can trigger bugs #1, #2, and/or #3 at some later point.)

Bug #5

Summary

Solo mode still allows out-of-channel messages to be played at the end of any local transmission.

Steps To Reproduce

Note: This bug is new in 1.17 and was not present in 1.16.

• Make sure there are multiple channels in Contacts that are active - i.e., people are frequently transmitting to them.
• Select a channel (or user) and enable Solo mode.
• Transmit to that channel or user and unkey when someone is activvely transmitting to a different channel.

Actual Results

When the local transmission ends, the out-of-channel transmission currenntly in progress will begin playing even though Solo mode remains active.

Expected Results

Solo mode should always prevent any out-of-channel transmissions from being heard.

Workaround

• Use Busy status instead of Solo mode.
• Watch the space below your chosen channel or user's name, where the message count appears when unplayed messages exist.
• Each time the message count below your chosen channel or user shows up (as "1"), click this number to begin playing the stream in real time (or very near real time).