- Developers - lists.chirpmyradio.com

[chirp_devel] [PATCH] [ui] Deprecate .chirp file format by disabling export. #3689
by Tom Hayward 26 May '16

26 May '16

# HG changeset patch # User Tom Hayward <tom(a)tomh.us> # Date 1464305985 25200 # Thu May 26 16:39:45 2016 -0700 # Node ID e16d2a8d216d10cdf678ff4ff6a1f7af940d6e78 # Parent 8ba3e3590a2a26f67a85f0c26ea4ca89d5b86081 [ui] Deprecate .chirp file format by disabling export. #3689 The .chirp file format provides no additional features compared to .CSV and is therefore redundant. .chirp is the more complex and less frequently used format of the two, so to eliminate the redundancy it should be deprecated. This patch removes the ability to export as .chirp, leaving no way to generate new .chirp files. It preserves the ability to open and import .chirp files, so any existing .chirp files can still be opened, edited, and exported to other formats. diff -r 8ba3e3590a2a -r e16d2a8d216d chirp/ui/mainapp.py --- a/chirp/ui/mainapp.py Thu May 26 12:14:44 2016 -0700 +++ b/chirp/ui/mainapp.py Thu May 26 16:39:45 2016 -0700 @@ -1164,7 +1164,6 @@ def do_export(self): types = [(_("CSV Files") + " (*.csv)", "csv"), - (_("CHIRP Files") + " (*.chirp)", "chirp"), ] eset = self.get_current_editorset()

1 0

[chirp_devel] [PATCH 0 of 2] Cross-instance copy/paste in Windows. ATTN: Jim
by Tom Hayward 26 May '16

26 May '16

Jim, Rich reported that copying in one instance of Chirp and pasting in another doesn't work. I tested this myself... Linux: - can open two instances of chirpw - copy/paste works between instances Mac OS X: - won't allow opening two instances - succeeded in opening two different versions of Chirp - copy/paste works between two different-version instances Windows: - installed version won't allow opening two instances - standalone version allows multiple instances - copy/paste doesn't work between instances So we can deduce Rich must be using the standalone version on Windows. The next question is why copy/paste doesn't work between instances on the standalone Windows version. I looked at which clipboard Chirp uses and it's one built into X. My guess is that PyGTK emulates this on Windows instead of using the OS clipboard. The first of these two patches changes the clipboard target to the normal OS clipboard. Can you test this on Windows? I don't have a Windows dev environment set up. The second patch is another attempt to solve the same problem. It stores the clipboard data outside the app. This feature exists so that the clipboard data can remain available after the source app is closed, but my thought is it might solve the cross-instance paste issue. Can you test this patch separately from the first one? Tom

2 4

[chirp_devel] [PATCH] [BTECH] Add new settings for BTECH gen3 radios
by Jim Unroe 25 May '16

25 May '16

# HG changeset patch # User Jim Unroe <rock.unroe(a)gmail.com> # Date 1464013811 14400 # Node ID 77bd2ad5e4e37248f31d56a7aa122956848e7bb2 # Parent 41195d73360b401e4f34f31cf87e4d79f09e70ee [BTECH] Add new settings for BTECH gen3 radios * Mic Gain * DTMF Gain related to #3015 diff -r 41195d73360b -r 77bd2ad5e4e3 chirp/drivers/btech.py --- a/chirp/drivers/btech.py Tue May 17 11:07:32 2016 -0400 +++ b/chirp/drivers/btech.py Mon May 23 10:30:11 2016 -0400 @@ -96,6 +96,8 @@ u8 ste; u8 rpste; u8 rptdl; + u8 mgain; + u8 dtmfg; } settings; #seekto 0x0E80; @@ -1236,6 +1238,18 @@ _mem.settings.rptdl])) basic.append(rptdl) + if str(_mem.fingerprint.fp) in BTECH3: + + mgain = RadioSetting("settings.mgain", "Mic gain", + RadioSettingValueInteger(0, 120, + _mem.settings.mgain)) + basic.append(mgain) + + dtmfg = RadioSetting("settings.dtmfg", "DTMF gain", + RadioSettingValueInteger(0, 60, + _mem.settings.dtmfg)) + basic.append(dtmfg) + # Advanced def _filter(name): filtered = ""

1 0

[chirp_devel] "hg email tip" error
by Jim Unroe 25 May '16

25 May '16

I just tried to submit a patch and got the following error. abort: (535, '5.7.8 Username and Password not accepted. Learn more at\n5.7.8 ht tps://support.google.com/mail/answer/14257 q19sm2047723itc.18 - gsmtp') I believe that this is due to me changing my password to gmail recently. I thought I had notes from when I originally setup mercurial, but I can seem to locate them. Google has been no help so far. Any ideas? Thanks. Jim

2 1

[chirp_devel] Gnome nautilus script to clean portmon logs.
by Pavel Milanes (CO7WT) 20 May '16

20 May '16

Hi to all, Today I want to share one of y tools to make the process of debugging portmon logs more faster and eye refreshing, this nautilus script is intended for the users that has a GNU/Linux with any of the Gnome flavors as a develop environment. (works with the default Ubuntu's Unity) The goal is to clean the original portmon serial logs from all the non essential "garbage" to make it more easy to analyze, but remember that under certain circumstances you will have to look at the original log, so this tool will preserver it. To make it work you must surf into the folder ~/.local/share/nautilus/scripts/ and copy it inside; It's as easy as follow this instructions: * Press Alt+F2 and paste "~/.local/share/nautilus/scripts/" in the box + Enter, a nautilus window will open, o If it complains about the folder not existing or do nothing, please do this extra steps: o Press Alt+F2 and paste "~/.local/share/nautilus/", A nautilus window will open o Create a folder named "scripts" (without quotes) and open it, now follow the next step * Just paste the file there, * Right-click the file and select properties, then permissions * Tick the box about allowing to run it as a program * Close the nautilus windows, that's all. After that you will need to find a portmon serial log and right-click it, search for and option named "Scripts" and after expanding it you will find the "Chirp portmon clean log" option, select it and a file with the exact name and an extension of .clean will appear on your folder, additionally the Gedit text editor will pop up with the clean log on it. Compare the original and cleaned log and your will find that your eyes/brain will thanks you for this. This also works with several files at once; as always use it, share it, improve it, it's GNU GPL 3.0 [The long name is because I have a lot of scripts in my script folder and I group them by the main related activity, of course you can change the name of it once it's recognized by the system] 73 -- 73 Pavel CO7WT.

1 0

[chirp_devel] [PATCH][KT8900R] Settings fix about the 220Mhz band, fixes #3547
by Pavel Milanes (CO7WT) 17 May '16

17 May '16

Now we have two of this radios that has 220/240 Mhz support in the base class and we need to validate the freq ranges for each one of them, this patch is to realize that. Thanks to Jim Unroe for the help with it. -- 73 Pavel CO7WT.

1 0

[chirp_devel] [PATCH][KT8900R] Initial support for the QYT KT8900R, fixes #3547
by Pavel Milanes (CO7WT) 16 May '16

16 May '16

This radio is like the BTECH UV-2501+220 but it has the 220 band in the Chinese area (240-270 Mhz) well outside the USA ham band. This is the initial support patch for this radio, it may need further work on the settings part. -- 73 Pavel CO7WT.

1 0

[chirp_devel] [PATCH][BTECH] Add a flag to know we have a BTECH gen3, fixes #3015
by Pavel Milanes (CO7WT) 16 May '16

16 May '16

This 3 gen wave of BTECH radios has new settings items and we need a flag to know when we are dealing with one of these to show the settings properly. This is an advance to the real settings modification. 73

1 0

[chirp_devel] [PATCH][BTECHs] Add support for the new Gen3 wave of BTECHs, fixes #3015
by Pavel Milanes (CO7WT) 13 May '16

13 May '16

This add support for the new generation (3gen) if the following BTECHs: * UV-2501 * UV-2501+220 * UV-5001 73

1 0

[chirp_devel] [PATCH][KT8900] Comment about old versions of KT8900 in the UI, fixes #3539
by Pavel Milanes (CO7WT) 13 May '16

13 May '16

All points that the QYT KT8900 is the main OEM model, and there are two variants of it, from the prespective of the communication dance: * One is with just the ID and right to the down/up process (clone of WACCOM Mini8900) * The other (is the default now) with a second id read & a extra step on the upload process. As both uses different communications steps we can't put them both under the same case, fortunately the "older" model has a clone in the WACCOM Mini8900. We put here a notice on the failure to read a KT8900 to warn the users to try the WACCOM Mini8900 instead.

1 0