Project

General

Profile

Actions

Bug #3715

open

chirp-daily-20160531-win32: img marked dirty is not changed

Added by Rich Messeder almost 8 years ago. Updated over 7 years ago.

Status:
Feedback
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
06/06/2016
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
(All models)
Platform:
Windows
Debug Log:
I read the instructions above:

Description

I opened an img file. Click on Browser tab. Click on Settings tab. File marked as dirty.

Actions #1

Updated by Jim Unroe almost 8 years ago

  • Status changed from New to Feedback

?. What radio is the image from? How about attaching that "dirty" image to this issue.

Your aren't clicking on the .img file in the Windows file explorer are you? If you did, the .img extension is likely associated with some other application, not CHIRP. You have to open a CHIRP Radio Images (.img) file by launching CHIRP and performing a File -> Open.

Jim KC9HI

Actions #2

Updated by Rich Messeder almost 8 years ago

BaoFeng UV-5RTP.
I apologize for using what may be a slang term for a file that is changed. To me, a file is dirty if the copy in memory is different from what was loaded. For some apps, this may also mean that the file is identical, but the app doesn't know that because a change was made and then "corrected" by entering the original data. No matter the vehicle, the app thinks that the data is changed. (Some apps will mark a file as dirty, then, if the user "undoes" the changes all the way back to the original file, the app changes the file from dirty to clean.) I will try to remember to use the term "modified" rather than "dirty".

Here, I load the image, click Browser tab, click Memories or Settings tab, and the file is marked dirty (the * in the tab). Happened for the BaoFeng and Icom images.

I am loading the files using CHIRP File > Open, though I imagine (untested) that if the file opens in CHIRP after clicking in the File Manager, is would behave the same way. Interesting thought.

~R~

Actions #3

Updated by Jim Unroe almost 8 years ago

Rich,

Thanks for taking the time to explain. Now I am on the same wavelength. It seems to be the act of leaving the browser tab is what causes the "*' to appear.

Jim

Actions #4

Updated by Rich Messeder over 7 years ago

I just updated to chirp-daily-20161018-win32, and the effect is still there.

Actions

Also available in: Atom PDF