I really, really am not trying to be rude.
Sorry, but blaming OS X is very unhelpful.
CHIRP worked fine and now it doesn¹t and this is an OS issue?
Rhetorical.
Unless someone can assist me, actually, assist, I would just as soon have no response.
The idea was to just report a bug seen in OS X.
If the problem is not going to be fixed, say so or, preferably, don¹t say anything, please.
Skip Horni
Message: 1 Date: Tue, 3 Jan 2017 23:25:22 -0600 From: "Mark H. Harris" harrismh777@gmail.com Subject: Re: [chirp_users] Off Track. To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Message-ID: CAFq9LpnbU+0UKfB+kcYmVWLEMZD2=ABPqY4H+++zw1Mtmi8-Rg@mail.gmail.com Content-Type: text/plain; charset="utf-8"
This issue is probably due to the desktop|window manager ( OS gui issue ) rather than an issue with the CHIRP software per se.
On Mon, Jan 2, 2017 at 3:29 PM, James Knapp jknappmd@gmail.com wrote: