[chirp_users] New Daily Build

[Rich Messeder]

I linked to the messages (see bottom of email), and saw some comments about the background for this mod. Here are my comments, just FYI, no complaints.

Windows 10 Pro x64.

1. I am using the standalone version. Wish that there is an x64 version.

2. Copy | Paste of records and record blocks twixt 2 instances if CHIRP, using ctrl-c, -v, works for records now.

3. Twould be nice if the confirmation dialog showed up on the same display as the main program. I run CHIRP on a an extended display in Windows.

4. Ctrl-x does not work  in a field. Delete does not work in a field. Ctrl-v does not work in a field.

5. RMC: Copy //does// work in a field, but then RMC: Paste is disabled in the 2nd instance. I /can/ RMC: Paste into a different file in a different tab in the same instance.

6. I use  the standalone version because I find it more controllable than installing multiple versions of the same product, though I imagine that upgrading the installed version in place works fine. Not tested. I do this so that it is easy for me to roll back, if I wish.

7. I use multiple instances of the standalone version because I can alt-tab twixt them to copy | paste. Ctrl-tab does not work for me, though it does shift the focus from a memory to a tab. So I can't easily cut from one tab and paste to another.

8. I understand deprecating .chirp files, even if I don't know the history. If .csv files are the ne way of exporting, that works for me.

9. Still don't know why I can't save  Kenwood TH-F6A .img in CHIRP, but can in Kenwood's Memory Control Program (MCP). MCP is not "live". I just did this test. While CHIRP was open, I ran MCP. I downloaded from the F6A. I modified a memory. I saved the file as .fx. I ended MCP. The F6A remained unchanged. I interpret this to mean that I could save the F6A in CHIRP as a .img file (which I can't).

10. It's nice that both MCP and CHIRP do not take control of the COM port; that is, they open it, use it, and release it. This allows me to run both programs at the same time. Currently, there are advantages and disadvantages to using both MCP and CHIRP with the F6A, so I use both.

~R~ NE1EE
Short email? No html? Here's why: http://emailcharter.org/

On 2016-05-31 00:09:-0700, Build System wrote:
>Greetings,
>http://trac.chirp.danplanet.com/chirp_daily/daily-20160531
>
>A list of the changes included in this build (since the last daily) follows:
>
>Changes for Build #405
>[Tom Hayward <tom at tomh.us>] [ui] Change clipboard target to support cross-process copy/paste on Windows. #3693
>
>Clipboard target was PRIMARY, the X clipboard. Changed to CLIPBOARD, the
>default clipboard, for better Windows support including the ability
>to copy/paste between multiple instances of Chirp.
>
>http://intrepid.danplanet.com/pipermail/chirp_devel/2016-May/004018.html
>
>[Tom Hayward <tom at tomh.us>] [ui] Store clipboard outside of app, so paste works after quitting. #3691
>
>[Tom Hayward <tom at tomh.us>] [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.
>
>chirp_users mailing list
>chirp_users at intrepid.danplanet.com
>http://intrepid.danplanet.com/mailman/listinfo/chirp_users