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:
So basically if someone doesn't have a solution just shut up, right?
Lol. Okay got it.
Sent from my iPhone
On Jan 4, 2017, at 3:41 PM, Charles J Skip Horni skip@butterflyfx.com wrote:
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:
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Joe Puma at theprogramllc@yahoo.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Wed, Jan 4, 2017 at 3:41 PM, Charles J "Skip" Horni skip@butterflyfx.com wrote:
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
Hi Skip,
CHIRP being used on Mac OS X is pretty common. Your issue with CHIRP is not common. Your report was the first time I have ever heard of it.
For the sake of argument, let's say there was a change in CHIRP that caused it to have this issue on your computer, then you should be able to install an older version of CHIRP that would not have this issue. If you can find the latest version that does work and report back what it is, it would help the developers solve your issue.
Jim KC9HI
hi Skip,
I genuinely was trying to be helpful. I will spell it out for you a little clearer; update your mac and make sure you have the latest fixes.
Often a new build of a product like CHIRP will have issues on an older version of the mac, depending on many many factors.
You have a couple of choices: 1) download a earlier version of CHIRP and keep flying, 2) update your mac and retry with the current version of CHIRP, 3) after updating your mac ( and still having the same issue with CHIRP ) open a bug report.
The problem you are talking about is not a common issue; consequently, there must be something about your setup that is unique. That is very helpful if you'll think about it a bit.
regards, '73 marcus W0MHH
On Wed, Jan 4, 2017 at 2:41 PM, Charles J "Skip" Horni <skip@butterflyfx.com
wrote:
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:
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to marcus at harrismh777@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com
participants (4)
-
Charles J "Skip" Horni -
Jim Unroe -
Joe Puma -
Mark H. Harris