Project

General

Profile

Actions

Bug #1797

closed

Misleading Message "An ERROR has Occurred"

Added by John LaMartina over 9 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
08/01/2014
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Baofeng UV-5R series
Platform:
All
Debug Log:
I read the instructions above:

Description

To avoid New User Panic,

  • the message: "An ERROR has occurred" should be softened to "Warning: Please Take Note"

This message occurs when two radios of the same series (ie. UV5R) with different firmware are using the same CHIRP image.

Everything transfers fine with the exception of the Others Tab.

As always, Thank You for the excellent work.

John K3NXU
http://www.miklor.com


Files

Actions #1

Updated by Jim Unroe over 9 years ago

Attached is a screen capture of the "Error" message. It has caused to me go "now what's wrong" more than once until I realize I am experimenting with an image that was saved from a radio with a different firmware version than the one in my radio.

I agree that this "Error" message needs to be toned down to be more of an "informational" message than an error message. I believe it should look more like the "Experimental" prompt for which I have also attached a screen capture.

This affects all radio Models supported by the "uv5r.py" driver.

Actions #2

Updated by Bernhard Hailer almost 4 years ago

  • Status changed from New to Feedback
  • Target version set to chirp-legacy
  • Model affected changed from UV5R series to UV-5R series

Jim, has this been done by any chance?

Actions #3

Updated by Jim Unroe almost 4 years ago

Bernhard Hailer wrote:

Jim, has this been done by any chance?

Hi Bernhard,

No. I think this is something that would have to be change in the CHIRP UI. It is the only "ERROR" message that is available.

If the reads the rest of the message, it should be clear that the upload completed. So it isn't that big of a deal.

The originator contacted me an said he is OK with the ticket being closed.

Jim KC9HI

Actions #4

Updated by Bernhard Hailer almost 4 years ago

Well, it's a valid concern, so let's keep this one open until someone can have a look. Thanks for your feedback, Jim.

Actions #5

Updated by John LaMartina almost 4 years ago

Jim / Bernhard
This request that I made 6 years ago can officially be closed as is.
No need to alter this message.

Thanks as always.
Stay Safe and Healthy.

John K3NXU

Actions #6

Updated by John LaMartina almost 4 years ago

John LaMartina wrote:

Jim / Bernhard
This request that I made 6 years ago can officially be closed as is.
No need to alter this message.

Thanks as always.
Stay Safe and Healthy.

John K3NXU

Changing this message now will cause confusion.
Please withdraw this issue request.
Thanks

Actions #7

Updated by Bernhard Hailer almost 4 years ago

  • Status changed from Feedback to Closed
  • Model affected changed from UV-5R series to Baofeng UV-5R series

Hello John, OK done. Thanks for your feedback!

Actions

Also available in: Atom PDF