Sermon Editor Scripture Insert

Just recently on the updates, I have two issues with inserting scripture:
1st issue: When I enter a scripture reference on a new line and hit enter, it used to generate the verse text and powerpoint, then place the cursor on a new line. Then, a couple of months ago, it stopped going to a new line. I had to hit enter again for a new line.
2nd issue: Yesterday this problem has developed into a more frustrating issue. When I enter a scripture reference and hit enter, it just goes to a new line without entering the scripture or creating the powerpoint. To have Logos generate the powerpoint and insert the text into the sermon, I now have to do a combined key stroke of Command and enter (Mac user).
While it does work, it has ruined one of the greatest features of the Sermon Builder. I am currently running the latest updates on a MacBook Pro.
Comments
-
Same frustration here… I came here looking for a possible settings-based solution. Have you figured anything out?
0 -
Cmd+Enter on Mac and Alt+Enter on Windows is now used to insert a passage block. There is no setting to change this.
I find your observation about the cursor no longer going to a new line to be interesting. I'm not sure why the cursor would need to stay on the line with the inserted passage block. It seems more likely that users would immediately want to hit enter to move to the next line rather than edit or add to the reference. Inserting passage blocks could save users this trouble by going to the next line automatically, as was previously the case.
Because I would judge this change in behavior to be unintentional, I have tagged this post with Bug. However, to be clear, Cmd+Enter/Alt+Enter is not a bug.
0 -
One thing that may be contributing to this is the recent change introduced a delay. After typing a reference in sermon builder, I have to pause a second or two before hitting enter to get it to insert the verse block correctly. It seems that the latest update created a delay in recognizing verses. Not sure this will address your particular issue, but it sounds like it might be related.
0 -
This delay used to happen as you say, but for me on Windows 11 v41.1, it is no longer an issue. Verses are recognized almost instantaneously.
0