Bug? No cursor in Notes
After updating to Logos 8.9, I no longer see a cursor in any Note. As you can imagine, typing "blind" is much harder.
Am I the only one seeing this behavior?
Comments
-
-
Jack Hairston said:
After updating to Logos 8.9, I no longer see a cursor in any Note. As you can imagine, typing "blind" is much harder.
Am I the only one seeing this behavior?
Is this with multiple monitors?
If so, it sounds similar to the report at https://community.logos.com/forums/p/67600/1075198.aspx#1075198
0 -
Graham Criddle said:Jack Hairston said:
After updating to Logos 8.9, I no longer see a cursor in any Note. As you can imagine, typing "blind" is much harder.
Am I the only one seeing this behavior?
Is this with multiple monitors?
If so, it sounds similar to the report at https://community.logos.com/forums/p/67600/1075198.aspx#1075198
Thanks Graham for the clue. My behavior is just as you suggested. I'll follow that thread to see if there's a solution.
0 -
Levi Durfey said:
I am seeing the cursor just fine on Logos 8.9/macOS 10.15.1.
Thanks, Levi. Unless the behavior only happens on a secondary monitor, tt's looking like a Windows-only problem.
0 -
Jack Hairston said:
After updating to Logos 8.9, I no longer see a cursor in any Note. As you can imagine, typing "blind" is much harder.
Am I the only one seeing this behavior?
Hi Jack,
I've written up a bug report. We've not been able to reproduce it yet. Are you by any chance using a Surface Pro?
0 -
Nope, sorry. My Win10 desktop L8 system is
- HP Envy laptop 17-ae1xx
- Secondary monitor is HP Pavilion 32q
I sure hope you can nail this down, Philana. Thanks for your help.
0 -
It only happens on the secondary monitor. I reported it earlier.
0 -
I too have this problem on the secondary (actually second and third monitor).
0 -
Any timeline on the fix?
0 -
Philana R. Crouch said:Jack Hairston said:
After updating to Logos 8.9, I no longer see a cursor in any Note. As you can imagine, typing "blind" is much harder.
Am I the only one seeing this behavior?
Hi Jack,
I've written up a bug report. We've not been able to reproduce it yet. Are you by any chance using a Surface Pro?
Philana, is anyone actively pursuing this bug? It would be reassuring to hear that it has not been forgotten.
0 -
We are still investigating this issue. In the meantime, Microsoft has released KB4534132 with the following release note:
- Addresses incorrect width of the text-insertion caret in TextBox et al., when the system DPI exceeds 96. In particular, the caret rendered nothing on a monitor with lower DPI than the primary, in some DPI-aware situations.
This sounds very similar to the problem being reported in this thread. Would anyone who's affected by the disappearing caret issue be able to install this update (from Windows Update) and report if it helps?
0 -
We are still investigating this issue. In the meantime, Microsoft has released KB4534132 with the following release note:
- Addresses incorrect width of the text-insertion caret in TextBox et al., when the system DPI exceeds 96. In particular, the caret rendered nothing on a monitor with lower DPI than the primary, in some DPI-aware situations.
This sounds very similar to the problem being reported in this thread. Would anyone who's affected by the disappearing caret issue be able to install this update (from Windows Update) and report if it helps?
I made sure the latest Microsoft updates were installed. This hotfix was not in the resulting list of installed hotfixes. When I tried to manually install this hotfix, I received a message that this one did not apply to my computer. [sigh]
0 -
Jack Hairston said:
I received a message that this one did not apply to my computer.
What version of Windows 10 are you running?
If you're not running Windows 10 1909 yet, you can update to it here: https://support.microsoft.com/en-us/help/4028685/windows-10-get-the-update
(Then the .NET Framework updates should become available.)
0 -
Jack Hairston said:
I received a message that this one did not apply to my computer.
What version of Windows 10 are you running?
If you're not running Windows 10 1909 yet, you can update to it here: https://support.microsoft.com/en-us/help/4028685/windows-10-get-the-update
(Then the .NET Framework updates should become available.)
Here you go. If I can help further, please let me know.
0 -
Your version of Windows 10 is over a year old, so I would recommend updating if you can. (There have been two major updates since Version 1809 and a third is scheduled to ship later in the first half of 2020. Service and support for Windows 10 1809 ends in May this year: https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet.)
0 -
You're right about Win10 being out of date. The strange part is that whenever I checked for latest updates, Windows said I was up-to-date. Now it is.
Unfortunately, updating Windows did not fix the missing-cursor problem. [sigh] Do you have any other steps I might take?
0 -
I forgot to mention that even when Win10 was updated to version 1909 and all the latest hotfixes were installed, the problem (no cursor in second monitor) still was not fixed. Sorry.
0 -
Jack Hairston said:
I forgot to mention that even when Win10 was updated to version 1909 and all the latest hotfixes were installed, the problem (no cursor in second monitor) still was not fixed. Sorry.
I, too, have the latest Win10 version 1909 update and the cursor does not show up on the second monitor in notes and in certain fields in the Sermon Editor. The problem in notes is annoying but you can still add notes. You just have to click and type, hoping you clicked in the right place before typing away.
0 -
Pastor Dan Cleghorn said:
I, too, have the latest Win10 version 1909 update and the cursor does not show up on the second monitor in notes and in certain fields in the Sermon Editor. The problem in notes is annoying but you can still add notes. You just have to click and type, hoping you clicked in the right place before typing away.
[Y] Frustrating, but still usable. I'm happy to see that Faithlife's software engineers are still gnawing on this issue.
0 -
Hi I updated Windows as suggested by Bradley and it worked for me, thanks for the quick fix!
0 -
Welcome to the forums, Harry, and thanks for the news. Unfortunately, even after the latest Logos 8 update, the cursor is still not visible for me when editing a Note.
0 -
Jack Hairston said:
Welcome to the forums, Harry, and thanks for the news. Unfortunately, even after the latest Logos 8 update, the cursor is still not visible for me when editing a Note.
The cursor is not showing on my second monitor either. Both in notes and in certain fields in sermon editor.
0 -
Just checked to see if this bug is fixed yet. The second or third monitor problem continues.
0 -
I just noticed that the cursor is visible in my Notes panel where Logos operates in a secondary monitor. Is this just me, or has a changed to Windows or Logos fixed the problem?
0 -
Cursor still does not show up for me on 2nd and 3rd monitor. This is with updated Windows 10 1909 + KB4550945 updates. Logos 8.13.0.0008
0 -
Yep, I am having the same problem as well on a newly acquired laptop with fresh install of the latest Win10 Pro & Logos 8.13.0.0008.
0 -
Jeff O'Neal said:
Yep, I am having the same problem as well on a newly acquired laptop with fresh install of the latest Win10 Pro & Logos 8.13.0.0008.
This is reported as fixed in the latest betas (https://wiki.logos.com/Logos_8.14_Beta_1). Still a few weeks from the stable version. If you are willing to take the risk of using a beta version, go here: https://community.logos.com/forums/t/190671.aspx
0 -
Jack Hairston said:
After updating to Logos 8.9, I no longer see a cursor in any Note. As you can imagine, typing "blind" is much harder.
Am I the only one seeing this behavior?
This has been fixed in 8.14.
0 -
Hats off to the developers who traced down this but and eliminated it.
Way to go!
0 -
Yes! Fixed with 8.14.0.0010
0 -
Jack Hairston said:
Hats off to the developers who traced down this but and eliminated it.
Way to go!
Yes some buts are hard to find. [:D]
Dr. Kevin Purcell, Director of Missions
Brushy Mountain Baptist Association0 -
[H] Caution: Blind typist, no proof reader...
0
