-
David, Check your program setting and make sure both your content and program scaling is set to 100%. this bug causes many problems
-
I tried this with program and content scaling set to 100% and it works properly, but when you set scaling to anything above 100% it does not work. This is a bug that has been around far too long!
-
Program and content scaling still not fixed. Have to set both at 100% in order to select a new resource in concordance to add to saved resource list.
-
Joe, This morning program worked properly. Was able to add Verse of the Day. Problem solved! Thanks for your help!
-
Application freezes when trying to add verse of the day Version 8.11.1 (0033) IOS 13.4
-
Philana I found that when I set my content and program scaling to 100% Concordance populates as it should. Can we get program and content scaling for the Mac fixed?
-
Philania I had my content scaling set to 120% and content to 110%. When I set my content and program scaling to 100% it works as it should
-
Jack I am using Mac OS 10.15.1 .
-
Yes Jack I am with no response
-
Clicking on tab in Mobile Ed course to expand screen has no effect. Does not expand screen to full screen
-
Bump
-
Richard Select the text that you would like to erase then use the short cut keys (Ctrl+Shift+K)
-
Thanks Philana!
-
Bump
-
Philana All my resources are up to date. I get resources all the time but this has been happening for a while now. I just haven't reported it. The resources never populate and cause program to crash.
-
Philana I have the ESV Bible selected. When clicking on it to bring up other resources list does not populate I don't get any resources to select from. Attached is another set of logs 7220.LogosLogs.lewisharper.20191125-132545.zip
-
Clicking on menu to select another resource and get spinning beach ball 3733.LogosLogs.lewisharper.20191125-123446.zip
-
No X or delete to remove a saved range mac OS 10.15
-
Tim, I can confirm the missing text on macOSA Mojave
-
Paul, This has been reported and fixed as reported here. https://community.logos.com/forums/t/178756.aspx Looks we will have to wait until the next beta release before we receive the fix.