To immediately update to the current beta enter the Update Now command. Otherwise, the app will automatically update the next time it's scheduled to check for updates.
Release Notes
Mac
Windows
Since upgrading to this beta I have a "task box" that follows me around no matter what program I'm in. Here's a screen shot of it covering this website. It appears when I copy something from a Logos resource and I have to return to Logos to get rid of it.
Tom can you reproduce this and provide logs?
It's happened twice in a few minutes but it doesn't happen every time.
My latest log files are from May 8. Did Logos switch to using another folder or something...
It's happened twice in a few minutes but it doesn't happen every time. My latest log files are from May 8. Did Logos switch to using another folder or something...
Yes, from the release notes from 8.5:
Moved the default logging folder location to:
Ok, I've got it back with logs. I can recreate it by selecting some text and then CTRL+C as quickly as possible because I want to copy the text before that box pops up because once it does CTRL+C doesn't work (I have to make it to go away and then CTRL+C again). There's some differences in focus in the logs which I suspect is the reason.
3480.Logos.zip
Since upgrading to this beta I have a "task box" that follows me around
Whenever I tried to highlight a passage that Selection Menu box would appear.
Then when I pressed my "hotkey" for the personalized highlight the "selected" text reverted to normal ie no "color" highlighting was applied to it.
(I realize that I could have chosen one of the Logos8 suggested highlights visible in the Selection Menu pop up box)
but I wished to have my own customized one as the option.
[I assume Selection Menu was added to solce a complaint. But it has just hindered my own way of doing things.]
So I finally just turned off this selection box in the Program Settings
Since upgrading to this beta I have a "task box" that follows me around Whenever I tried to highlight a passage that Selection Menu box would appear. Then when I pressed my "hotkey" for the personalized highlight the "selected" text reverted to normal ie no "color" highlighting was applied to it. (I realize that I could have chosen one of the Logos8 suggested highlights visible in the Selection Menu pop up box) but I wished to have my own customized one as the option. I finally turned off this selection box in the Program Settings
I finally turned off this selection box in the Program Settings
We're fixing the hotkey issue, however, if you apply your custom ones, then they will show up in the Selection Menu, it shows your most recently used ones.
if you apply your custom ones, then they will show up in the Selection Menu
How can they show up if the present mode of operation of the Selection Menu keeps them from being applied?
Thanks for the reply Philana but I remain Puzzled?
Ok, I've got it back with logs. I can recreate it by selecting some text and then CTRL+C as quickly as possible because I want to copy the text before that box pops up because once it does CTRL+C doesn't work (I have to make it to go away and then CTRL+C again). There's some differences in focus in the logs which I suspect is the reason. 3480.Logos.zip
This is going to be fixed, using the keyboard shortcut to copy will dismiss the pop-up.
I thought I noticed in a previous version of Logos that a tool tip indicated the name of your recently used custom highlights in the Selection Menu, but with Windows 8.6 Beta 4 (8.6.0.0030), there are no tool tips except for the Passage Guide and the Text Comparison icons. Tool Tips identifying all options would be helpful.
Tim, I'm still seeing tooltips for custom styles but not for standard styles (macOS). Could you confirm?
I am perhaps a little foolish and am running the Logos 8.6 Beta 4 (8.6.0.0030) on a Mac running MacOS Catalina 10.15 Beta (19A487l). This is partly because I like to test out the latest and greatest, and partly because the "stable" channel of Logos wouldn't open successfully for me on Catalina.
Things seem to be going well for the most part, except that, when I open a new Sermon document (not a Sermon Guide), I get a blank screen instead...
Clarification: I created a sermon doc in the Web app (which worked fine) but when I tried to open it in the Logos 8.6 beta 4, this is what shows up for me:
Also, the Atlas will not open for me...
Now Logos is crashing every time I try to open it. Here's the crash log:
*** Application Crash ***Program Version: 8.6 Beta 4 (8.6.0.0030)Windows Version: 10.0.18362.0.NET Framework Version: 4.0.30319.42000Time: 2019-07-03 11:28:34 -07:00 (2019-07-03T18:28:34Z)Installed memory: 24,481 MBInstall path: C:\Users\Tom\AppData\Local\Logos\Pending\Logos.exeFree install space: 97,542 MBTemp path: C:\Users\Tom\AppData\Local\Temp\Free temp space: 97,542 MBError ID: 1345Error detail: NotImplementedException: The method or operation is not implemented.System.NotImplementedException: The method or operation is not implemented. at MS.Internal.AppModel.ITaskbarList.HrInit() at System.Windows.Window.ApplyTaskbarItemInfo() at System.Windows.Window.WindowFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam) at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg) at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame) at System.Windows.Application.RunDispatcher(Object ignore) at System.Windows.Application.RunInternal(Window window) at LDLS4.OurApp.InitializeAndRun(ReadOnlyCollection`1 listArgs, SingleInstanceManager sim, Scope telemetryStep) at LDLS4.OurApp.Main(String[] astrArgs)
Tom,
I'm sorry you are crashing, I've got a few questions:
I works fine after restarting my computer but thought you might like to know.
After I rebooted my computer that folder disappeared and everything was back in C:\Users\Tom\AppData\Local\Logos\System. It opened fine and downloaded the latest beta (8.6.0.0046) and the pending folder reappeared but after L8 restarted it has once again disappeared.
After a software download, the Pending folder contains the executable files for a new version of Logos. Normally, it is renamed as System after you initiate a restart, and then you should be up and running the new version. Normally! If you notice a Pending folder and a System folder, something has gone wrong, and it could also affect the Windows Registry; which contains the location of the exe (and other information).
Fortunately, it corrected itself in your case, but I've had to fix the Registry in the past!
How did you install the beta if you couldn't open Logos to type in the command?
I am like you and am a little trigger happy when it comes to the "latest and greatest". Haha
The links are in the first post.
You click the Mac or Windows link in the first post! You get an installation file to run (in Windows), but it only does an update if Logos is already installed.
This beta saved me after updating to OS X Catalina. Thank you. It works great!
Jimmy
I am perhaps a little foolish and am running the Logos 8.6 Beta 4 (8.6.0.0030) on a Mac running MacOS Catalina 10.15 Beta (19A487l). This is partly because I like to test out the latest and greatest, and partly because the "stable" channel of Logos wouldn't open successfully for me on Catalina. Things seem to be going well for the most part, except that, when I open a new Sermon document (not a Sermon Guide), I get a blank screen instead...
This has been fixed in 8.8 RC 1.
