It appears that command key logging is broken in 4.5b b6. I tried several times to get a log while tracking down another bug and had to resort to turning on logging through KS4J's great script program [Y].
KS4J confirmed the bug as well in THIS POST.
Using Logos 4.5b (4.52.0.2176) can replicate command key not enabling diagnostic logging for a session.
Updated Feature Parity list with reference to this thread:
Keep Smiling [:)]
Updated Enable Mac logging for one session
Caveat: Logos 4.5b on Mac has a regression so using command key fails to enable logging.
I was unable to reproduce this on 4.5b SR-2. Let us know if you continue to experience this issue. Thank you.
Let us know if you continue to experience this issue.
Using Logos 4.5b SR-2 (4.52.0.2202) on Mac OS X 10.6.8 with Logos 4 Mac closed, changed logging from enabled to disabled, then used command:
defaults read com.logos.Logos_Bible_Software_4 LoggingEnabled
that returned a value of 0, followed by launching Logos 4.5b SR-2, then quickly pressing and holding command key until sign-in dialog box appears, released command key, then clicked "sign-in", however Logos4.log file was not created in Logging folder.
Used command to enable logging:
defaults write com.logos.Logos_Bible_Software_4 LoggingEnabled -bool YES
then launched Logos 4.5b SR-2 with command key. Noticed Logos4.log file was created in Logging folder before sign-in dialog box appeared.
After switching to beta channel, Logos 4.5c Beta 1 does have command key logging working so updated => Feature Parity list:
