Dave,
Other than the normal “malicious software” warning, having to go into System Settings and telling it to run anyway, and getting just a single “Fldigi wants to use your microphone” prompt, I am able to run this just fine including subsequent program starts.
I’m on an M2 Max Mac Studio.
I cannot remember what makes it show up in Launchpad but .02 doesn’t show up in Launchpad either.
toggle quoted message
Show quoted text
On Nov 13, 2024, at 10:59?AM, Dave, W1HKJ via groups.io <w1hkj@...> wrote:
I need a few Mac users to test
install this version of fldigi:
on M1/2/4 systems.
You may need to right click on the installed app icon in
/Applications to force the first start.? The Mac will complain
that it cannot test the app for malicious software (read that as
I did not pay Apple their insurance premium).? You will also
have to allow microphone use, but only once.
David, W1HKJ
On 11/13/24 10:12, Dave, W1HKJ wrote:
I will look again at the
code, but this change was forced upon us by the current ADIF
specification.
David
On 11/12/24 22:08, Barry, PC1K via
groups.io wrote:
Hello,
Today I got around to testing fldigi 4.2.06, specifically:
With this patch, when I log a QSO in FSKH105, fldigi logs HELL
in the mode field, which is correct.
However the submode field, is not in logbook.adi, nor do I see
it anywhere else in the UI. This means that all Hell contacts
will be logged as HELL regardless of submode. Is there a way to
configure fldigi so that it stores the submode to logbook.adi
and preferably show the submode in the UI?
Thanks, Barry
Joel Black - W4JBB